Yeah ! Nice job !!! It seems we are on the same road ---> CatalystPlus
However, this nice application works differently than mine :
- it s SYNCHRONIZING everything (whereas CatalystPlus IMPORTS everything or just the skins/assets)
- it does not separate the look&feel in a library project
- you can manage multiprojects
- this app does not seem to come from old ages like mine !
Anyway, you know fellows ... frenchie frogs rock !
So yes, our approach is slightly different, but less than you think. Actually, my usual workflow consists in not synchronizing the entire source folder but simply the components folder in which Catalyst creates its own components and skins. I keep the same structure in my own builder projects but keep the modifications to those components to a minimum. Instead, I add all the logic to those components using composition via a Mediator pattern, close to the one used in PureMVC. I'll publish an example of that on my blog at some point.
It's also perfectly possible to synchronize different folders by creating several sub-projects to a specific project, one sub-project synchronizing for example the skins folder, another one the assets folder, etc (I'm throwing random folder names here).
I'll try to add in the next iterations the possibility to select which folders and sub-folders to include/exclude and also the possibility to limit the synchronization to a folder's content and not going any further into the hierarchy.
Anyway, work in progress!
One last point: CatalystBuilderSync synchronizes indeed, but on demand. If you deactivate the autosync functionality (which is deactivated by default) you can mimic your import function by selecting the Catalyst overwrites Builder button and you'll get something pretty similar to your import everything function. Anyway.
And yes, French people rule the World! The World just doesn't seem to be aware of that yet... Odd.