Bugzilla – Full Text Bug Listing
| Summary: | [Editor][import] improve usability of add import and add schema | ||
|---|---|---|---|
| Product: | [WebTools] WTP Webservices | Reporter: | May Zhu <mayzhu> |
| Component: | wst.wsdl | Assignee: | Amy Wu <for.work.things> |
| Status: | CLOSED INVALID | QA Contact: | Valentin Baciu <valentinbaciu> |
| Severity: | normal | ||
| Priority: | P3 | CC: | valentinbaciu |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
May Zhu
Changed Version field given new release numbering. This is an issue in the "add import" scenario. It does not completely make sense to open a dialog for the "add schema" scenario (May, what do you suggest we prompt the user for? We could prompt for a namespace, but it's not necessary and will add an extra step for the user). With the "add import" scenario, the user must take that 'extra' step to specify the import location, so it makes sense here. Moving the severity to normal. There is a very simple workaround (Using the properties view). (In reply to comment #2) > This is an issue in the "add import" scenario. It does not completely make > sense to open a dialog for the "add schema" scenario (May, what do you suggest > we prompt the user for? We could prompt for a namespace, but it's not > necessary and will add an extra step for the user). With the "add import" > scenario, the user must take that 'extra' step to specify the import location, > so it makes sense here. > Moving the severity to normal. There is a very simple workaround (Using the > properties view). (In reply to comment #2) > This is an issue in the "add import" scenario. It does not completely make > sense to open a dialog for the "add schema" scenario (May, what do you suggest > we prompt the user for? We could prompt for a namespace, but it's not > necessary and will add an extra step for the user). With the "add import" > scenario, the user must take that 'extra' step to specify the import location, > so it makes sense here. > Moving the severity to normal. There is a very simple workaround (Using the > properties view). Richard,i don't think leaving this to "properties view" is a good solution. My description has explained well about why the problem creates the usability issue. Consistent UI with inconsistent interaction model for user is a frustration especially when their attention has to be relocated to a spot that seems out of their previous concentration scope - the WSDL editor. Yes,you can say that the user finally will locate the "properties view" is a right spot to go, however adding a lightweight dialogue, the same dialogue used in Properties view when clicking the button of add an external schema. I see this is an extra task for the developers not for users:-). For users, it's a speedy way to define an imported schema in a spot handy to them. Hi, I think there's a slight misunderstanding. As stated in comment #2, I agree the "add IMPORT" scenario (right-click in the "Imports" box), is an issue but perhaps not for the "add SCHEMA" scenario (right-click in the "Types" box). Suggestion that if this is still the way the UI is designed..that it might be best to take it through the UI Useability Workgroup at eclipse. Adding investigate to the whiteboard just to serve as a reminder for me to consider this for 3.1. *** Bug 251255 has been marked as a duplicate of this bug. *** I think this bug talks about the old WSDL editor (pre WTP 1.5). In the new editor the user can add an import: - in the source view - in the outline view - automatically, when choosing components from other WSDL documents. The outline view scenario suffers from the same "two step" usability issue. I will close this as invalid and re-open the enhancement Amy marked as a dup of this (bug 251255). Being reopened as an enhancement |