Jump to: navigation, search

Difference between revisions of "WTP 30 Facets Usability"

Line 11: Line 11:
  
 
Image:
 
Image:
 
+
[[Image:FacetConfigurationPreferencePage.jpg]]
  
 
:*This is a mock up of what the facet configuration could look like.  This is a familiar look and feel based on the eclipse run/debug page.
 
:*This is a mock up of what the facet configuration could look like.  This is a familiar look and feel based on the eclipse run/debug page.

Revision as of 12:32, 18 July 2007

A Proposal...

Imagine a scenario where the generic user never needs to go the facet selection panel. Imagine a scenario, where out of the box, the user just picks a pre-canned product project configuration and then hits finish from the first page of the new project wizard. Imagine a scenario where an advanced user maybe could have a team with one facet guru, who would be responsible for defining the custom configurations his team would use on a day to day basis to create faceted projects. This guru would open a configurations editor in the workbench preferences, select the facets he wants, save that configuration, and then export it using workbench preferences. Other team members could then import the configurations and decide which ones they want to show up in their new project wizards. Then, all they ever need to do is select the appropriate configuration from the first page of the project wizard and theoretically, hit finish right from there.


Please note the following screen mock-ups are not meant to be of pristine quality, but rather general thoughts on direction to take the wizards. It is understood visual clean up is necessary.

The Configuration Editor

The pre-defined "typical" configurations will be key. Adopter products could extend and ship with additional configurations, but WTP should have just enough base configurations. The idea is that the configuration editor really does stay an advanced option. But, we do want to make the configuration editor as easy to use as possible because we cannot assume everyone will have a "facet guru".

Image: FacetConfigurationPreferencePage.jpg

  • This is a mock up of what the facet configuration could look like. This is a familiar look and feel based on the eclipse run/debug page.
  • The facet configuration editor could create new configurations, edit existing ones, and they will show nested under the primary project type for ease of use. For usability when creating a new configuration, the facet list is filtered by what is applicable to the primary project type.
  • These configurations would then be exported for use by each team member to import to their own workspaces. So, the idea is not every user would have to use this editor and be worried about such details.


Back to Web Tools Wiki Home