mandatory task

[qotsa]

First of all, I'd like to say you did good job with workspacemechanic, I recently tried it and have to say it's nice plugin. 

We decided to deploy it in my company but to match perfectly our goals, we'd like another feature that would be a kind 

of mandatory task. I mean a task that user can't refuse and without he have to click anything.

I had a look to the road map and didn't notice any new functionnality like that. 

We really need it so if you won't, we'll dev it and share our work with community.

I'll take a look to the code and make a first purpose in a few days, hope you'll help us ;)

[Mats Rappe]

Please share. I think it would be a good addition to have.

[Robert Konigsberg]

http://code.google.com/a/eclipselabs.org/p/workspacemechanic/issues/detail?id=33&can=1

If it's a preference task then you should just have shared preferences then consider using plugin_customization.init [1]. If it's a custom-build task type, then you can just basically implement the changes during evaluate(), which I don't really recommend.

Keep in mind that the design goal of WM was to center around user choice; with the notion of a centrally-managed team dealing with mandatory configuration [1]

[1] http://code.google.com/a/eclipselabs.org/p/workspacemechanic/wiki/DesignGoals

--
Robert Konigsberg