EasyShell not compatible with new Eclipse Neon

[belpk]

Eclipse Neon is released yesterday.
But EasyShell can't installed nor used anymore.

Missing requirement: Easy Shell Feature 1.4.2 (com.tetrade.eclipse.plugins.easyshell.feature.feature.group 1.4.2) requires 'org.eclipse.core.runtime.compatibility 0.0.0' but it could not be found

Seems the latest EasyShell release dates from 2014, so I guess this project is dead? So as it doesn't work anymore, I guess that's the end of it?
A shame. Well, time to switch to alternative similar plugins instead...

[anb0s]

Thanks for the report, but the words "A shame. Well, time to switch to alternative similar plugins instead" etc. are no help for me to give more of my spare time for EasyShell development...
Other plugins that i like you can try instead:

• https://marketplace.eclipse.org/content/startexplorer
• https://marketplace.eclipse.org/content/open-explorer
• https://marketplace.eclipse.org/content/path-tools

Anyway i have a working version for Neon and wanted to release it together with Neon, but it will be released in the same week later, see milestone v1.5

[anb0s]

related to #30

[anb0s]

related to https://sourceforge.net/p/pluginbox/bugs/26/

[jctophefabre]

Thanks for your plugin, it is really very useful, I use it for years and it helps me a lot!
Thanks for the time you give to maintain it!

[electrotype]

Same here: thank you very much for this plugin! I use it every day.

[p91paul]

Is there an early binary for the 1.5/2.0 release, or an easy way to build one from source?

[anb0s]

I've an internal alpha version of 1.5 stream that is ONLY for playing with some new features i want to add. BUT this version is not compatible to 1.4.x nor to new 2.0 stream. So if you have own presets, they will not be usable, because of new property-format. It also has possibility to have 3 EasyShell menu instances --> fist enable one instance in preferences:

All three configured intances of EasyShell menus (some entries are duplicates) looks like this:

I will release new v2.0 instead of v1.5 officially, because the interface is clear and simple, but it supports dynamic menus, you can select the tools you want instead of having 4 predefined, see
issue #9 and #14 etc. The v2.0 will automatically migrate or import the user modified 1.3 or 1.4 presets. Also the v2.0 is complete rewrite with EPL license.

So v1.5 will have no future ;) but if you want to use for Neon until v2.0, testing update site: http://anb0s.github.io/EasyShell/testing

v2.0 pre-release will be added during this week...

Thanks!

[electrotype]

Hi anb0s,

I'm not sure in which issue I should suggest this but since you posted those images here... Wouldn't it be nice if one could simply add and remove custom entries, with custom names? You could keep the suggested "templates" but also allow to add/remove any entry?

I suck at photoshop, but something like this:

[anb0s]

Thanks! The version v2.0 that i'm preparing has something similar, one can add, remove, enable/disable predefined and own commands / presets:

I hope it will solve the most requests in this direction, like issue #9 and #14 :)

[electrotype]

Nice!!!

[anb0s]

done at branch v2_0

[electrotype]

I'm currently testing it in Neon and it works well!

1. There is a NPE if you create an item and then change its "type" to "Other" (and you click "OK")
2. Would be nice to list the new names to use as arguments since "{1}", "{2}", etc. don't work anymore.
3. If it can help someone, I primarily use EasyShell to pop Windows Context Menu. To do that, I now use this as my command in Neon:

C:\path\to\WinContextMenu_x64.exe "${easyshell:resource_loc}

"WinContextMenu_x86.exe" and "WinContextMenu_x64.exe" are avaialble there:
https://github.com/vkalviss/WinContextMenu/tree/master/bin

UPDATE: I found that "context.exe" from http://www.maddogsw.com/cmdutils/ works even better than "WinContextMenu_x64.exe": it opens right where the cursor is. Also, the source is available.

Thanks for that 2.0 version!!

[electrotype]

• Another small bug: when you click the "Edit" button for an item, its "type" is always reset to "Open".

[anb0s]

Thank You for the alpha test! So you have builded it by yourself :)

I have more patches to apply and adapt to new codebase from my private work done in 2015, so may be some commits have issues. I will commit it during the week, so please wait for the last one that should be stable and have all UI elements available :) I will put the beta release to testing site, i have to do it step by step...

There is a NPE if you create an item and then change its "type" to "Other" (and you click "OK")
Yes, the new icon path was wrong here --> fixed with next commit

Would be nice to list the new names to use as arguments since "{1}", "{2}", etc. don't work anymore.
Yes, comes with next commit together with other elements of prefernec page (string tokenizer, variable assist etc.)

If it can help someone, I primarily use EasyShell to pop Windows Context Menu. To do that, I now use this as my command in Neon:
C:\path\to\WinContextMenu_x64.exe "${easyshell:resource_loc}
Cool, i will try it too!

Another small bug: when you click the "Edit" button for an item, its "type" is always reset to "Open".
OK, will check it.

Thanks electrotype!

[anb0s]

I have added this v2.0 issues to #50 and will track it there.

[anb0s]

fixed with 6aac781

[anb0s]

v2.0.0 beta 2 build available at site: http://anb0s.github.io/EasyShell/testing
version: EasyShell 2.0.0.v20160719-1230
see issue #54 for found bugs and general discussion

@ALL users: Thanks again for your support :)