Changes between Version 1 and Version 2 of GROUP_PLUGINS_R0


Ignore:
Timestamp:
03/10/09 13:27:00 (16 years ago)
Author:
boyan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GROUP_PLUGINS_R0

    v1 v2  
    11[[BackLinksMenu]] 
    22 
    3 [[TicketQuery(summary=GROUP_PLUGINS_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|)]] 
     3[[TicketQuery(summary=GROUP_PLUGINS_R0, format=table, col=summary|owner|status|type|component|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)]] 
    44 
    55= Analysis = 
    … …  
    99 
    1010== Task requirements == 
    11  * Provide a basic version of the plugin support library: 
    12   * Provide an API for dealing with shared resources (see [wiki:PLUGIN_SUPPORT_LIB_BASE_R1]). 
    13   * Provide an API that allows plugin configuration. 
     11 * Provide an API for dealing with shared resources: 
     12  * Resources that will be used by the application should go in the /src/main/resources/distrib folder of each module. 
     13  * A resource manager should be implemented - it should be able to get these resources. 
     14  * All existing static paths should be changed to use the newly written functionality. 
     15  * Both the Fake and True launchers should correctly handle these. 
     16 * Provide an API that allows some kind of plugin configuration: 
     17  * Define how plugins will be configured. 
     18  * Provide the classes/iterfaces necessary for plugin configuration support. 
     19  * Choose a plugin that will be configured and define what will be configured about it. 
    1420 * Add a plugin configuration palette to the application: 
    15   * it should allow configuring of the selected plugin if the plugin supports it. 
    16   * at least one plugin should be configurable at this iteration. 
     21  * Make sure it works in the TrueAuthorMain (currently the plugin info palette that exist works in the FakeAuthor only). 
     22  * It should allow configuring of the selected plugin if the plugin supports it. 
     23  * At least one plugin should be configurable at this iteration. 
    1724 
    1825== Task result == 
    … …  
    2027 
    2128== Implementation idea == 
    22  * Use the design of [wiki:PLUGIN_SUPPORT_LIB_BASE_R1] and improve it to implement the resources functionality. 
    23  * Consider an interface for the configurable plugins with a single method that automatically configures them. 
     29 * Consider using a config file for each plugin and loading it as a resource. 
     30 * See if you can use the OSGi plugin configuration service. 
     31 * A plugin might provide a list of all configuration options that can be configured (just a list, no GUI elements). 
     32 * Another option is for the plugin to provide the GUI configuration elements - a panel, dialogs or whatever is needed. 
    2433 
    2534== Related == 
    … …  
    2938== How to demo == 
    3039 * Configure a plugin from the plugin configuration palette. 
    31  * Show and briefly describe the plugin support library. 
     40 * Show and briefly describe the code of the plugin support library. 
    3241 
    3342= Design =