Re: [platform-dev] Best approach to branch good old Eclipse 3.8
On Wed, Jan 19, 2022 at 8:59 PM Mário Marinato wrote: > This is what kept us from moving into Eclipse 4 territory. > Then it's a pity because e4 allows you to use your custom renderers for about anything, including views, toolbars... See PartRenderingEngine class for inspiration of how to plug a different renderer for the IDE. Also keep in mind that the features you're implementing might be interesting to some others. In such case, please consider contributing your enhancement directly to Eclipse Platform. ___ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
Re: [platform-dev] Best approach to branch good old Eclipse 3.8
Hi Mario, That can be archived with the rendering framework using custom render. Preventing dragging can be done via tags on the model elements. Check my tutorials at vogella.com or the more guided remote training at learn.vogella.com for details. Best regards, Lars Mário Marinato schrieb am Mi., 19. Jan. 2022, 20:59: > Hello, folks. Thanks for the replies. > > There are two reasons we overrode the Presentation classes. > The first was to implement theming, which we believe can be easily > addressed with Eclipse's new CSS capabilities. > > The second was to boost detached views, adding improvements and features > that Eclipse doesn't offer. > Those include: > - not wrapping our views toolbars: they show a chevron when needed. > - change the Shell that houses them. This Shell doesn't have a title bar > and 'snaps' on nearby Shells when moved or resized. > - add "locked" behavior, when they cannot be dragged around. > > This is what kept us from moving into Eclipse 4 territory. > > Mario Marinato > ~ Rio de Janeiro/Brazil > > > Em qua., 19 de jan. de 2022 às 14:47, Lars Vogel > escreveu: > >> Mario, what do you do with the presentation API? Most of the things >> should be doable with CSS and the rendering framework. >> >> Best regards, Lars >> >> Mickael Istria schrieb am Mi., 19. Jan. 2022, 18:16: >> >>> Hi, >>> >>> On Wed, Jan 19, 2022 at 5:28 PM Mário Marinato >>> wrote: >>> - Upgrade our whole RCP to Eclipse 4 and work on adding back the Presentation classes. >>> >>> Definitely better, by thousands hours of work. >>> Even better would be to re-evaluate whether you can replace your >>> Presentation class by other mechanisms offers by more recent Eclipse, such >>> as theming. >>> >>> HTH >>> ___ >>> platform-dev mailing list >>> platform-dev@eclipse.org >>> To unsubscribe from this list, visit >>> https://www.eclipse.org/mailman/listinfo/platform-dev >>> >> ___ >> platform-dev mailing list >> platform-dev@eclipse.org >> To unsubscribe from this list, visit >> https://www.eclipse.org/mailman/listinfo/platform-dev >> > ___ > platform-dev mailing list > platform-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/platform-dev > ___ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
Re: [platform-dev] Best approach to branch good old Eclipse 3.8
Hello, folks. Thanks for the replies. There are two reasons we overrode the Presentation classes. The first was to implement theming, which we believe can be easily addressed with Eclipse's new CSS capabilities. The second was to boost detached views, adding improvements and features that Eclipse doesn't offer. Those include: - not wrapping our views toolbars: they show a chevron when needed. - change the Shell that houses them. This Shell doesn't have a title bar and 'snaps' on nearby Shells when moved or resized. - add "locked" behavior, when they cannot be dragged around. This is what kept us from moving into Eclipse 4 territory. Mario Marinato ~ Rio de Janeiro/Brazil Em qua., 19 de jan. de 2022 às 14:47, Lars Vogel escreveu: > Mario, what do you do with the presentation API? Most of the things should > be doable with CSS and the rendering framework. > > Best regards, Lars > > Mickael Istria schrieb am Mi., 19. Jan. 2022, 18:16: > >> Hi, >> >> On Wed, Jan 19, 2022 at 5:28 PM Mário Marinato >> wrote: >> >>> - Upgrade our whole RCP to Eclipse 4 and work on adding back the >>> Presentation classes. >>> >> >> Definitely better, by thousands hours of work. >> Even better would be to re-evaluate whether you can replace your >> Presentation class by other mechanisms offers by more recent Eclipse, such >> as theming. >> >> HTH >> ___ >> platform-dev mailing list >> platform-dev@eclipse.org >> To unsubscribe from this list, visit >> https://www.eclipse.org/mailman/listinfo/platform-dev >> > ___ > platform-dev mailing list > platform-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/platform-dev > ___ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
Re: [platform-dev] Best approach to branch good old Eclipse 3.8
Mario, what do you do with the presentation API? Most of the things should be doable with CSS and the rendering framework. Best regards, Lars Mickael Istria schrieb am Mi., 19. Jan. 2022, 18:16: > Hi, > > On Wed, Jan 19, 2022 at 5:28 PM Mário Marinato > wrote: > >> - Upgrade our whole RCP to Eclipse 4 and work on adding back the >> Presentation classes. >> > > Definitely better, by thousands hours of work. > Even better would be to re-evaluate whether you can replace your > Presentation class by other mechanisms offers by more recent Eclipse, such > as theming. > > HTH > ___ > platform-dev mailing list > platform-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/platform-dev > ___ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
Re: [platform-dev] Best approach to branch good old Eclipse 3.8
Hi, On Wed, Jan 19, 2022 at 5:28 PM Mário Marinato wrote: > - Upgrade our whole RCP to Eclipse 4 and work on adding back the > Presentation classes. > Definitely better, by thousands hours of work. Even better would be to re-evaluate whether you can replace your Presentation class by other mechanisms offers by more recent Eclipse, such as theming. HTH ___ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
[platform-dev] Best approach to branch good old Eclipse 3.8
Hello, all. I don't know if this list is the best place to ask this question, but given the kind of thing our team aims to do I believe you might give us good advice. We develop an RCP application that is still based on Eclipse 3.8. We have not updated it because of the various changes made on Eclipse's interface, most notably the removal of Presentation classes. In the last few weeks we've been working on changes to make our application compatible with Java 9+. So far we're happy with what we've done: compile our own versions of both org.eclipse.equinox.launcher and org.eclipse.osgi plugins, making the necessary changes to make our application work. Most of those changes we do are based on the changes made on both plugins on Eclipse 4. But the deeper we dig, the harder things get. And we're thinking about changing our approach. So here's the request for your advice. Which do you think is best? - Keep working to port Eclipse 4 changes into Eclipse 3.8 code (mostly, make Eclipse 3.8's plugins able to handle changes in class loading and multi-release jars and that kind of stuff) or - Upgrade our whole RCP to Eclipse 4 and work on adding back the Presentation classes. Thanks in advance. Mario Marinato ~ Rio de Janeiro/Brazil ___ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
