I'm following your various commits on Github and I've seen that you've already released the view component for Ext4, but I'm not sure about how to use it as the structure of the code has totally changed (the mvc way :-)
Can we use the "old" .nsf file for the (extnd/3x/Session.js) agent and (extnd/3x/DXLExporter) and other required stuff ?
If you could guide me just a little bit to use the view component with Ext4, I would be more than happy and I'm sure I would not be alone in this case, when we see the popularity of THIS post : http://www.sencha.com/forum/showthre...JSON-parameter
7828 HITS !!!
On top of this, I wonder if you will still keep the DXL exporter agent to feed the ext grids, considering the cpu cost of the agent conversion compared to the built-in readviewentries JSON capabilities (check the post with 7828 hits ...)
I've tested huge views with native readviewentries JSON and the performance really rocks... but my final grid is lacking so many features that, at the moment, I would prefer rely on your great view component.
I am also interested in the "new". nsf to whether it is better to start from scratch or migrate from old version;-)
good day
Don't have a new nsf yet but that's in the works. In the meantime you can use the UIView and UIOutline since they both work now with ExtJS 4.1.3 and higher. (well, mostly work. I forgot to tell you guy about the events that would fire for a grid and a tree and in the old code we would fire custom events and even open docs, etc. into containers you specify. That part isn't working yet)
I'm following your various commits on Github and I've seen that you've already released the view component for Ext4, but I'm not sure about how to use it as the structure of the code has totally changed (the mvc way :-)
Can we use the "old" .nsf file for the (extnd/3x/Session.js) agent and (extnd/3x/DXLExporter) and other required stuff ?
Yes, currently you can still use the 3x agents. All of this code has been tested and works with them.
Originally Posted by Bob Wilson
If you could guide me just a little bit to use the view component with Ext4, I would be more than happy and I'm sure I would not be alone in this case, when we see the popularity of THIS post : http://www.sencha.com/forum/showthre...JSON-parameter
7828 HITS !!!
Sorry about that, I'll add some examples to the docs tonight.
Originally Posted by Bob Wilson
On top of this, I wonder if you will still keep the DXL exporter agent to feed the ext grids, considering the cpu cost of the agent conversion compared to the built-in readviewentries JSON capabilities (check the post with 7828 hits ...)
I've tested huge views with native readviewentries JSON and the performance really rocks... but my final grid is lacking so many features that, at the moment, I would prefer rely on your great view component.
Well, the DXL exporter compliments the ?ReadDesign call and gives more info about the column design...BUT the plan is to allow the developer to pass in their own column config if they wish and if they do, then the calls to DXLExporter and ?ReadDesign can be skipped.