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 "Eclipse UI Outlet"
m |
|||
| Line 1: | Line 1: | ||
| − | This | + | This article describes a proposal for creating an outlet for Eclipse User Interface design. The idea is to provide a community driven ''thing'' which can be used by all Eclipse projects to improve their user interface. |
| − | == Proposal A == | + | == Proposal A - Make it an Eclipse project == |
One way that ''thing'' could work is using a regular Eclipse project. | One way that ''thing'' could work is using a regular Eclipse project. | ||
Revision as of 09:22, 26 July 2007
This article describes a proposal for creating an outlet for Eclipse User Interface design. The idea is to provide a community driven thing which can be used by all Eclipse projects to improve their user interface.
Proposal A - Make it an Eclipse project
One way that thing could work is using a regular Eclipse project.
Why?
Because we would leverage the existing infrastructure and the existing processes.
How?
- Eclipse Bugzilla will be used for:
- Submitting User Interface assistant requests
- Discussing issues and their solutions
- Attaching solutions as patches
- Eclipse CVS/SVN will be used for:
- Publishing common staff like
- Icons
- Design templates/examples
- Code templates/snippets
- ...
- Developing tools/scripts that would help this thing
- Publishing common staff like
- Eclipse Wiki will be used for:
- Project website
- FAQ
- ...
- Eclipse Blogs will be used for:
- Community engagement