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 <lars.vo...@vogella.com> 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 <mist...@redhat.com> schrieb am Mi., 19. Jan. 2022, 18:16: > >> Hi, >> >> On Wed, Jan 19, 2022 at 5:28 PM Mário Marinato <mariomarin...@gmail.com> >> 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
