| | 1 | [[BackLinksMenu]] |
| | 2 | |
| | 3 | [[TicketQuery(summary=PRO_CHANGE_SCOPING_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 | == Overview == |
| | 7 | The goal of this task is to define the scope and extent to which Changes apply. |
| | 8 | |
| | 9 | == Task requirements == |
| | 10 | * Devise a concept on what areas of Sophie 2 should Changes should apply, like: |
| | 11 | * Should Changes be applied to the model only |
| | 12 | * Should Changes also be applied to the state of the views |
| | 13 | * Should Changes be applied to models and views in a hybrid way |
| | 14 | * Should Changes be applied to shared resources |
| | 15 | * Other [[BR]] |
| | 16 | Argue on these alternatives and provide an ideas for solutions |
| | 17 | * Here are listed a few concrete problems which also must be solved: |
| | 18 | * Are all actions, which mutate the views, to be considered Changes? If not, which of these actions should be considered Changes? |
| | 19 | * A change in a model (a Frame, for instance) produces multiple changes in the views, dependent on this model (BookViews). Which of the view changes (if any) are to be uploaded on the server and which are to be handled locally? |
| | 20 | * Two books share the same resource (possibly embedded in both), for instance some license text. One user edit this shared resource which results in a Change locally at his side, which he can undo/redo. Should the other user be able to undo/redo this change? Generally, how should a Change of shared resource from a user on one of the sides affect affect the other side? |
| | 21 | * Think of other problems with the scope of Changes and propose solutions to the above |
| | 22 | |
| | 23 | == Task result == |
| | 24 | * Design ideas and solutions on the above problems, listed in the wiki page |
| | 25 | |
| | 26 | == Implementation idea == |
| | 27 | * View the related pages and problems to get a broader perspective |
| | 28 | * Search for solutions on the Web |
| | 29 | |
| | 30 | == Related == |
| | 31 | [wiki:PRO_CHANGE_MANAGER_R0] [[BR]] |
| | 32 | [wiki:PRO_CHANGE_UNDO_MANAGER_R0] [[BR]] |
| | 33 | [wiki:PRO_CHANGE_PRIMITIVES_R0] [[BR]] |
| | 34 | [wiki:PRO_LIB_CORE_TUTORIAL] |
| | 35 | |
| | 36 | == How to demo == |
| | 37 | * Show this page |
| | 38 | * Explain the problems and the proposed solutions |
| | 39 | |
| | 40 | = Design = |
| | 41 | ^(Describe your design here.)^ |
| | 42 | |
| | 43 | = Implementation = |
| | 44 | ^(Describe and link the implementation results here (from the wiki or the repository).)^ |
| | 45 | |
| | 46 | = Testing = |
| | 47 | ^(Place the testing results here.)^ |
| | 48 | |
| | 49 | = Comments = |
| | 50 | ^(Write comments for this or later revisions here.) |
