Actually, I haven't used any tgext stuff so far because I considered it
too unstable and underdocumented to be used in real-world projects. So I
can only comment from an uneducated point of view. But your article
http://blog.axant.it/archives/423 gets me interested again.
As far as I understand, tgext.crud makes use of sprox.dojo which uses a
Dojox.grid.DataGrid via tw.dojo (Dojox is to Dojo what TGExt is to TG).
I think the main problem here is that tw.dojo is pretty much a dead
project - download links do not work and its successor tw2.dojo has not
been released yet and seen no updates for 2 years either. Meanwhile,
Dojo has evolved quite a lot, and there are already two successors
(dgrid and gridx) for the old Dojox grid
(http://www.sitepen.com/blog/2011/10/26/introducing-the-next-grid-dgrid/).
So, I agree that it's best to disable Dojo support in tgext.crud.
Ideally, tw2.dojo and tw2.jquery will be updated, then Sprox will be
updated to use the new Dojo dgrid and alternatively jqGrid, and then
tgext.crud will be made configurable to use plain HTML, dgrid or jqGrid.
But that's a long way to go, and though it sounds interesting, I'm not
sure whether I'll have enough time this year to work on such stuff. I
currently see myself working more and more on client side code and am
not so much using server side frameworks such as TG or TW any more.
-- Christoph
--
You received this message because you are subscribed to the Google Groups
"TurboGears Trunk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/turbogears-trunk?hl=en.
