Why is the current Servoy 7.3.0 based on Eclipse Indigo 3.7 from 22. Juni 2011? The current Eclipse version is 4.3. Is there a special reason for using the old Eclipse?
It would be great if Servoy could be based on newer Eclipse versions, because it would be possible to use newer plugin versions, like EGit 3.1 instead of EGit 2.3.
The surface has changed since their UI is CSS based (and quite a pain TBH), and the performance was abyssal last time I checked.
Hopefully they’ve optimized it, but I’m worried that Servoy Developer will see its performance dive, and as far as I can imagine the leap will be a lot bigger between 7.3 and 7.4 if you go that route than it is between 6.1.3 and 7.3, so that’s why I feel it would be more appropriate to reserve that change to a major version.
ptalbot:
Hopefully they’ve optimized it, but I’m worried that Servoy Developer will see its performance dive, and as far as I can imagine the leap will be a lot bigger between 7.3 and 7.4 if you go that route than it is between 6.1.3 and 7.3
@Paul
I’d be happy to test this on a couple of large workspaces/solutions.
Just let me know when you have a beta version ready to test.
it will not be disruptive at all, its just a drop in replacement that you shouldn’t really notice as a pure servoy developer.
I also didn’t notice much really when i upgraded my Java Eclipse 3.8 to 4.3, the only thing i noticed that the default or chosen theme of the UI was ugly and i needed to choose the right one.
That css is just i think the theme you choose, but all our ui is just as it was before. (and if you choose the classic theme the ui is almost the same)
the performance of Servoy especially with big solutions is not depending on the core of eclipse, but the dltk builder/source parser.