Ulrich_Laegeler at arburg.com wrote:
> Hello Hussein,
>
> ok, now i understand the value-editor issue.
>
> How do you think is the performance of XmlMind
> if i use xs:string attributes with value-editors compared
> with the usage of xs:string elements rendered as "normal" content.
>
Nothing can beat "normal" content in XXE.
xs:string elements rendered as "normal" content is, in all aspects
(speed, memory size but also usability), more efficient than xs:string
attributes rendered using value-editor()s.
>
> Von: Hussein Shafie <hussein at xmlmind.com>
> An: Ulrich_Laegeler at arburg.com
> Kopie: "xmleditor-support at xmlmind.com" <xmleditor-support at
> xmlmind.com>
> Datum: 26.03.2010 15:36
> Betreff: Re: [XXE] Antwort: Re: value-editor control
>
>
>
> Ulrich_Laegeler at arburg.com wrote:
>> i pop up once more this old issue.
>>
>> I have a normal text value-editor() for a xs:string attribute.
>>
>> If i press the right mouse button with the inside this editor
>> the mouse event is not passed thru to the document view.
>> As a result my binding for the mouse button 3 is not executed.
>>
>> It doesn't make any difference if the text value-editor is activated
>> or not.
>>
>> I think this event should be passed thru so that my binding is executed,
>> or am i wrong.
>>
>
> I've already answered your question about this. There is no bug we can
> fix here. It simply cannot work with a value-editor() or any other
> built-in ``form control'' generated by the CSS.
>
> XXE bindings work only in the document view. value-editor() creates an
> ``alien island'' within the document view where XXE bindings no longer
> apply.
>
>
>> Best regards, Uli
>>
>>
>>
>>
>> Von: Hussein Shafie <hussein at xmlmind.com>
>> An: Ulrich_Laegeler at arburg.com
>> Kopie: "xmleditor-support at xmlmind.com"
> <xmleditor-support at xmlmind.com>
>> Datum: 15.12.2009 12:49
>> Betreff: Re: [XXE] value-editor control
>>
>>
>>
>> Ulrich_Laegeler at arburg.com wrote:
>>> the value-editor control
>> There is no value-editor control per se.
>>
>> ---
>> foo {
>> content: value-editor();
>> }
>> ---
>> means: create whatever form control (text field, combobox, list, etc)
>> that can be used to edit the content of the element which is the subject
>> of the CSS rule. Of course, value-editor() needs a schema to do its job.
>>
>> See
>> http://www.xmlmind.com/xmleditor/_distrib/doc/csssupport/value-editor.html
>>
>>
>>
>>> grabs the mouse button 3
>>> with which i want to popup a context menu.
>>> Is it possible to pass thru this mouse event to the application?
>> I'm not sure to understand.
>>
>> [A] Do you want to create your own context menu, which would be specific
>> to the embedded form control?
>>
>> [B] OR do you want a right-click on a embedded form control to display
>> XXE's edit menu?
>>
>> --> [A] is possible by specifying:
>>
>> foo {
>> content: component("your AWT/Swing Component factory here");
>> }
>>
>> How to do this is easy and fully documented:
>>
>> * See
>> http://www.xmlmind.com/xmleditor/_distrib/doc/csssupport/component.html
>>
>> * See
>>
> http://www.xmlmind.com/xmleditor/_distrib/doc/api/com/xmlmind/xmledit/styledview/ComponentFactory.html
>
>>
>> * See http://www.xmlmind.com/xmleditor/_distrib/doc/dev/styleext.html
>>
>>
>>
>> --> [B] is *probably* possible by specifying:
>>
>> foo {
>> content: gadget("your Gadget factory here");
>> }
>>
>> See http://www.xmlmind.com/xmleditor/_distrib/doc/csssupport/gadget.html
>>
>> Unfortunately, how to develop Gadgets is not documented (and will
>> probably never be). Moreover in the case of embedded form controls, the
>> Gadgets created by the factory should use a special technique[*] which
>> makes all this even more difficult.
>>
>>
>>
>> ---
>> [*] In fact, the Gadget displays an image (i.e. screen capture) of the
>> form control and not the actual form control. The actual form control is
>> temporarily created when the Gadget gets the keyboard focus (Tab to or
>> click on the Gadget). The actual form control is destroyed and replaced
>> by its image when the Gadget looses the keyboard focus.
>>
>> This allows a styled document view to efficiently embed thousands of
>> form controls.
>>
>
>
>
>
>
>
> ARBURG GmbH + Co KG, Postfach 1109, D-72286 Lo?burg, Arthur-Hehl-Strasse,
> D-72290 Lossburg, Telefon: 07446 33-0, Telefax: 07446 33-3365,
> http://www.arburg.com, contact at arburg.com.
> Registergericht: AG Stuttgart, HRA 430209, USt-Id-Nr. DE 144 252 064,
> Komplement?r: Hehl Verwaltungs-GmbH, AG Stuttgart, HRB 430155.
> Gesch?ftsf?hrer: Eugen Hehl, Karl Hehl, Michael Hehl, Juliane Hehl, Renate
> Keinath, Herbert Kraib?hler, Michael Grandt, Helmut Heinson.
>
> Diese E-Mail einschlie?lich ihrer Anh?nge ist vertraulich und daher allein
> f?r den Gebrauch durch den vorgesehenen Empf?nger bestimmt. Dritten ist das
> Lesen, Verteilen oder Weiterleiten dieser E-Mail nur mit ausdr?cklicher
> Zustimmung erlaubt. Wir bitten, eine fehlgeleitete E-Mail unverz?glich
> vollst?ndig zu l?schen und uns eine Nachricht zukommen zu lassen. Sofern
> diese E-Mail oder ihre Anh?nge Informationen enthalten, die erkennbar von
> Dritten stammen, ?bernimmt ARBURG GmbH + Co KG, die Gliederungen und T?chter
> keine Haftung f?r diese. Insbesondere macht sich ARBURG GmbH + Co KG diese
> Informationen nicht zu Eigen.
> This email may contain material that is confidential, privileged and for the
> sole use of the intended recipient. Any review, reliance or distribution by
> others or forwarding without express permission is strictly prohibited. If
> you are not the intended recipient, please contact the sender and delete all
> copies. ARBURG GmbH + Co KG, its branches and subsidiaries herewith exclude
> any liability for third-party information recognizably contained in this
> e-mail or its attachments. Third-party information does not necessarily
> reflect the opinion of ARBURG GmbH + Co KG.
>
> --
> XMLmind XML Editor Support List
> xmleditor-support at xmlmind.com
> http://www.xmlmind.com/mailman/listinfo/xmleditor-support
