Function Plugin Manager

[GoogleCodeExporter]

Core Requirements
-Users should be able to disable/enable individual function plugins while the 
application is running.
-The application should remember the users set of enabled function plugins.
-Enabling a function plugin should not require the application to be restarted 
in order for its functionality to take effect.
-The user should be presented with an easy to use graphical interface for 
toggling function plugins.
-Any class that makes use of plugins will need to be notified when a plugin 
becomes enabled/disabled.

Additional Requirements
-Function plugins should be able to specify whether or not they can be toggled 
on and off in plugin_preferences.xml.
-The interface for toggling function plugins should group them by category 
(e.g. main menu extensions, login extensions, etc…) and only allow one 
function plugin of a particular category to be enabled at a time for 
appropriate categories.
-Users should have access to a short description of what a function plugin does 
and how to use it from the function plugin toggling interface.

For more info see the project proposal: 
http://dl.dropbox.com/u/20066539/Documents/POSIT/UCOSP_Proposal_Plugin_Manager.o
dt

Original issue reported on code.google.com by RobIan...@gmail.com on 1 Mar 2012 at 10:28

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Original comment by RobIan...@gmail.com on 1 Mar 2012 at 10:35

• Changed state: Started

[GoogleCodeExporter]

Submitted initial implimentation of core requirements.

Original comment by RobIan...@gmail.com on 1 Mar 2012 at 10:42

Attachments:

• Issue340Core.patch

[GoogleCodeExporter]

I've downloaded and installed the patch in my local workspace and I'm in the 
process of testing it.  So far it looks good. 

Original comment by ram8...@gmail.com on 12 Mar 2012 at 12:10

[GoogleCodeExporter]

I pushed the patch that was submitted containing initial functionality.  It 
appeared to work fine.  Let's keep the issue open for subsequent changes. 

Original comment by ram8...@gmail.com on 21 Mar 2012 at 12:19

[GoogleCodeExporter]

When you get a chance, make sure to update the Javadoc comments (for methods) 
and the boilerplates (for new files).  

Original comment by ram8...@gmail.com on 21 Mar 2012 at 12:54

• Added labels: Difficulty-Expert, Priority-High

[GoogleCodeExporter]

Original comment by ram8...@gmail.com on 21 Mar 2012 at 12:57

• Added labels: Repository-Plugin

[GoogleCodeExporter]

-Find plugins and function plugins can now be made unavailable to the user 
through plugins_preferences.xml
-A description of find plugins and function plugins can now be viewed by 
clicking on the question mark buttons.
-Added some Javadoc and boilerplate comments.

Original comment by RobIan...@gmail.com on 23 Mar 2012 at 5:29

Attachments:

• Issue340Additional.patch

[GoogleCodeExporter]

Hi Rob,

I'm having trouble building the project after applying this patch. The culprit 
is probably a missing resource file, question_mark.png?  Can post a copy of 
that resource here.  

(I found a question_mark icon online and I'm using that temporarily.)

Original comment by ram8...@gmail.com on 5 Apr 2012 at 12:45

[GoogleCodeExporter]

This patch is the same as the previous patch but I have removed all of the find 
plugin specific code. Also I have included the question_mark.png image.

Original comment by RobIan...@gmail.com on 5 Apr 2012 at 5:23

Attachments:

• Issue340AdditionalB.patch
• question_mark.png

[GoogleCodeExporter]

Reverted changes to files that were not modified in Issue340AdditionalB so now 
the patches can all be sequentially submitted and everything should work.

Original comment by RobIan...@gmail.com on 5 Apr 2012 at 10:12

Attachments:

• Issue340AdditionalC.patch

[GoogleCodeExporter]

Rob's UCOSP project implemented this enhancement.

Original comment by ram8...@gmail.com on 4 May 2012 at 3:36

• Changed state: Fixed