On Sun, 17 Aug 2008 04:44:20 +0200, Marshall Culpepper < mculpepper(a)appcelerator.org&gt; wrote: Right, but I'm trying to avoid reinventing the wheel ;) I guess I have no > other recourse? > I guess using rhino or some other javascript interpreter you should be able to do whatever you want in javascript - assuming your javascript spits out something that can be inserted into a DOM tree... To find out where in VPE javascript is disabled/enabled we should hear from Maxim or Sergey which know it better than I. -max > On Sat, Aug 16, 2008 at 11:27 AM, Max Andersen <manderse(a)redhat.com&gt; > wrote: > > This is why you write templates - to simulate the rendering :) >> >> /max (sent from my phone) >> >> On 16/08/2008, at 16.39, "Marshall Culpepper" < >> mculpepper(a)appcelerator.org&gt; >> wrote: >> >> I guess the next logical question is, where can I look to find the >> Javascript disabling code? I've been doing lots of poking around looking >> for >> it, but haven't had any luck... any pointers? >> >> On Fri, Aug 15, 2008 at 9:33 PM, Marshall Culpepper << >> mculpepper(a)appcelerator.org&gt; >> mculpepper(a)appcelerator.org&gt; wrote: >> >> At runtime, our widgets are rendered using Javascript. It would help >>> tremendously if we could execute the same script in VPE so I don't have >>> to >>> reinvent the wheel in Java.... (though calling into JS using Rhino is >>> another option, but I'm guessing nowhere near as effecient) >>> >>> >>> On Fri, Aug 15, 2008 at 6:33 PM, Max Andersen < <manderse(a)redhat.com&gt; >>> manderse(a)redhat.com&gt; wrote: >>> >>> We do what we can to prevent javascript to execute in the editor to >>>> avoid >>>> bad sidesffects -. Why do you need it ? >>>> >>>> /max (sent from my phone) >>>> >>>> >>>> >>>> On 15/08/2008, at 21.25, "Marshall Culpepper" << >>>> mculpepper(a)appcelerator.org&gt; >>>> mculpepper(a)appcelerator.org&gt; wrote: >>>> >>>> Hey guys.. >>>> >>>>> >>>>> I was curious if it's possible to execute javascript by adding >>>>> <script> >>>>> nodes into the head node the same way that <link> nodes are added for >>>>> CSS >>>>> styles. I've created a method that does it for me locally, but the >>>>> script in >>>>> question doesn't seem to be executing... is there something special >>>>> needed >>>>> to make javascript work in this document? Here's my snippet: >>>>> >>>>> public static void addScriptNodeToHead (VpePageContext pageContext, >>>>> nsIDOMDocument visualDocument, String scriptSrc) { >>>>> nsIDOMNode headNode = >>>>> pageContext.getVisualBuilder().getHeadNode(); >>>>> >>>>> nsIDOMElement scriptNode = >>>>> visualDocument.createElement("script"); >>>>> scriptNode.setAttribute("src", scriptSrc); >>>>> scriptNode.setAttribute("type", "text/javascript"); >>>>> >>>>> headNode.appendChild(scriptNode); >>>>> } >>>>> _______________________________________________ >>>>> jbosstools-dev mailing list >>>>> <jbosstools-dev@lists.jboss.org&gt;jbosstools-dev(a)lists.jboss.org >>>>> <https://lists.jboss.org/mailman/listinfo/jbosstools-dev> >>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>>>> >>>>> >>>> >>> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> >> -- -max

Maxim/Sergey, any pointers? 1)For know we are not support execution of java script in visual editor. To allow javascript we should switch off design mode, but know it's hard to do, because all selections events processing throw nsISelectionController which can be obtained only if we switch mozilla in design mode.

2) possibly JavaScript that inserted into head node doesn't be executed automatically, because browser executes this scripts when documents are loaded. When we insert it into DOM, document already loaded.

PS. Using of JavaScript in Visual Editor can strongly change the process handling, because we can modify dom using js, and using xpcom, there then many questins how to map elements from source and visual part and others.

