MVC Controller ref store or pollingprovider

[Green]

Hi,

I have tried various permutations, but can not figure out how to ref either a store or pollingprovider in my app.Controller. I even tried to autoCreate these components within the controller but without success. Creating them in the app.Launch works just fine, but then I can't "ref" them and hook their events. Any help would be welcome, tia.

Ext.define('MyApp.controller.ctrlMain', {
    extend: 'Ext.app.Controller',
    config: {
        refs: {
            sightTab: 'tabbar button[iconCls=search]',
            tweetTab: 'tabbar button[iconCls=chat3]',
            sightstore: '#storeSightings', // which I added both as id and storeId to my store
            pollProvider: '#poll1', // which I added both as id and itemId to my pollingprovider
        },
        control: {
            pollProvider: {
                data: 'pollData'
            },
            sightstore: {
            	load: 'sightingsLoaded'
			}
        }
    },
    pollData: function() {  // This never fires
    	alert('poll'); 
	},
    sightingsLoaded: function() {   // This never fires
    	alert('load'); 
	}
});

[mitchellsimoens]

refs are only for components. A store or PollingProvider are not components, they are just classes.

[Green]

Thanks much, explains it.

Does not make sense though. Strictly speaking using the MVC paradigm, all Control should after all be manageable/implementable in the controller(s).

Surely it would not be such a big jump from being able to ref UI components as well as any other types of non-UI controls like stores, direct providers, etc. One could even limit the Controller to resolve using ComponentQuery like now, and then just for the fun of it, check if the ref is not contained in the Application object. All the rest works the same, how events are hooked up, how callbacks are used, etc. The only limitation currently that the refs are synthetically limited to components only, instead of all Ext objects in the application.

Bit silly to use a MVC methodology and then have to split your Control functionality between UI and non-UI events - makes everything messy again.

Now one have to create one half the components in the app.js, the other half in views/controllers; handle the one half of the events here, and the rest there. All whilst all the events usually end up influencing the UI in some way.

Just my 2 cents.

[Malro]

So what is best practise to handle a store-event in controller?

[mitchellsimoens]

So what is best practise to handle a store-event in controller?

Resolve the store and use the on method