29 Feb 2008 3:14 PM #1
Why use a native Ext.AIR window?
In the AIR Tasks V2 blog entry Jack says "NativeWindow: This was one of the most useful additions to the Ext.air package.".
Conceptually I don't understand this comment. I assume a standard Ext window is just a collection of DOM DIVs formatted to resemble a classic modal window and hence quite resource efficient. Using an Ext.air window presumably instantiates a new instance of a browser control in the new native window. Why is this preferable?
1 Mar 2008 2:04 PM #2
My guess would be that NativeWindows are a lot more efficient than the regular Ext window. Try creating ,say, 10 large Ext Windows and drag them around. You'll see that they are very sluggish. This would not be the case with NativeWindow.
SanjivGWT-Ext Widget Library
1 Mar 2008 5:45 PM #3
NativeWindow is useful when you need chromeless window and it can minimize to system tray. It suppose to be the main window in your applicationSpket IDE - Development Tool for RIA
1 Mar 2008 9:16 PM #4
If you want to use Ext.Windows, they are obviously even easier. However, if you are working with NativeWindows, Ext.air.NativeWindow makes it much less painful.Jack Slocum
Sencha Co-Founder, Ext JS Founder
Original author of Ext JS 1, 2 & 3.