1) We currently have: builder.js controls.js dragdrop.js effects.js Form.js prototype.js tacos.js 2) They are included in *.script files in net.sf.tacos.ajax.components using: <include-script resource-path="/net/sf/tacos/ajax/components/effects.js" /> See Autocompleter.script, AjaxForm.script, e.t.c.
Chris Norris wrote: > We use tacos stuff in our project, and I'm just learning about it > now. I'm mainly learning about it because I've been working on > another Ajax thing that requires many of the same javascript files > that tacos uses, like effects.js , util.js, etc. I didn't want to > include those scripts twice, so my component now gets those files as > ClasspathResources and adds them as external scripts. > > So I have a few questions: > 1) Does tacos use/require scriptaculous.js at all? > 2) Where in tacos is the code that adds these external scripts? I see > that the AjaxFormSupportImpl adds an external script, but I don't see > where the effects.js and others get added. > > I think that's it for now. > > -chris ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Tacos-devel mailing list Tacos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tacos-devel
