Designer limitations I run into

[Phil.Strong]

@timmcintyre writes:

Just wanted to send you a note on the reasons I need to edit externally from the designer.

this is one example of a typeable text field I have that fires a ajax search, it loads a store containing city names

 {
    xtype:'combobox',
    id:'cbCityCode',
    fieldLabel:'City',
    labelWidth:50,
    width:236,
    tabIndex:2,
    allowBlank:false,
    store:ds,
    displayField:'city',
    typeAhead:false,
    minChars:1,
    hideLabel:false,
    hideTrigger:true,
    x:10,
    y:30,
    listConfig:{
        loadingText:'Searching...',
        emptyText:'No records found.',[/SIZE]
        // Custom rendering template for each item
        getInnerTpl:function () {
            return '<p class="search-item" >' + '<b>{city}</b>, ( {code} )' + '</p>';
        }
    },
    pageSize:10,
    stateId:'srchOriginCity',
    value:'Vancouver'
},

I also use the rowexpander plugin in grids of which you cant code from the designer.

apart from that I tend to design my panels & windows individually and add them as items using xtypes, for instance my main viewport would look like this

 initComponent:function () {
        this.items = [
            {
                xtype:"navigation",
                region:"west",
                width:200
            },
            {
                id:"wsCenterPanel",
                xtype:"workspace",
                region:"center",
                layout:'border'
            }
        ];
        this.callParent(arguments);
    }

If any of what ive mentioned above is possible in the designer, please let me know the process as this would be great to contain everything in the designer as I love it as a tool .

I have to say I really love this new Designer 2.0 . .its an evolution on Designer 1.0

Cheers

Tim

[Phil.Strong]

I also use the rowexpander plugin in grids of which you cant code from the designer.

You won't be able to use this fully in Designer until we allow for 3rd party components

However you can always include an outside script and reference it as you always would.

[Phil.Strong]

apart from that I tend to design my panels & windows individually and add them as items using xtypes, for instance my main viewport would look like this

 initComponent:function () {
        this.items = [
            {
                xtype:"navigation",
                region:"west",
                width:200
            },
            {
                id:"wsCenterPanel",
                xtype:"workspace",
                region:"center",
                layout:'border'
            }
        ];
        this.callParent(arguments);
    }

Yes you can do this. Creating top level components and linking them as children to other components aka Linked Instances.

For example you can create a panel and give it a userAlias: 'workspace' and fully configure it to your liking. When your ready you can drag workspace into a Viewport (for instance) and choose to link it. You now have an instance of your workspace component. You can override things or retain the original configs.

See the documentation (not sure if it's ready yet) for help regarding Linked Instances