Issue 114: Add an option to enable/dissable plugins in mixare and/or launchers
Project Member Reported by abdu.e...@gmail.com, May 9, 2012
Currently, mixare starts all available plugins directly until they are uninstalled. This could let to problems like forgotten plugins that are still activated in mixare.

Another problem is that lauchers can not decide them self wheither they want plugins or not. It should be easier for launchers to choose wheither they want plugins or not. And also the ability to decide which plugins they want.

Thanks to:
https://groups.google.com/forum/?fromgroups#!topic/mixare-development/IlTlXY0O96U


May 10, 2012
#1 DevBinn...@gmail.com
Thats right, what about if we merge plugins with the dataSource,
so it should be treated as a source, a user can activate or deactivate the plugin when they wanted.

What's your thought. 
May 11, 2012
Project Member #2 abdu.e...@gmail.com
Doesn't that mean that every datasource needs its own plugin? Though datasources are connected to plugins. It currently works like this:

There are dataselector plugins, that can return a datasource, or the user can add its own datasources in the arrays.xml, or through the mixare app.

There are also marker and datahandler plugins, they work together. The datahandler plugin checks if the url of the datasource, or the content of the datasource matches its criteria. If they match, then the datahandler will process that datasource and creates the markers.

This way, the plugins are only activated, when they are used.

I think its better if I write a technical documentation about this, so that everyone can discuss about this structure (issue116).
May 12, 2012
#3 DevBinn...@gmail.com
I see what you mean. I'll take a look at it and see what we can do about it.

In the mean time, and for such expanding project, I would HIGHLY recommend documenting newly created classes as it helps the developer who created them and the new comers.

 
May 12, 2012
Project Member #4 abdu.e...@gmail.com
I totally agree with you about that. For that reason I created issue116.
May 18, 2012
Project Member #5 abdu.e...@gmail.com
(No comment was entered for this change.)
Status: Fixed