Usability/Documentation: Preferences/Default Schema Associat
Posted: Fri Jul 28, 2006 1:28 pm
I'm generally a very happy user of oXygen, though I've just stumbled across a patch of poor usability which has made me rather grumpy. Please bear with me.
Dialog: Preferences/Default Schema Association
* Column namespace: (Documentation)
Supposing I want this association to be used when no namespace is declared. What do I do? Leave it blank? Write <NONE>, write <ANY> (even though that's not what I want) or do something else? The documentation of this feature is insufficient.
* Buttons:
I recently entered a number of very similar patterns (Associating a schema without a namespace with the 8 possible root elements of that schema). I accomplished this by first exporting the preferences, then hacking the resulting xml and then re-importing. A simple Duplicate button would have been very helpful.
* In-place Editing:
It would be convenient to be able to edit the values in the table in place. Failing that, you could use the yawning gulf at the bottom half of the window to show an edit view for the currently selected row.
* Yawning gulf at the bottom of the window
How about allowing the table to grow vertically to fill the available space?
* Column "Root local name": Documentation? RegEx? XPath?
What I was doing my repetitive data entry, I thought "gee, wouldn't it be nice if I could use a subset of XPath or a regular expression here, that would save me a lot of typing." Who knows, maybe I could have. Again, with the documentation!
Thanks
Ben
Dialog: Preferences/Default Schema Association
* Column namespace: (Documentation)
Supposing I want this association to be used when no namespace is declared. What do I do? Leave it blank? Write <NONE>, write <ANY> (even though that's not what I want) or do something else? The documentation of this feature is insufficient.
* Buttons:
I recently entered a number of very similar patterns (Associating a schema without a namespace with the 8 possible root elements of that schema). I accomplished this by first exporting the preferences, then hacking the resulting xml and then re-importing. A simple Duplicate button would have been very helpful.
* In-place Editing:
It would be convenient to be able to edit the values in the table in place. Failing that, you could use the yawning gulf at the bottom half of the window to show an edit view for the currently selected row.
* Yawning gulf at the bottom of the window
How about allowing the table to grow vertically to fill the available space?
* Column "Root local name": Documentation? RegEx? XPath?
What I was doing my repetitive data entry, I thought "gee, wouldn't it be nice if I could use a subset of XPath or a regular expression here, that would save me a lot of typing." Who knows, maybe I could have. Again, with the documentation!
Thanks
Ben