Well, on the matter of jqGrid - we'll see if it works with jQuery 1.4.2; if not, it might be a non-starter. There are other, non-jQuery-based editable grid tools that might be worth looking into - YUI has one, and this one looks quite nice too:


Regardless, I'm not that worried about it because it would be a self-contained tool - no other code would use it, and if there were any problem with it, people could always go back to using the regular multiple-instance-template scheme.

On the general question of using jQuery UI, I looked through the set of plugins we're looking into for the different functionality, and interestingly it seems like the current top choices for all of them doesn't use jQuery UI. So it could be that jqGrid really is the only thing that would require it - which might mean that it's better to keep that library in Semantic Forms.

On the other general question of requiring Javascript - SF already requires Javascript for a number of things, including the multiple-instance-template functionality that jqGrid would be an alternative to. If it were worthwhile to let SF work Javascript-free, that's really a separate discussion; I haven't seen any evidence that it's important to anyone, though.


On Thu, May 27, 2010 at 3:14 AM, Daniel Friesen <lists@nadir-seen-fire.com> wrote:
I'll quote myself from the Gsoc thread since it's relevant.

Daniel Friesen wrote:
> Oh, btw I kinda want to caution on the use of some jQuery libraries,
> especially jqGrid.
> jQuery libraries don't often keep up to date with newer versions of
> jQuery as they come out. Depending on them can hinder the ability to
> upgrade the library. Looking at jqGrid they appear to be sticking with
> an out of date version of an old version of jQuery (1.3.1, the latest
> jQuery is 1.4.2 and the latest 1.3 series was 1.3.2). Also while they
> may abstract some things, they can also lock you in a box, by depending
> on a plugin you can get to a point where you want to do just one small
> extra little thing, but the plugin can't do it and restricts your
> ability to do it yourself. I often ran into that issue when I looked at
> autocomplete plugins.
> jQuery is nice, but plugins can be hazardous, jQuery is best used with
> minimal plugins.

Also when it comes to anything SF related do try to keep in mind the
users without JS. MW works without it, and likewise it shouldn't require
js to edit a page via form. I already spent a deal of work pushing SF
closer towards actually working for users without JS.

~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]

Yaron Koren wrote:
> Hi Daniel,
> This is obviously not the best forum for discussing changes to core
> MediaWiki - I would write to one of the MediaWiki lists about it, or
> talk to the developers on IRC.
> As to whether jQuery UI should be included at all, that's actually a
> reasonable question - I'm just getting started learning about jQuery,
> but it seems that there are usually a bunch of plugins to accomplish
> any specific task, some of which use jQuery UI and some of which
> don't. So the answer may depend on which set of plugins gets chosen.
> One plugin that seems to stands unique in its category, and does use
> jQuery UI, is the jgGrid library, which creates an editable grid that
> could be great within forms:
> http://trirand.com/blog/jqgrid/jqgrid.html
> (Click on "Row Editing > Input types" in the sidebar.)
> One nice thing about jQuery UI is that its file lets you create your
> own version of the file, including only the components you need:
> http://jqueryui.com/download
> ...so if it turns out that there are only a few parts that are
> necessary, it could end up being a rather small file.
> -Yaron