nodj / AutoDeriv

eclipse plugin that handle the 'derived' state of resources from a textual file.
http://nodj.github.io/AutoDeriv
Other
29 stars 13 forks source link

There should be option to configure AutoDeriv globally for all workspaces #8

Open michaldo opened 8 years ago

michaldo commented 8 years ago

I'm maven user and I appreciate that my target folder can be easy derived with this plugin. However, I feel uncomfortable, when I have to configure each new workspace.

I would like to configure [target is derived] globally

nodj commented 8 years ago

Hello Michal, It is already possible :) Just add a .derived file into the root directory of your workspace, it should do the trick. Can you try it and tell me if it's fine for you ?

michaldo commented 8 years ago

I know that is possible to add .derived file to workspace root. I use that feature extensively. However, when I create NEW workspace, I have to copy the file to utilize the plugin power.

I'm thininkg about configuration on Eclipse-level, not workspace-level. I'm inspired by http://stackoverflow.com/a/17432147/2365727

nodj commented 8 years ago

Hello again,

My bad, I didn't read your previous message correctly, I thought you were thinking of new projects instead of workspace. I apologize. This is a cool feature, thank you for this suggestion =)

I think I'll try to implement it as the personal dictionary (spelling stuff). I mean, a place in the settings where you set a path to a .derived file. That way, the file can even be shared among several eclipses (I use different eclipses for different stuff, I guess I'm not the only one in that case)

On Thu, Jan 14, 2016 at 3:23 AM, Michal Domagala notifications@github.com wrote:

I know that is possible to add .derived file to workspace root. I use that feature extensively. However, when I create NEW workspace, I have to copy the file to utilize the plugin power.

I'm thininkg about configuration on Eclipse-level, not workspace-level. I'm inspired by http://stackoverflow.com/a/17432147/2365727

— Reply to this email directly or view it on GitHub https://github.com/nodj/AutoDeriv/issues/8#issuecomment-171569808.

michaldo commented 8 years ago

Oh, system-level settings is one step further my dreams. For me Eclipse-level is enough.

For example, eclipse optimizer plugin store his global configuration within $ECLIPSE_HOME/configuration/.settings/com.zeroturnaround.eclipse.optimizer.prefs

nodj commented 8 years ago

The big question for me is: what UI design should I implement. I mean, what should be displayed in the settings page ? I think it would be very strange to have a text editor, with its content saved in prefs. I feel it's better to have a path in prefs, then a standard file (that can be shared via git, edited with notepad++ or...) I'll try that :) Le 14 janv. 2016 12:42, "Michal Domagala" notifications@github.com a écrit :

Oh, system-level settings is one step further my dreams. For me Eclipse-level is enough.

For example, eclipse optimizer plugin store his global configuration within $ECLIPSE_HOME/configuration/.settings/com.zeroturnaround.eclipse.optimizer.prefs

— Reply to this email directly or view it on GitHub https://github.com/nodj/AutoDeriv/issues/8#issuecomment-171719096.

ahoehma commented 8 years ago

I think a "normal" text editor is okay. To save the content in the prefs is also fine.

ahoehma commented 8 years ago

It would be cool to define a "hierarchy" of ".derived" files:

like git, oomph ... what do you think?