We have discussed sandbox mode and there are a couple or so directions it could go.
I am curious to know more specifically what you are wanting to achieve. I assume you have a mixture of v3 and v4 classes? Are you wanting to produce a subset of the frameworks? And wrap the v4 subset in a sandbox...
Cmd wouldn't need to care about the Ext JS 3 classes and their proper inclusion, but only accept "Ext4" as the Ext JS 4 namespace.
I imagine this might just be a minor tweak to the tool, but maybe sandboxing is more complicated internally?
Yeah that is the harder part - partitioning code that says one thing ("Ext") but needs to be understood as another ("Ext4") so that references from other code using the other name ("Ext4") link up properly. Then we need to wrap the sandbox around the Ext 4 code during the build.
It is all doable, but won't make in this release (3.0.0). Knowing that there are folks using/needing this support is really helpful though to decide when to pull the trigger on it.
I'm going to open this as a ticket so we can both track it.
Thanks for taking the time to explain what you were needing.
Any update on this issue ? Is it possible with the latest Sencha Cmd 220.127.116.112 release ? This is vital functionality for being able to port a legacy ExtJS 3.x application to ExtJS 4.x and a Sencha Cmd based build.
To get around this I ended up taking the sliced images from a non-sandboxed version of our theme that I generate and incorporate those images as the images for the sandboxed theme. When generating the theme with the sandbox I just use
sencha package build
from within the theme package and use the built <theme-name>-all.css.
The main downfall of this is that we can't take advantage of minimizing the js or css sent to the page as we use ext-all-sandbox.js and <theme-name>-all.css.