Re: [web2py] jqGrid to SmartGrid - Who's made the switch?
I still prefer JQGrid many places. It is the best grid solution in existance still. But now, with the switch to qooxdoo i have to dump it and replace with qooxdoo's table coz it wont fit inside qooxdoo , in design, oo style of programming and UI. I still miss jqgrid and its remote capabilities (filtering , search ,etc) i have to re-implement everything at qooxdoo. Smartgrid still need a lot to reach jqgrid's functionality (in Client side) but web2py helper for it is very powerful. On 2/18/12, Willoughby neil.erik...@gmail.com wrote: Thanks Jim - easier upgrades and lower overhead is definitely an attraction! I guess my next step is to do some quick prototypes and see. Thanks for sharing your experience...
[web2py] jqGrid to SmartGrid - Who's made the switch?
Hello All, I've inherited a site running on v1.61.1 and we're looking at updating/upgrading things. Grids are an integral part of the site and was built extensively with jgGrid including a search plugin, etc. SmartGrid seems to be near the point we need it to be to switch things over smoothly and I think maintenance would be much easier. But on the other hand I've gotten to know jqGrid pretty well...so I'm definitely hesitant to switch from a devil I know... I was curious if anyone on the list has 'done the switch' and would kindly share any 'gotchas' they've run across in doing so. Thanks! -Willoughby
Re: [web2py] jqGrid to SmartGrid - Who's made the switch?
I've made the switch, but I was new to web2py and jqgrid when .smartgrid came out so it wasn't that tough for me. Happily, the result was that my boilerplate code is now about 10x less than it was with jqgrid. .smartgrid isn't perfect, but it works well and was easy to implement. And, I'm suspecting it will improve as time goes on without breaking backward compatibility. -Jim On 2/17/2012 9:04 AM, Willoughby wrote: Hello All, I've inherited a site running on v1.61.1 and we're looking at updating/upgrading things. Grids are an integral part of the site and was built extensively with jgGrid including a search plugin, etc. SmartGrid seems to be near the point we need it to be to switch things over smoothly and I think maintenance would be much easier. But on the other hand I've gotten to know jqGrid pretty well...so I'm definitely hesitant to switch from a devil I know... I was curious if anyone on the list has 'done the switch' and would kindly share any 'gotchas' they've run across in doing so. Thanks! -Willoughby
Re: [web2py] jqGrid to SmartGrid - Who's made the switch?
Thanks Jim - easier upgrades and lower overhead is definitely an attraction! I guess my next step is to do some quick prototypes and see. Thanks for sharing your experience...
