Hi Wilk, I'm a Sencha Architect user (power to the domain experts!) and I'm looking at how to create a packaging that is compatible with both Bower and Architect. It seems possible, http://stackoverflow.com/questions/14079833/how-to-change-bowers-default-components-folder covers how to set the default bower_components to something else. Naming it "packages" means that "bower install" will unwrap the packages into an area that Architect will recognize them as extensions.
What I'm pondering now is how to deal with the fact that there's a dependency between the two bower packages if one wants to use the proxy. This is less obvious, but the shortest path seems to be if the Bower packages were combined. I can imagine there are cases that people might want to use one without the other and care a lot about that extra code getting downloaded, what do you think?
If we could combine the two projects, I could build the Architect metadata. It would be reeeeeallllly cooool!
Brian
Hi Wilk, I'm a Sencha Architect user (power to the domain experts!) and I'm looking at how to create a packaging that is compatible with both Bower and Architect. It seems possible, http://stackoverflow.com/questions/14079833/how-to-change-bowers-default-components-folder covers how to set the default bower_components to something else. Naming it "packages" means that "bower install" will unwrap the packages into an area that Architect will recognize them as extensions.
What I'm pondering now is how to deal with the fact that there's a dependency between the two bower packages if one wants to use the proxy. This is less obvious, but the shortest path seems to be if the Bower packages were combined. I can imagine there are cases that people might want to use one without the other and care a lot about that extra code getting downloaded, what do you think?
If we could combine the two projects, I could build the Architect metadata. It would be reeeeeallllly cooool!
Brian