| Summary: | Egit harms Eclipse UI guidelines | ||
|---|---|---|---|
| Product: | [Technology] EGit | Reporter: | Holger Staudacher <holger.staudacher> |
| Component: | UI | Assignee: | Project Inbox <egit.ui-inbox> |
| Status: | CLOSED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | robin.rosenberg |
| Version: | 1.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Holger Staudacher
It takes time to learn UI guidelines, so anyone who has not spent a *lot* of time designing Eclipse UI's will miss stuff. It would be much easier if you could be specific about the issues you have noticed. Opening an issue on the Staging view pointing out the issues will get them resolved and probably some others too. UI issues may appear differently on different platforms, so the developers may not even see what you see, It's good to get a reminder that such a document exists. I added a section on coding conventions and user interface guidelines to the contributor's guide in the wiki. No specifics |