[1.2 Beta] Some properties/atributes missing in component config

[wemerson.januario]

Ext.window.Window
# missing iconCls property in Ext Designer and in ExtJs 4.0.2a Doc API

Ext.form.Panel
# missing monitorValid property in Ext Designer and in ExtJS 4.0.2a Doc API
# missing buttonAlign in Ext Designer but its ok in ExtJs Doc API

Ext.form.field.Text
# missing property autoEl in Ext Designer

Ext.button.Button
# missing formBind property in Ext Designer and in ExtJS 4.02a Doc API

Ext.panel.Tool

Strange behavior while you add a tool in Ext.window.Window and click on the tool, This action appears a box with a combo to select the region, but what kind of region? in the ExtJs 4.0.2a does not have this config option in in Ext.panel.Tool

Ext.grid.column.Column
locked property is missing to try Locking Grid Column example

Ext.data.TreeStore
The sorters config property is also missing

 sorters: [{
            property: 'leaf',
            direction: 'ASC'
        }, {
            property: 'text',
            direction: 'ASC'
        }]

Ext.tab.Panel
missing enableTabScroll proprety in Designer and API DOC

Ext.data.Store
groupField property is missing, so I can not test the grouping feature
the model property is also missing

Ext Designer 1.2
Windows 7
ExtJS 4.x framework

Thanks

[jarrednicholls]

Hey Wemerson,

Some of the properties you listed are legitimately missing, and others are omitted on purpose or simply not legitimate (e.g. monitorValid is not a valid configuration option for 4.x Form Panels).

We'll open a ticket and comb through your list here to verify all of them. Thanks!

[jarrednicholls]

Ext.window.Window
# missing iconCls property in Ext Designer and in ExtJs 4.0.2a Doc API

This has been added, thanks.

Ext.form.Panel
# missing monitorValid property in Ext Designer and in ExtJS 4.0.2a Doc API
# missing buttonAlign in Ext Designer but its ok in ExtJs Doc API

monitorValid is not a legitimate Ext.form.Panel configuration. It is now called "pollForChanges".
buttonAlign is a legacy config option and is not valid for Designer 1.2 because Toolbars are created independently and not through the "buttons" config. To align your buttons, use the HBox "pack" config and set to "start", "center", or "end" accordingly.

Ext.form.field.Text
# missing property autoEl in Ext Designer

This is intentional - no field should have its autoEl set, as they have specific renderTpl's

Ext.button.Button
# missing formBind property in Ext Designer and in ExtJS 4.02a Doc API

This is an accidental omission, thanks. It has not been resolved yet in our code base but we'll resolve it before GA.

Ext.panel.Tool

Strange behavior while you add a tool in Ext.window.Window and click on the tool, This action appears a box with a combo to select the region, but what kind of region? in the ExtJs 4.0.2a does not have this config option in in Ext.panel.Tool

This has been resolved, thanks.

Ext.grid.column.Column
locked property is missing to try Locking Grid Column example

This has been resolved, thanks.

Ext.data.TreeStore
The sorters config property is also missing

 sorters: [{
            property: 'leaf',
            direction: 'ASC'
        }, {
            property: 'text',
            direction: 'ASC'
        }]

We're pinging the SDK team to see if this is intended to be a configuration option, or rather just a "property" (as it's documented). Same goes for "groupField" and "groupers". For now, you can easily supply this configuration when you call the sort() method, or after the store has been instantiated; though not optimal.

Ext.tab.Panel
missing enableTabScroll proprety in Designer and API DOC

It is not documented because this is no longer a valid configuration option for tab panels. All Ext.tab.Panel's get overflow scrolling for free, there is no on/off switch.

Ext.data.Store
groupField property is missing, so I can not test the grouping feature
the model property is also missing

groupField: see above re: sorters
model is intentionally omitted because we are not supporting Models and the full MVC stack for Designer 1.2; that will be in Designer 2.0. Designer 1.2 uses the old "fields" configuration on stores. You can of course call setModel() on the store's proxy after it has been instantiated, if that is desired.

Ext Designer 1.2
Windows 7
ExtJS 4.x framework

Thanks

[wemerson.januario]

Thanks Jarred!