| 1 | [[BackLinksMenu]] |
| 2 | |
| 3 | [[TicketQuery(summary=SCRIPTING_ACTIONS_API_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 | The goal of this task is to expose to the user the Sophie book's model and Sophie's logic in a user-friendly way. |
| 9 | |
| 10 | Generally, there are two use-cases for scripting, which imply some differences in the requirements: |
| 11 | * Scripts used for automation |
| 12 | * The result of their execution should be undoable, as each other change to the model |
| 13 | * Scripts as link targets |
| 14 | * They have limited scope - for example, user cannot create a new book with them |
| 15 | * There's no need to be undoable |
| 16 | |
| 17 | == Task requirements == |
| 18 | ^(List the necessary requirements that the task must fulfill.)^ |
| 19 | |
| 20 | == Task result == |
| 21 | * Source code |
| 22 | |
| 23 | == Implementation idea == |
| 24 | ^(Provide some rough implementation idea(s).)^ |
| 25 | |
| 26 | == Related == |
| 27 | ^(Add links to related tasks that could be useful or helpful.)^ |
| 28 | |
| 29 | == How to demo == |
| 30 | ^(Provide instructions for demonstration of the task.)^ |
| 31 | |
| 32 | = Design = |
| 33 | ^(Describe your design here.)^ |
| 34 | |
| 35 | = Implementation = |
| 36 | ^(Describe and link the implementation results here (from the wiki or the repository).)^ |
| 37 | |
| 38 | = Testing = |
| 39 | ^(Place the testing results here.)^ |
| 40 | |
| 41 | = Comments = |
| 42 | ^(Write comments for this or later revisions here.) |