Dear Mr. Shafie,
The new <attributeEditor> is very good; from the recent tests we have
made, it appeared to be a very simple yet powerful way to significantly
improve the add-ons we wrote for our XML dialects.
Our only regret is that the <attributeEditor> declarations are used to
improve the generic attribute editor, but are not used to improve the
controls inserted in generated content.
E.g.:
In *xxxx.xxe*, we declare an *attributeEditor* for attribute @idref in
<grpref>; it fetches only the @id attribute of <grp> elements, but
display also their @name for more clarity:
<attributeEditor attribute="idref" elementMatches="geov:grpref">
<list selectItems="//geov:grp" itemValue="@id"
itemDescription="geov:nativeDescript/@name"/>
</attributeEditor>
It would be very attractive to be able to use the same customization in
the generated content instead of having to write a totally different
command, e.g.:
value-editor(icon,url(icons/select.png),tool-tip,'Select a
group',attribute,"idref")
Would bring the customized value editor for attribute "idref" instead of
the default text field; this might be driven by an extra parameter in
value-editor for example.
Would it make sense ?
Best regards.
--
XMLmind XML Editor Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
