On 06/17/2011 02:57 PM, Philippe Nobili wrote:
On 06/17/2011 01:02 PM, Hussein Shafie wrote:
The screenshots you sent me show a set-attribute-button() working as
expected. Its dynamically created menu items are not supposed to display
any information beyond the bare IDs.
Rationale: in most cases, very wide menu items (i.e. containing both the
IDs and their descriptions) would make the menu unusable.
If you want to display both the IDs and the text snippets describing
these IDs, please use a command-button() invoking the putAttribute command.
Dear M. Shafie,
To come back on this issue, we understand the rationale above; for
consistency reasons (and to save coding time), we believe that it is
however interesting to be able to reuse the same attribute editor from
either the attribute panel, or the generated content.
So what the following development suggestion ?
*Description:* Provide a function, e.g. 'set-attribute-editor-button'
which pops-up the declared attribute editor if any, the default one
otherwise.
*Rationale:* Reuse the same attribute editor from both places, from a
simple declarative statement (valueEditor).
Would it make sense ?
Many thanks for your feedback.
Philippe.
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
