Summary: | Module Assembly page entries not editable with keyboard | ||
---|---|---|---|
Product: | [WebTools] WTP Common Tools | Reporter: | Kaloyan Raev <kaloyan> |
Component: | wst.common | Assignee: | Rob Stryker <stryker> |
Status: | NEW --- | QA Contact: | Carl Anderson <ccc> |
Severity: | major | ||
Priority: | P2 | CC: | cbridgha, shr31223, stryker |
Version: | unspecified | Keywords: | accessibility |
Target Milestone: | 4.0 | ||
Hardware: | PC | ||
OS: | Windows Vista | ||
Whiteboard: |
Description
Kaloyan Raev
2010-02-05 10:37:10 EST
Assigning to Chuck for initial investigation. Moving this to M7, may need some assistance from Rob.. Possibly a special keystroke to enter edit mode Targeting to generic 3.2. If someone can offer me advice on how to do this I can look into it, but until then it's only tentatively planned for 3.2 and if no advice comes will be retargeted to later The most natural way I see for the moment is to use the Edit button. When the user click the Edit button, the current selection in the table will switch to edit mode (like the user has clicked on the left cell). This would be a good use of the Edit button, which is currently disabled. The edit button is *not* currently disabled. it is currently disabled for any reference type which does not have an edit action associated with it. For other reference types, such as filesets, or any custom reference type created by adopters, 'edit' will open a wizard (same wizard as add) with the page which claims to be able to edit that reference type. Adding such an editor for project / jar / external jar references would be trivial but ultimately pointless because editing a reference from ProjectA to ProjectB would be functionally equivalent to simply removing the ProjectA reference and adding a new ProjectB reference. However for any other custom reference implementation with lots of parameters, such as a fileset, this is not the case. For example assuming a fileset has basedir, includes, excludes, flatten, etc as parameters, and you want to change just one (the includes pattern), to delete that reference and add a virtually identical one with a slightly changed includes pattern is overburdening to the user. Hence, the edit button. So the edit button cannot be used to enable modifying the deploy path and a different way must be found. I cannot think of a good way to implement this now, being as the 'edit' button has its own other uses. Without some more suggestions as to a convenient and clean way to allow the user to edit the field, I'm left with pushing this forward |