-
1 Nov 2007 10:40 AM #101Tim Ryan
Read BEFORE posting a question / BEFORE posting a Bug
Use Google to Search - API / Forum
API Doc (4.x | 3.x | 2.x | 1.x) / FAQ / 1.x->2.x Migration Guide / 2.x->3.x Migration Guide
-
1 Nov 2007 11:09 AM #102
Well, yes, it's a good point. The samples often display some information about the classes they are demonstrating, and this can become out of date, so, perhaps a general Samples Bugs thread is in order as I don't think there will be that many issues in either code or text.
-
1 Nov 2007 1:42 PM #103
[2.0b1] Ext.Toolbar "items"
[2.0b1] Ext.Toolbar "items"
The "items" config option of Ext.Toolbar isn't documented. (No, seriously.)
T.J. Crowder
tj / crowdersoftware / com
-
1 Nov 2007 1:55 PM #104
It's just a synonym for the "buttons" config, but I'll add it and mention that they're both the same.
-
1 Nov 2007 2:04 PM #105
Well actually neither of them are documented because the default config to Toolbar is just a straight Array of Button configs rather than a standard config object with name/value pairs.
This might change in future. So I'm going to hold off on doc changes. I think this class might change a little as it integrates more and becomes a Container, and the items become proper child Components.
-
1 Nov 2007 7:32 PM #106
Sencha Docs / Ext 3.x - ( Docs | Examples )
Learning Center / Saki's Examples (for 2.x) / HOWTO - ( Report Bugs | Post Proper Code )
-
2 Nov 2007 1:23 PM #107
TabPanel
Config Option enableTabScroll: Number
Should be boolean?
-
2 Nov 2007 3:49 PM #108
Ext.data.Store
Ext.data.Store
Class Ext.data.Store
First few lines should be updated no?
The Store class encapsulates a client side cache of Ext.data.Record objects which provide input data for widgets such as the Ext.grid.GridPanel, or the Ext.form.ComboBox.
-
3 Nov 2007 12:44 PM #109
el not defined for GridPanel
el not defined for GridPanel
As far as I can tell the "el: " config doesn't appear to be defined for Ext.grid.GridPanel.
-
3 Nov 2007 1:44 PM #110
Ext.form.TriggerField
Ext.form.TriggerField
Hi, I think the example
should be changed toCode:trigger.applyTo('my-field');
Code:trigger.applyToMarkup('my-field');
Horst



Reply With Quote