Sounds like a good idea but people who are doing the real work have final word.
Tom Von meinem iPhone gesendet > Am 19.11.2013 um 20:49 schrieb Joseph D Carroll Jr <[email protected]>: > > Sounds like a great idea! I think this is exactly what we need to > eliminate/keep superfluous elements from the model. For example there could > be an entire tab dedicated towards "tags". That way when you select > different model elements the list of available tags changes. > > Even if there wasn't an immediate usecase, I feel that enhancements like this > will foster innovation moving forward and should be implemented. Though Tom, > Sopot, and others would who invested a great amount of time into the e4 > tooling would have final say, I would certainly support refactoring the code > to support such extensions. > > Let me know if there is anything I can do. > > JD > > >> On Tue, Nov 19, 2013 at 6:05 AM, Marco Descher <[email protected]> wrote: >> Hy List, >> >> WHAT >> >> I would like to add horizontal extension possibility to the e4 tooling. That >> is, there already is the possibility to add new elements to the application >> model, and provide ones own editors >> for the e4 tooling. I would like to extend the tooling for already >> available elements by adding an extension point to the tooling itself. >> >> WHY >> >> I want to enrich already available elements with additional information. >> This could for example be used to add documentation information to all >> elements of the application model, >> or would allow me to e.g. create an additional tab, valid only if I use the >> SWT renderer, allowing me to do deeper inspection of the model. >> >> HOW >> >> I plan to create an extension point allowing to contribute tabs to given >> elements, as can be seen in the following image. The extension point will >> have to define for >> what model elements the contributed tab is valid, and on call of the editor >> the full model will be passed. >> <epaddition.png> >> >> Can you please give me any feedback, on what you think about this, who would >> back/mentor this implementation, and what he/she would do different? >> >> Thanks, >> marco >> >> _______________________________________________ >> e4-dev mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/e4-dev > > _______________________________________________ > e4-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/e4-dev
_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