Marshall Culpepper wrote: > >> Maxim/Sergey, any pointers? > 1)For know we are not support execution of java script in visual > editor. > To allow javascript we should switch off design mode, but know > it's hard to do, because all selections events > processing throw nsISelectionController which can be obtained > only if we switch mozilla in design mode. > > > Where is "design mode" turned on and off? So if I understand correctly > ... taking the Mozilla renderer out of design mode turns off the > propogation of nsISelectionController events? org.jboss.tools.vpe.editor.mozilla.MozillaEditor.getEditor(), this method calls from VpeController.init(); To Disable design mode you should comment body of method org.jboss.tools.vpe.editor.mozilla.MozillaEditor.getEditor(). Also for **Preview** tab we using another instance of mozilla , which in browser mode and you can use preview mode, then you shouldn't swicth off design mode. > > > > 2) possibly JavaScript that inserted into head node doesn't be > executed automatically, because browser executes this scripts > when documents are loaded. When we insert it into DOM, document > already loaded. > > > This sounds right, but if I can't execute javascript at all, I guess > it doesn't matter? =) For execution js i have mode following steps(Easy way): 1)create html page with following content / <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> </head> <body> <input type="button" onclick="alert('I am an alert box!!')" value="Display alert box" /> <input type="button" onclick="document.write('Test');" value="Display alert box" /> </body> </html> 2)/ open /org.jboss.tools.vpe.html/templates/vpe-templates-html.xml/ file and add for tag with name="input" to copy attributes /onclick/ attribute. It's should looks like this: <vpe:copy attrs="id,type,style,class,value,size,*onclick*" /> 3) open page which was created in [1] in visual editor. 4) switch to preview tab, and click on submit button on page. JavaScript will be executed. // > > > > PS. Using of JavaScript in Visual Editor can strongly change the > process handling, because we can modify dom using js, and using > xpcom, there then many questins how to map elements from source > and visual part and others. > > > Very true.. Our problem is that the appcelerator platform uses > javascript code to render widgets.. it's sounding more and more like > it would be better to try and approach this using Rhino. I'd still > like to fiddle with the design mode to see what I can accomplish > though, any pointers to source code? I think it's better to use in test purposes preview tab for testing js, in such way it's takes minimal changes.

Max Rydahl Andersen wrote: > Maxim, Marshall is not really asking for enabling javascript in the live > preview...he is asking for away to evaluate javascript so he can actually > generate the corresponding html via javascript instead of manually coding. > > -max > > Then DOM tree can be modifying in using js and dumped to console. To do this need following: 1) disable design mode (Comment body of org.jboss.tools.vpe.editor.mozilla.MozillaEditor.getEditor()) 2) include js into visual document(into head node) 3) run included js, simple way by some action (onclick for submit for example) 4) dump visual dom to console, such fuctionality already exist and use generated html. Marshall Culpepper wrote: >> >>> >>> Maxim/Sergey, any pointers? >>>> >>> 1)For know we are not support execution of java script in visual >>> editor. >>> To allow javascript we should switch off design mode, but know >>> it's hard to do, because all selections events >>> processing throw nsISelectionController which can be obtained >>> only if we switch mozilla in design mode. >>> >>> >>> Where is "design mode" turned on and off? So if I understand correctly >>> ... taking the Mozilla renderer out of design mode turns off the >>> propogation of nsISelectionController events? >>> >> org.jboss.tools.vpe.editor.mozilla.MozillaEditor.getEditor(), this >> method calls from VpeController.init(); >> To Disable design mode you should comment body of method >> org.jboss.tools.vpe.editor.mozilla.MozillaEditor.getEditor(). >> Also for **Preview** tab we using another instance of mozilla , which >> in browser mode and you can use preview mode, then you shouldn't >> swicth off design mode. >> >>> >>> >>> >>> 2) possibly JavaScript that inserted into head node doesn't be >>> executed automatically, because browser executes this scripts >>> when documents are loaded. When we insert it into DOM, document >>> already loaded. >>> >>> >>> This sounds right, but if I can't execute javascript at all, I guess >>> it doesn't matter? =) >>> >> For execution js i have mode following steps(Easy way): >> 1)create html page with following content >> / <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" >> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> >> <html> >> <head> >> </head> >> <body> >> <input type="button" onclick="alert('I am an alert box!!')" >> value="Display alert box" /> >> <input type="button" onclick="document.write('Test');" >> value="Display alert box" /> >> </body> >> </html> >> 2)/ open /org.jboss.tools.vpe.html/templates/vpe-templates-html.xml/ >> file and add for tag with name="input" to copy attributes /onclick/ >> attribute. >> It's should looks like this: <vpe:copy >> attrs="id,type,style,class,value,size,*onclick*" /> >> 3) open page which was created in [1] in visual editor. >> 4) switch to preview tab, and click on submit button on page. JavaScript >> will be executed. >> // >> >>> >>> >>> >>> PS. Using of JavaScript in Visual Editor can strongly change the >>> process handling, because we can modify dom using js, and using >>> xpcom, there then many questins how to map elements from source >>> and visual part and others. >>> >>> >>> Very true.. Our problem is that the appcelerator platform uses >>> javascript code to render widgets.. it's sounding more and more like >>> it would be better to try and approach this using Rhino. I'd still >>> like to fiddle with the design mode to see what I can accomplish >>> though, any pointers to source code? >>> >> I think it's better to use in test purposes preview tab for testing js, >> in such way it's takes minimal changes. >> > > > >

