Community
Participate
Working Groups
I recently wrote some pieces of code that I use to get a preview of the Draw2d figures with a right-click on the figure class. I find this quite useful, especially when mixing with usage of GMF Tooling, that generates figures that often need some debugging. This previewer is hosted on GitHub and available at Eclipse Marketplace. I think this is probably a step towards a dedicated draw2d tooling. If you think it is relevent to make this code part of Draw2d, then I'd be glad to contribute it, and to have the project hosted at Eclipse and available in release trains. Links to the project: * https://github.com/mickaelistria/Draw2d-Preview * http://marketplace.eclipse.org/content/draw2d-preview
Hallo Michael, that sounds quite interesting. I hope I can find time to have a deeper look into it on the upcoming weekend.
(In reply to comment #1) > Hallo Michael, that sounds quite interesting. I hope I can find time to have a > deeper look into it on the upcoming weekend. And Mickael, sorry for having written your name wrong...
Mickael, that's certainly a nice idea you have picked up here. And as there always have been some inquiries for GEF developer tooling, I think that's something that definitely would be of interest to the community. However, I doubt that contributing the current code basis to GEF would be the best option to take. I think so because of the following reasons: 1) As the feature is rather "young", it will definitely need quite some additional work at the beginning until being really mature, and having contributed the code to GEF, you would be limited to contributing patches alone to help to maintain the code (which will be quite cumbersome if we would also have to go via CQs each time). 2) Having contributed the code to GEF, the GEF committers alone would have the responsibility (and also the duty) of maintaining the code. And while I think that it is quite an interesting thing to have, for me the renewal of GEF itself currently has the highest priority (see bug #347636 for details), so I fear that this could somehow get missed out. 3) Attracting additional contributors could probably be discouraged because of 1) and 2). What about creating an EclipseLabs project (e.g. GEFTools) and contributing the code to it? This would enable the maturation of the current basis and its augmentation in a lot more flexible way. It could also help to attract additional contributors because of a lower entry threshold. We could promote the project on our dev mailing list as well as in our wiki and/or our web pages.
Ok, thanks for your advices.
