[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [gef-dev] GEF3 resurrection
|
Le 16/02/2022 à 17:11, Serge Rider a écrit :
Hi Team!
I am from the DBeaver development team (https://dbeaver.io). We
develop the universal database management tool based on the Eclipse
RCP platform.
Besides other Eclipse RCP extensions, we heavily rely on legacy
GEF/draw2d.
I was a speaker on several recent Eclipse Cons, the last session was
about legacy GEF adoption:
https://www.eclipsecon.org/2021/sessions/diagrams-eclipse-rcp-back-future
https://www.youtube.com/watch?v=3ZIUB2XFDLE
What we want is to resurrect GEF3 maintenance and include it back to
the standard Eclipse RCP lifecycle.
We have several PRs we'd like to merge in the codebase (currently we
maintain all fixes in our forked repository on GitHub). We also want
to propose legacy API improvements (keeping API backward
compatibility) and several features.
Hi.
This is great news, thanks for the initiative Serge! (Thanks for DBeaver
btw, I use it almost every day and it's a great tool).
As the maintainer of GMF Runtime, I'd like to remind that *a lot* of
projects depend on GEF Legacy (via GMF Runtime or not). In the SimRel
alone there's Graphiti, Sirius (and Capella, even if it's not in the
SimRel), Papyrus, Ecore Tools, and probably others.
Of course improvements would be welcome, and we (in GMF and Sirius) may
able to propose some fixes/improvements we've currently had to make in
our own copies of GEF classes like you, but care must be taken not to
break the many projects which depend on the current behavior (sometimes
in subtle ways).
Regards,
Pierre-Charles David
