[by jay@moduscreate.com]

I've escalated & it's being worked on. Thank you very much for reporting this problem.

[by jay@moduscreate.com]

This is very strange! You can't download Ext JS or Touch. I'm escalating.

[by jay@moduscreate.com]

bad effing a$$!

[by jay@moduscreate.com]

Moved to the appropriate forum.

[by jay@moduscreate.com]

Interested in Sencha Touch video training provided by myself and three of our experts? Check out our preview at http://moduscreate.com/training/video/ and sign up for the newsletter.

We haven't...

[by jay@moduscreate.com]

it's not designed to do so! If you're not going to "waste time" trying to learn the MVC pattern for Ext JS and understand how it does work for large apps, then I'm not going to waste my time trying...

[by jay@moduscreate.com]

OK, that's your call. To be honest, we at Modus Create build large enterprise apps and use the MVC pattern that's out of the box with no problem. Seems that you're frustrated that it doesn't work...

[by jay@moduscreate.com]

Well it's design is different than server side MVC.

[by jay@moduscreate.com]

All proxies are read only, except for the local & session storage proxies.

What you need to understand is that the store changes are applied to the model instances not the raw data.

[by jay@moduscreate.com]

this block could be better improved


storeObj.load({
callback: function() {
callbackFn();
}
});

to

[by jay@moduscreate.com]

You're not taking scope into account for your callback, which may be dependent on execution scope.

[by jay@moduscreate.com]

What you could do is tell each store to check for non-favorable status codes, and then have them attempt one or two re-loads. <shrugs>

[by jay@moduscreate.com]

No. This is a fundamental JavaScript issue you're trying to tackle.

When a model ingests data, it makes "copies" to that data. (i say copies because it's duplicating references). When you change...

[by jay@moduscreate.com]

If your server side cannot handle multiple async requests, then you need to do something on the client to throttle it.

It's either: Fix the server or hack up the client. :-\

[by jay@moduscreate.com]

Commit the changes in the store, loop through the records (store.getRange()), and create an array of the items from the record.data references. Submit *that* array, not the original!

[by jay@moduscreate.com]

No it should not. Why? Because it won't munge the original data. This is setup this way for a reason.

[by jay@moduscreate.com]

FWIW, this is not a problem with the basic grid example. This is a problem where you're trying to go above and beyond how the grids & forms work.

[by jay@moduscreate.com]

Wow. Are you really doing a full page submit??? ... and an alert to boot. :(

Ok... Modifying the grid instance and wrapping it a form doesn't make it an input field. If you're looking to submit...

[by jay@moduscreate.com]

The implementation of MVC dictates that only one controller instance per APP. So... the best way to achieve what you're looking to do is probably adopt & use Deftjs.

[by jay@moduscreate.com]

I don't think it's any more clunky than your current setup though.

You should not need to use an Ext.defer though.

[by jay@moduscreate.com]

Why not just allow them to pinch the image to resize?

[by jay@moduscreate.com]

there is no "diagonal swipe" gesture. You'll have to create your own.

[by jay@moduscreate.com]

If you don't need the panel, don't nest the list under the panel. Just add the list as a child of the tab panel.

You're not seeing a list because of the exception. The question is, are you seeing...

[by jay@moduscreate.com]

The 2.2 lists are still highly optimized and only add to the DOM what is necessary,and I believe having a height helps w/ that issue.

I can't imagine why you can't have the parent container set...

[by jay@moduscreate.com]

I believe you need to use a native wrapper to do this. There's some low-level stuff that needs to go on and wrapping it is the only way to achieve this. The JS Engine has no access to the photo...