Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "E4/Tooling"
< E4
| Line 6: | Line 6: | ||
[[https://bugs.eclipse.org/bugs/show_bug.cgi?id=159072 159072]]: Associate target definitions on a per-project basis (multiple target platforms) | [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=159072 159072]]: Associate target definitions on a per-project basis (multiple target platforms) | ||
| + | |||
| + | The question is, what else do people want? What do they envision as the tooling story for e4? | ||
| + | |||
| + | Should we have more templates? There aren't many templates available in Eclipse... how can we make this easier? | ||
Revision as of 12:04, 8 May 2008
In order for e4 to succeed, it will need to have a solid tooling story. There are some outstanding issues in PDE that need to be solved to enable working against the various targets e4 is aiming to support.
Target Platform Issues
[186618]: Target Platforms should be more first class
[159072]: Associate target definitions on a per-project basis (multiple target platforms)
The question is, what else do people want? What do they envision as the tooling story for e4?
Should we have more templates? There aren't many templates available in Eclipse... how can we make this easier?