search

thanawat158 / mixare

Automatically exported from code.google.com/p/mixare
0 stars 0 forks source link

Add an option to enable/dissable plugins in mixare and/or launchers #114

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
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/IlTlXY0O96
U

Original issue reported on code.google.com by abdu.e...@gmail.com on 9 May 2012 at 12:55

GoogleCodeExporter commented 8 years ago 
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.

Original comment by DevBinn...@gmail.com on 11 May 2012 at 12:32

GoogleCodeExporter commented 8 years ago 
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).

Original comment by abdu.e...@gmail.com on 11 May 2012 at 10:09

GoogleCodeExporter commented 8 years ago 
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.

Original comment by DevBinn...@gmail.com on 12 May 2012 at 7:14

GoogleCodeExporter commented 8 years ago 
I totally agree with you about that. For that reason I created issue116.

Original comment by abdu.e...@gmail.com on 12 May 2012 at 10:01

GoogleCodeExporter commented 8 years ago

Original comment by abdu.e...@gmail.com on 18 May 2012 at 8:28