I'm pretty ignorant when it comes to javascript. There's some kind of "addResources" class that seems to have something to do with keeping javascript maintainable (only one instance of each function, maybe also keeping the javascript in separate files). Perhaps you could look into that.
On 11/26/05, Matthias Kahlau <[EMAIL PROTECTED]> wrote: > Hi! > > > Many thanks for the tip. Do you know, if the Javascript generated by the > t:jsValueChangeListener tag is embedded in the target site? Is it possible > to bias MyFaces so that the generated Javascript will reside in an external > file. I might have problems with embedded Javascript, because the app should > run in a portal framework (uPortal), where some characters of embedded > JavaScript are not allowed. > > > Regards, > Matthias > > > > -----Ursprüngliche Nachricht----- > > Von: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Auftrag > > von Mike Kienenberger > > Gesendet: Freitag, 25. November 2005 17:13 > > An: MyFaces Discussion > > Betreff: Re: AW: selectOneRadio and valueChangeListener method with > > onchange submit - submit only after 2nd change > > > > > > I haven't used it, but there's a t:jsValueChangeListener. It may > > already do most or all of what you need. I need to have one that > > also sets some f:param values (or sets some hidden field values) so it > > sets the correct Optional Validation Framework mode, which is why I've > > stuck with the original code on the wiki. > > > > http://myfaces.apache.org/tomahawk/javascriptListener.html > > > > If it doesn't do everything you need, perhaps it could be extended. > > > > On 11/25/05, Mario Ivankovits <[EMAIL PROTECTED]> wrote: > > > Mike Kienenberger wrote: > > > > Your suggestion of calling this.form.submit() may not work. There's > > > > other "hidden" javascript that needs to be executed before form is > > > > submitted. > > > Ok, I understand. > > > Thanks for this information, I'll rework the sample. > > > > > > Thoug, I dont like it to make asumptions about how ids are rendered > > > > > > > > > Thus, this might be a perfect thing for an additional tag, isnt it? > > > > > > <t:jsaction event="onchange" for="select-box-id" > > > action="#{command.action}" /> > > > > > > This will install a "onchange" javascript on the compontent referenced > > > by "for" and (if "onchanged") do some magic to get the command fired. > > > > > > > > > What do you think? > > > > > > > > > Ciao, > > > Mario > > > > > > > >
