View Full Version : Containers vs Panels for MVC
bweiler
17 Jan 2012, 10:18 AM
I have been extending Containers for MVC views instead of Panels in my app since the documentation doesn't mention any significant difference between the two and generally higher level components means fewer html div levels. Am I missing something or should I use Containers instead of Panels except for forms and carousels?
Thanks
mitchellsimoens
17 Jan 2012, 11:12 AM
You are correct... the only thing Panel does is add some CSS.
estesbubba
17 Jan 2012, 2:18 PM
At SenchaCon it was mentioned that panels might end up going away in ST2
mitchellsimoens
17 Jan 2012, 2:39 PM
At SenchaCon it was mentioned that panels might end up going away in ST2
Jamie did say that but for now it's not holding weight. We are almost in the beta release where the api is frozen and any release (2.1... 2.2... etc) will need backwards compat with 2.0 so it looks like Panel is sticking around.
edspencer
23 Jan 2012, 6:03 PM
Yea we're not getting rid of Panel - they don't do a lot in ST2 but the pain involved in removing them does not justify the (small) benefits
bweiler
23 Jan 2012, 7:47 PM
I recently discovered that Ext.Panels are required to create floating panels. Extending Ext.Container does not work when creating floating panels.
Powered by vBulletin® Version 4.1.5 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.