Well, I have written a treemap implementation in PHP and JavaScript (like the one of SequoiaView - http://www.win.tue.nl/sequoiaview/). And in this application, there is a difference.
Of course, in most applications, there will be no difference. But there are cases, in which you need a fast selector speed, because you have many elements (>1000). The application is workable in a browser, but you need fast algorithms. The question is: can you use jquery, jquery's style and (for me, that's important) can you use the fantastic jquery plugins or do you have to reinvent everything. I think, the jquery community can profit from big applications like the treemap implementation, because in this way, there will be new interesting plugins (all plugins, I have written, are created in combination with this project). So it is necessary, to enable users to use jquery even in complex applications. That's the reason, why I have said, that it doesn't matter, if you use a special performance plugin or not. The only important thing is that you can use the plugins and the programming style. This is much more important than any filesize. Mathias On 3 Apr., 19:06, "Glen Lipka" <[EMAIL PROTECTED]> wrote: > What about the common "Grid"? When you have a table with 100-1000+ rows and > 5-10+ columns and then you want to resize columns, or bind click functions > to them, or enable drag and drop or have collapsable rows, or sorting. > > This is where selector speed should make a difference. The 1.0 version of > Slocums grid should be a perfect real world test. Put 1000 rows in it. > Then use it with a jQuery base, and then a DomQuery base. Does the user see > a differece then? > > Other than that, what are real world examples where it would matter? > > Glen
