This content has been marked as final. Show 9 replies
the thought of storing all of the grid configurations in a special table seems a little odd.Where else would you store it? In an Apex process (CLOB) ? Or somehow encoded "on top" of the regular Apex metadata?
Apex plugins were not yet invented when the jQGrid Integration Kit was developed...
I could see where, if you were going to reuse the same grid across multiple pages then a central configuration may make sense. But since a grid's definition is usually page specific then I would think it should be stored with that page.
How would you store it with the page definition? Since it is NOT a part of the standard APEX page definition? Storing it in a table would seem to be the logical solution...
Unless, some how you want to volunteer to build a plugin to handle doing this in APEX 4.x?
In case anybody else ever has this same question, this was fairly easy to do with jqGrid (and I would imagine it would also be with other jQuery based libraries such as FlexiGrid).
Much easier, and more standard, than messing with database tables. All of the sample and demo code works the same as if you were using a regular web server, which makes it even easier.
In particular, I'm interested to see how you:
* Populate the grid with data from the database
* Handle grid edits (inserts, updates, deletes)
* Handle dropdown lists / LOVs
I haven't done more than get the table to display with pagination working so there may be other issues I run into along the way. I shouild also note that we are using Apex 4.0 and I understand there have been improvements in AJAX processing in Apex 4.2, so that may change things (hopefully for the better).