Changes between Initial Version and Version 1 of GROUP_SCRIPTING_R0


Ignore:
Timestamp:
07/04/09 19:17:55 (16 years ago)
Author:
mitex
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GROUP_SCRIPTING_R0

    v1 v1  
     1[[BackLinksMenu]] 
     2 
     3[[TicketQuery(summary=GROUP_SCRIPTING_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 == 
     8The users should be able to type and execute custom scripts. 
     9 * The script file is resource. 
     10 * Execute button should present inside resource pallet.  
     11 * Scripts could be edited inside document window. Again execute button should present. While editing the resource is saved automatically. 
     12 * Scripts could also be executed via links. 
     13 * The resource preview for scripts could allow editing. 
     14 * There should be ability to import/export script files. 
     15 * The user could create/edit/delete script files. 
     16== Task requirements == 
     17Create prototype for scripting that include following functionality. 
     18 * Ability to add/edit/delete script files. 
     19  * Add 'Insert Script File' button inside 'Insert' menu 
     20  * Create 'Insert Script' button inside 'Insert' menu that creates new resource. 
     21  * Provide document window that allows editing for scripts as well as executing them. 
     22  * Add 'Execute' button inside resource details pallet, that is visible only when script resource is selected. 
     23 * Create 'Hello world' example via scripting in Sophie 
     24 * OPTIONAL: Provide functionality that allows scripts to be evoked from links. 
     25 * Provide functionality that allows for script resource to be exported to files. Again in resource pallet. Also while editing it from the file menu save and save as should be functional. (NOTE: Saving the resource should be automatically, but exporting it to file is not) 
     26 
     27== Task result == 
     28 * The result should be code 
     29 
     30== Implementation idea == 
     31 * The output for the script could be Eclipse console or popup window. 
     32 
     33== Related == 
     34^(Add links to related tasks that could be useful or helpful.)^ 
     35 
     36== How to demo == 
     37^(Provide instructions for demonstration of the task.)^ 
     38 
     39= Design = 
     40^(Describe your design here.)^ 
     41 
     42= Implementation = 
     43^(Describe and link the implementation results here (from the wiki or the repository).)^ 
     44 
     45= Testing = 
     46^(Place the testing results here.)^ 
     47 
     48= Comments = 
     49^(Write comments for this or later revisions here.)