modisposition

I am getting bored ... the cost per use enterprise ready UI library we all heard about has some intrinsic, internal, illogical logic! I already wrote how to hack JsonReader to obtain expected behavior. I have already posted how to solve the TreePanel arrows inconsistency ... what I have never said is that my version of Ext JS is 30% hacked via overrides, extends, or directly in the core and 70% hacked in my application code to make it widely work as expected. The Layout Problem I am constantly trying to fix missed rendered components, layout problems, not visualized stuff ... I am hacking the entire layout process in Ext JS 2. Apparently version 3 with about 1000 fixes and enhancements should have solved layout problem but what I think is: how can be possible that probably the only library with a license for commercial purpose has to be that problematic with layout? The answer is that to make things " delayable " layout s not synchronous. I had then to hack with my timeouts...

I have a new job ( hooooray?! ) and I suggested Ext JS framework as web UI to focus more about Ajax, XML + XSLT data interactions rather than problems with CSS, events delegations, etc ... and I guess I am doing well, so well, that here I am with a simple tiny trick to hack an Ext.data.JsonReader instance, specially the root and the totalProperty params: // directly from Ext JS 2.2 API site // http://extjs.com/deploy/dev/docs/ new Ext.data.JsonReader({ totalProperty: "results", // The property which contains the total dataset size (optional) root: "rows", // The property which contains an Array of row objects id: "id" // The property within each row object that provides an ID for the record (optional) }) Especially for the paginator toolbar, the JsonReader is a must to surf a big amount of data without stressing too much both server and client sides. One nice feature, or one cleve...