Module or class or library would be the right name for this sort software but i was on the plugin page at the time and focused so much on the word i named it wrong.
Because the jquery methods are saved the first time the code runs the page/site specific code can be checked against it so that you know if a method is present or not. I'm going to try to also cache the number of method arguments so that can be checked too.
Because the page/site specific code is embedded in a server language it would be called every time the code runs so that's why the js code is going to get cached. I still have to figure out how to merge site specific code with page specific code without creating to much files.
So the class not only lets you generate jQuery execution code but also provides basic jquery code checking. For now i'm going to focus on the jquery code itself but later i would add the possibility to check and generate plugin code too.
I hope it's clearer now? John Farrar schreef:
Maybe I am totally missing it. Please clear up my fog. 1. It seems like you are wanting to "Generate jQuery execution code via server pages.". I don't see what is offered by a plugin if that is the case. (Esp. since jQuery doesn't run on the server platforms.) 2. The page caching the code is a server side item. NOTE: I am for implementation techniques. As a CF developer that is something strongly encouraged. It just doesn't make sense that it is labeled as a plugin. (Or is that a common name for them in PHP?) Also, if you would like then I will be glad to help create similar features out as platform implementations... assuming I understand what you mean by plugins. John Farrar
-- David Duymelinck ________________ [EMAIL PROTECTED]
