You can access the grid by Netzke.page.your_grid_name, where your_grid_name is what you provide as the first parameter to the "netzke" helper in your view. I'll add this bit to the documentation.
------------------
NomadCoder
Netzke Development Team
Follow me on Twitter: http://twitter.com/nomadcoder
Btw, not sure if the old version of Netzke that you apparently are using will have Netzke.page - just check Netzke in Firebug to make sure.
------------------
NomadCoder
Netzke Development Team
Follow me on Twitter: http://twitter.com/nomadcoder
> --
> You received this message because you are subscribed to the Google Groups "netzke" group.
> To post to this group, send email to net...@googlegroups.com.
> To unsubscribe from this group, send email to netzke+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/netzke?hl=en.
>
It seems that the wrapper, a Panel with layout 'fit', is needed only because the GridPanel itself doesn't handle resizing well - I see that the top toolbar does change on resizing, while the rest does not. It's a pity this wrapper is needed - maybe this will be solved in Ext JS 4?
It's possible to incorporate the behavior you created into the component itself. So, you may need to create a Netzke::Base-based component (the wrapper), nest your GridPanel inside of it, maybe pass all the config down to the GridPanel (so that you can use this component just as a GridPanel itself), and then override the onRender method:
js_method :on_render, <<-JS
function(ct){
Ext.EventManager.onWindowResize(this.doLayout, this);
#{js_full_class_name}.superclass.onRender.call(this, ct);
}
JS
This way you'll not need to create another view helper, the logic will be incapsulated in the component.
It seems that the wrapper, a Panel with layout 'fit', is needed only because the GridPanel itself doesn't handle resizing well - I see that the top toolbar does change on resizing, while the rest does not. It's a pity this wrapper is needed - maybe this will be solved in Ext JS 4?
Along with a smarter rendering pipeline, many parts of the new grid have been made into proper Components and integrated into the standard layout management system rather than relying on custom internal markup and CSS. This enables us to unify the grid's rendering process with the rest of the framework, while still retaining a pixel-perfect UI experience.