jQuery Grid Plugin – jqGrid

There seems to be a problem with the export function. At least the colModel and the colNames are not exported.

Could some on confirm ?

Thanks.

It seems I hit another weird problem : If I use the new "True srolling" feature (which is real improvement, thanks) with a json response that contains a reference to an image (either hard coded img tag or a div with backgound-url in css) the first batch of row is loaded correctly, but after scrolling the initialy loaded rows, the grid issue an ajax request to the same data (IE same rows and page parameter), than after everything works fine.

So to summarize, I have row 1-30 loaded at grid display, scroll to 31, and it load 1-30 again, then continuing to scroll, data 30-60 are loaded fine. If I remove the img reference, everything works fine.

I hope I was clear enough.

Post edited 16:23 – 09/11/2009 by fuhrysteve

With true scrolling enabled,

sometimes re-appends data to the table without clearing the previous data. (looks like it's happening in populateVisible() to me..).

So far, I've only been able to reproduce this with large table dimensions (tall and wide), and a small number of rows (too few for vertical scrolling).

friflaj said:

Is 3.5 still available? I replaced my copy with 3.6, I want to see if some of the problems I'm seeing are new or if I just overlooked them earlier.

Looks like this is 3.5.3 (last 3.5.x release)
http://www.trirand.com/jqgrid/…..demo35.zip

Source:
http://www.trirand.com/jqgrid/downloads/

Demo files are not available at http://www.trirand.com/jqgrid/…..demo35.zip.

Link name is ok "Demo files (3.6) " but content is wrong (3.5)

Post edited 20:56 – 09/11/2009 by Akeru
Post edited 21:18 – 09/11/2009 by Akeru

@Tony : Please could you have a look here 

http://pastie.org/690809 (test.js)

http://pastie.org/690811 (test.html)

http://pastie.org/690818 (results)

Tests done using Safari4 and Firefox 3.5 on a Mac and Firefox 3.5 on a Linux machine. Export to JSON

I was not sure of the best way to provide you test files, if this is not convenient for you, just tell me what to do.

Thanks.

Post edited 13:44 – 10/11/2009 by jmav
Post edited 13:44 – 10/11/2009 by jmav

Bug with scroll bars, if height parameter is set to "auto" IE7 always show both scroll bars.

If height is set to fix height everything is ok. In FF is ok.

Post edited 16:01 – 10/11/2009 by Akeru

@Tony : I'm the one who should thank you, this was a quick fix !

Could you also have a look and my issue with true scrolling and images ?

@Tony,

After extensive testing, I get the feeling that it has nothing to do with embedded images in data or not. I think it is more related to the number of visible rows in the grid. Please have a look a theses pastie. Setting rowNum to 5 (or 9) instead of 10 triggers the issue.

Test.html is the same as before.

http://pastie.org/693459 – test.js

http://pastie.org/693461 – data.php

Thanks for your time.

bluesky said:

Will the old API be support in future versions ?

It seems all jQuery plugins are evolving in a way where parameters and methods are accessed using 'magic strings'… Won't it make it harder (or even impossible) for IDE's to ever provide for code completion for plugin's like this one ?

I cant speak for whether it will continue to be supported. I cant see why it shouldnt, for those who want it.

But the problem with the old api is that it adds 150+ relatively common function names to the $.fn namespace. How many plugins might want a showCol, setCell or setLabel method, for example?

If you disable the old api (set $.jgrid.no_legacy_api = true after loading the language file, and before loading the rest of the grid), you dont get anything beyond $.fn.jqGrid.

A lot less to worry about every time you add a new plugin to your project…

The other way to do it would be to have $("").jqGrid return a class object, which you then call methods on. But that completely breaks backward compatibility, and isnt really the jQuery way of doing things.

So yes, you do lose code completion in ide's (at least until someone extends it to match the jquery-ui idiom) – but you gain encapsulation – which seems far more important to me…

Mark