Community
Participate
Working Groups
It would be good IMHO if the tooling (Toms Editor and the wizards) could be moved to git.
I'm +1 on this - I'll prepare a list of bundles we'd need to move.
Cool. I hope this will help others (including myself) to help out in the tooling area.
With the work being done in bug 345471 and bug 345479 post 4.1/0.11 might be the ideal time to do it, or at least organize what must be moved. PW
Like stated before I'd really welcome moving to git. What we should consider is that the e4 brigde we talked about to leverage in 4.2 to refactor some of our ui.workbench-code is currently developed as part of the tooling effort. Beside that I really hope that we'll push the e4 tooling forward more in 4.2 so that it can graduate. PDE could be a potential candidate but to make that happen I need help from others because I simply don't have enough resources.
A component I'd like to add in 4.2 here is an CSS-Editor written using Xtext. I already wrote one just the other day for my JavaFX-work. Maybe it could even replace the batik and css stuff we currently consume from Orbit?
(In reply to comment #5) > A component I'd like to add in 4.2 here is an CSS-Editor written using Xtext. I > already wrote one just the other day for my JavaFX-work. CSS editing support seems to make sense to me in 4.2/0.12. But the batik stuff doesn't supply an editor, it's about multiple CSS stylesheet processing IIRC. PW
... but if you write an editor using Xtext you naturally also get a parser genersted because all Xtext does is to create an in memory EMF-Model from the textual representation ;-)
(In reply to comment #7) > ... but if you write an editor using Xtext you naturally also get a parser > genersted because all Xtext does is to create an in memory EMF-Model from the > textual representation ;-) But it's not just the parser ... it's the knowledge that when you ask for .body "here" you get one definition, but when you ask for .body "somewhere-else" you get a hierarchical .body definition because it read some parent stylesheets as well. PW
(In reply to comment #5) > A component I'd like to add in 4.2 here is an CSS-Editor written using Xtext. I > already wrote one just the other day for my JavaFX-work. Wouldn't that conflict with the one we've had in WTP since '04? Is it not worth just adding onto that editor in some way?
I've created a test repo at git://git.eclipse.org/e4/org.eclipse.e4.tools.git PW
(In reply to comment #10) > I've created a test repo at git://git.eclipse.org/e4/org.eclipse.e4.tools.git git://git.eclipse.org/gitroot/e4/org.eclipse.e4.tools.git
OK, I've created a real tools git repo. git://git.eclipse.org/gitroot/e4/org.eclipse.e4.tools.git I have not converted the map file yet to use the new repo, but any new changes you wish to contribute should go here. PW
technically post 4.1 and in 0.12 PW
Fixed long time ago.
