New theme location for SenchaCmd 3.0.2 & multi-app shared theme proof of concept

[ilanc]

Hi guys,
I couldn't figure out how to move directories, so have just deleted and recreate in the new location (sorry). I've also re-added the .sencha directories (there are settings files in there which need to be edited in order to get the multi-app / shared theme POC to work).

To use the forked repo:

• Clone
• Copy your ext-4.1.1a directory in to $/ext/
• Run your "Start Command Prompt with Ruby"
• Run $/BuildAll.bat
• Load $/Build/App1/index.html

Note index.html has a demo menu for switching between app1/2/3
Each app uses a shared theme (bootstrap in this case)

You can also load the apps from their source locations e.g. $/app1/index.html - but NB this uses the intermediate build outputs i.e. $\shared\resources\bootstrap\app.css = so you must build the theme in the shared app before this will work (this is built as part of BuildAll.bat by the commands:
cd shared
sencha app build

The new senchacmd Package structure isolates all Theme files away from the Resources/ directory. This is easier from the build process, but does mean that the Resources/ directory is bare until the app is built i.e. $\app1\index.html won't load until you've built the shared app. During build theme resources are built to $\shared\resources\bootstrap (intermediate) and then copied to $\build\shared\resources\bootstrap (final). I've excluded the whole of the final build outputs ($\build) as well as the images from the intermediate dir to save space in the git repo.

Finally - app1,2,3 are pretty unexciting apps - just proof of concept. I've left $\examples untouched, but ideally these should replace app1 & app2.

Let me know what you think.

Ilan

[wedgybo]

Thanks for this Ilan. We've not looked at 3.0.2 yet. I'll try and get a look at this before the end of the week and get it merged!

[ilanc]

No problem. If you're looking for a useful task which will teach you about the change:

• incorporate one of the apps from the main repo (e.g. $\examples\themes) as an app in my forked repo (e.g. as $\app4)