nobili, philippe wrote: > Many thanks for your reply. > > Actually, valueEditor() works very well; but what you are saying is that > calling 'putAttribute' without passing an attribute value, will exactly do > what we need by poping-up the attribute editor, is it right ? >
Yes, I confirm that. > If so, we had indeed missed this point... Sorry for the misunderstanding, > Best regards. > > ----- Message d'origine ----- > De : Hussein Shafie [mailto:huss...@xmlmind.com] > Envoyé : Monday, June 20, 2011 06:20 PM > À : nobili, philippe > Cc : 'xmleditor-support@xmlmind.com' <xmleditor-support@xmlmind.com> > Objet : Re: [XXE] Does set-attribute-button() makes use of attributeEditor() > ? (XXE 4.9.1) > > On 06/20/2011 05:13 PM, Philippe Nobili wrote: >> 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 ? > > I'm really sorry but we don't see anything wrong about a > command-button() which would invoke command putAttribute. Please notice > that, to my knowledge, command putAttribute does exactly what you have > described: ``pop-up the declared attribute editor if any, the default > one otherwise''. > > Therefore we see your set-attribute-editor-button() simply as a > convenience pseudo-function. We do not intend to implement such > convenience pseudo-function. > > Now, concerning value-editor(), you are welcome to report any > inconsistency, any annoying behavior or any limitation related to this > simple declarative statement. (In fact, I suspect that you have found > something wrong about value-editor().) > > References: > > * http://www.xmlmind.com/xmleditor/_distrib/doc/commands/putAttribute.html > > * > http://www.xmlmind.com/xmleditor/_distrib/doc/csssupport/command-button.html > > * http://www.xmlmind.com/xmleditor/_distrib/doc/csssupport/value-editor.html > > -- > XMLmind XML Editor Support List > xmleditor-support@xmlmind.com > http://www.xmlmind.com/mailman/listinfo/xmleditor-support > > > > -- > XMLmind XML Editor Support List > xmleditor-support@xmlmind.com > http://www.xmlmind.com/mailman/listinfo/xmleditor-support > > -- XMLmind XML Editor Support List xmleditor-support@xmlmind.com http://www.xmlmind.com/mailman/listinfo/xmleditor-support
