Feedback on JQueryDevPlugin

I needed to use to that jQuery UI thing and didn't want to mess up with JQueryPlugin so I created this one. Maybe this one will become obsolete once JQueryPlugin is updated. Now the idea behind this plug-in is also that it merely provides the jQuery library for developer to use on the TWiki platform.

-- StephaneLenclud - 24 Feb 2008

Bad practice to create redundant plugins instead of teaming up and bundle forces.

-- MichaelDaum - 24 Feb 2008

What does this plugin add to the existing JQueryPlugin?

-- ArthurClemens - 24 Feb 2008

White flag! Don't shoot! I don't mind putting all that stuff in JQueryPlugin if you want me to Michael, or feel free to do it yourself if you prefer. I just wanted to get that thing moving fast as I need to deploy it next week on a production server for integration with PerforcePlugin. I asked you last week Michael about the UI and you said you were waiting for the1.5 official release to update JQueryPlugin. Personally I don't mind using the beta as I only need the dialog for now and it seems like it's working just fine. On top of that I just didn't want to break JQueryPlugin, that's all.

It adds jQuery UI, spinner and update jQuery core. It does not provide TWiki variables but merely enable jQuery developer on the TWiki platform.

-- StephaneLenclud - 25 Feb 2008

All your current work would be very welcome on the original JQueryPlugin. Let's merge.

-- MichaelDaum - 25 Feb 2008

How do you want to do that? Do you want me to do it or should I let you handle it?

JQueryDevPlugin is just the js, css and images from the pub directory. Integrating that in JQueryPlugin should be straightforward. It would be great to have an example page in JQueryPlugin combining examples from the JQueryPlugin page and the PluginTestJQueryDevPlugin.

While doing that we probably want to upgrade other js files from jQueryPlugin such jquery.treeview.js if needed.

-- StephaneLenclud - 25 Feb 2008

Please have a look at the files in svn. JQueryPlugin is already updated to jquery-1.2.3. All jquery plugins have been updated as well. There is a test page coming with it that is in the Sandbox web. We can either add more demos to that page or multiple. The current problem with the JQueryPlugin is that it packs every js into one big jquery-all.js ... if you need all plugins on a page or not. That needs to be resolved as adding more plugins, ie as big as UI, will down performance. So for now, I'd say: just move the additional jquery plugins, like spinner and UI to the pub dir, but DON'T add it to the Makefile. Means if you want to make use of UI, you will have to add a <script ...> manually, for now. Likewise, the perl code should not blindly add all js to the header of every page.

-- MichaelDaum - 25 Feb 2008

I understand the the script inclusion problem. I know you were looking at solutions to make it more practical. We will have to find a solution for the UI theme CSS as well.

I'm not sure which of the JS need to be in the head surely the jQuery core but beside that... and what about the theme CSS I think they also need to be in the head ?

Maybe we can have a varJQSCRIPT taking the jquery.myplugin.js file name as parameter to ease script inclusion. I'm not sure having a varJQTHEME will help since I believe it needs to be in the head.

-- StephaneLenclud - 25 Feb 2008

Thanks Stephane for sharing this plugin, and thanks for merging it into the JQueryPlugin. Good dialog here.

-- PeterThoeny - 02 Mar 2008