Bugzilla – Full Text Bug Listing
| Summary: | Context-sensitive view with possible high level actions | ||
|---|---|---|---|
| Product: | [WebTools] WTP Java EE Tools | Reporter: | Kaloyan Raev <kaloyan> |
| Component: | jst.j2ee | Assignee: | Kaloyan Raev <kaloyan> |
| Status: | NEW --- | QA Contact: | Chuck Bridgham <cbridgha> |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | kaloyan |
| Version: | unspecified | Keywords: | usability |
| Target Milestone: | Future | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| URL: | http://wiki.eclipse.org/WTP_UX_Whiteboard#Context-sensitive_view_with_possible_high_level_actions | ||
| Whiteboard: | UX | ||
Pain point Developing an end-to-end Java EE scenario involves many steps. It is a common situation for non-experienced Java EE developers to ask themselves: "OK. I have generated the JPA entity for my DB table. Now, what's next?". It is true that the context menus of the editors and Project Navigator contain Java EE-specific actions, but they are somehow lost for the user in the whole bunch of context-menu actions. Solution The Java EE perspective should provide a special view that guides and hints developers with the possible Java EE-specific steps they could execute. For example: "Generate Session facade for JPA entity". Here are some of the characteristics that should be required for the view: * Context-sensitive. Only the actions relevant for the current (on focus) artifacts should be displayed in the view. * Sections. Available actions should be grouped in sections by relevance criteria, e.g. JPA, JSF, EJB related actions. * Extensibility. Adopters should be able to contribute their own specific actions and sections to the view.