For example, like your project, it only need to change userClassName of "tab1.controller.Mycontroller" from "MyController" to "tab1.MyController", and it will save to "app/controller/tab1" with an name called "app.controller.tab1.MyController", and you just put all subfolder together!
I tried to build a multiple-namespace structure like you suggested. The part where I get stuck is when a store needs to load in the dependent project.
Can you provide me with a sample that consists of the following:
1) application - main project consisting of a TabPanel
2) tab1 - dependent project that is a TreePanel with a Model and autoloading TreeStore.
3) when the application loads, the TabPanel Controller render event will use Ext.create to instantiate the tab1 object, and add the tab to the TabPanel. The tree should then autload the tree store and show a valid tree.
I have set up a multiple-namespace application in the latest Designer (v2, build 341). This is a "main" application TabPanel, with a dependent project as a Tab for that TabPanel. Everything seems to be set up fine. However, the only problem I seem to have (so far) is the store reference in the dependent project.
On the Tab I have a ComboBox which references a store "tab1.aStore". This deploys to the web folder as /webroot/scripts/app/store/tab1/aStore which is fine.
The problem is how the Dessigner references the store. When I select the ComboBox and pick the store from the list of stores, I can pick "aStore", which is the ID of my store. So the deployed code ends up with store: 'aStore' for the ComboBox. When I edit the deployed code to be "tab1.aStore" then it works fine. This leads me to believe that the store field in the ComboBox is not looking for the store ID, but rather the userClassName.
Can the Designer be changed to select the userClassName instead of the storeId?