| | 1 | [[BackLinksMenu]] |
| | 2 | |
| | 3 | [[TicketQuery(summary=FRAME_LINK_TRIGGERING_R0, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|)]] |
| | 4 | |
| | 5 | = Analysis = |
| | 6 | |
| | 7 | == Overview == |
| | 8 | |
| | 9 | This task is about how users will trigger links while in test mode. |
| | 10 | |
| | 11 | While in author mode, the user can select a frame and get the link halo for frames. They will be able add actions to the frame and then put Sophie into test mode. |
| | 12 | |
| | 13 | Once in test mode, the mouse and keyboard actions can effect how links are triggered. When passing a mouse over the frame, any mouseEnter actions would be triggered. When the mouse leaves the frame, mouseLeave actions would triggered. |
| | 14 | |
| | 15 | When the user clicks the frame, any mouseDown/mouseUp/mouseClicked actions should be triggered. |
| | 16 | |
| | 17 | The R3 event system should handle the proper hierarchy of event handling for frames. If not, that will be to be fixed. What I mean by this is that, for example, if the user has a text frame, and some text in the frame has a link and the frame itself has a link, if the user clicks the text link, only the text link should trigger. If the user clicks any text that is not linked, the click should be sent up the object hierarchy to the frame, which would then handle the click and trigger any actions on the frame. |
| | 18 | |
| | 19 | == Task requirements == |
| | 20 | |
| | 21 | * Add event handling to frames for: (if neeeded) |
| | 22 | * mouseEnter |
| | 23 | * mouseLeave |
| | 24 | * mouseDown |
| | 25 | * mouseUp |
| | 26 | * mouseClicked |
| | 27 | * Dispatch actions based on events sent to the frame |
| | 28 | * Make sure R3 Event system sends the proper events to the frame (it should be) |
| | 29 | |
| | 30 | == Task result == |
| | 31 | |
| | 32 | The result of this task is code |
| | 33 | |
| | 34 | == Implementation idea == |
| | 35 | |
| | 36 | There should be no if-then statements. The dispatch of the actions should be transparent and shared among all objects, whether they are frames, or text, or a portion of a movie or image. You should just make sure that the proper event sends the right event id to whatever module is executing events. |
| | 37 | |
| | 38 | Write as little code as possible. Most of this code should be shared amonst all objects that can trigger actions. |
| | 39 | |
| | 40 | == Related == |
| | 41 | |
| | 42 | * [wiki:FRAME_LINK_MANIPULATION_R0] |
| | 43 | * [wiki:LINKS_MANIPULATION_R0] |
| | 44 | * [wiki:TEXT_LINK_TRIGGERING_R0] |
| | 45 | |
| | 46 | == How to demo == |
| | 47 | |
| | 48 | Attach an action to a frame, change into test mode and then execute the link by clicking on the frame |
| | 49 | |
| | 50 | = Design = |
| | 51 | ^(Describe your design here.)^ |
| | 52 | |
| | 53 | = Implementation = |
| | 54 | ^(Describe and link the implementation results here (from the wiki or the repository).)^ |
| | 55 | |
| | 56 | = Testing = |
| | 57 | ^(Place the testing results here.)^ |
| | 58 | |
| | 59 | = Comments = |
| | 60 | ^(Write comments for this or later revisions here.) |