Marshall Culpepper wrote: > Rhino is a possibility, but it seems silly to load 2 seperate > javascript interpreters (Seamonkey for XULRunner and Rhino for Java..) > at the same time when Seamonkey is already available (or at least > could be). > > Maxim/Sergey, any pointers? 1)For know we are not support execution of java script in visual editor. To allow javascript we should switch off design mode, but know it's hard to do, because all selections events processing throw nsISelectionController which can be obtained only if we switch mozilla in design mode. 2) possibly JavaScript that inserted into head node doesn't be executed automatically, because browser executes this scripts when documents are loaded. When we insert it into DOM, document already loaded. PS. Using of JavaScript in Visual Editor can strongly change the process handling, because we can modify dom using js, and using xpcom, there then many questins how to map elements from source and visual part and others. > > On Sun, Aug 17, 2008 at 8:49 AM, Max Rydahl Andersen > <max.andersen(a)redhat.com <mailto:max.andersen@redhat.com>> wrote: > > On Sun, 17 Aug 2008 04:44:20 +0200, Marshall Culpepper > <mculpepper(a)appcelerator.org <mailto:mculpepper@appcelerator.org>> > wrote: > > Right, but I'm trying to avoid reinventing the wheel ;) I > guess I have no > other recourse? > > > I guess using rhino or some other javascript interpreter you > should be able to do whatever you want in javascript - > assuming your javascript spits out something that can be inserted > into a DOM tree... > > To find out where in VPE javascript is disabled/enabled we should > hear from Maxim or Sergey which know it better than I. > > -max > > > On Sat, Aug 16, 2008 at 11:27 AM, Max Andersen > <manderse(a)redhat.com <mailto:manderse@redhat.com>> wrote: > > This is why you write templates - to simulate the rendering > :) > > /max (sent from my phone) > > On 16/08/2008, at 16.39, "Marshall Culpepper" > <mculpepper(a)appcelerator.org > <mailto:mculpepper@appcelerator.org>> > wrote: > > I guess the next logical question is, where can I look to > find the > Javascript disabling code? I've been doing lots of poking > around looking for > it, but haven't had any luck... any pointers? > > On Fri, Aug 15, 2008 at 9:33 PM, Marshall Culpepper > <&lt;mculpepper(a)appcelerator.org > <mailto:mculpepper@appcelerator.org>> > mculpepper(a)appcelerator.org > <mailto:mculpepper@appcelerator.org>> wrote: > > At runtime, our widgets are rendered using Javascript. > It would help > tremendously if we could execute the same script in > VPE so I don't have to > reinvent the wheel in Java.... (though calling into JS > using Rhino is > another option, but I'm guessing nowhere near as > effecient) > > > On Fri, Aug 15, 2008 at 6:33 PM, Max Andersen < > <manderse(a)redhat.com <mailto:manderse@redhat.com>> > manderse(a)redhat.com <mailto:manderse@redhat.com>> wrote: > > We do what we can to prevent javascript to execute > in the editor to avoid > bad sidesffects -. Why do you need it ? > > /max (sent from my phone) > > > > On 15/08/2008, at 21.25, "Marshall Culpepper" > <&lt;mculpepper(a)appcelerator.org > <mailto:mculpepper@appcelerator.org>> > mculpepper(a)appcelerator.org > <mailto:mculpepper@appcelerator.org>> wrote: > > Hey guys.. > > > I was curious if it's possible to execute > javascript by adding <script> > nodes into the head node the same way that > <link> nodes are added for CSS > styles. I've created a method that does it for > me locally, but the script in > question doesn't seem to be executing... is > there something special needed > to make javascript work in this document? > Here's my snippet: > > public static void addScriptNodeToHead > (VpePageContext pageContext, > nsIDOMDocument visualDocument, String > scriptSrc) { > nsIDOMNode headNode = > pageContext.getVisualBuilder().getHeadNode(); > > nsIDOMElement scriptNode = > visualDocument.createElement("script"); > scriptNode.setAttribute("src", scriptSrc); > scriptNode.setAttribute("type", > "text/javascript"); > > headNode.appendChild(scriptNode); > } > _______________________________________________ > jbosstools-dev mailing list > <jbosstools-dev(a)lists.jboss.org > <mailto:jbosstools-dev@lists.jboss.org>>jbosstools-dev@lists.jboss.org > <mailto:jbosstools-dev@lists.jboss.org> > > <https://lists.jboss.org/mailman/listinfo/jbosstools-dev> > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > <mailto:jbosstools-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > > > > > -- > -max > > > ------------------------------------------------------------------------ > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev