On 3 Jan 2010, at 15:35, Felix Gilcher wrote: >> - Is it possible to define my own "new" project, to be created using the >> command line, like "agavi project-create"? I have found >> http://blog.agavi.org/post/155569516/using-your-own-build-templates-from-second-zero >> from a while ago, but can I check it is still accurate? > > It is still accurate, if something doesn't work the way intended, let me know.
Thanks, >> Is this sort of thing possible? I think I'm trying to extend the concept of >> a class hierarchy to a "project" hierarchy. > > Not in a simple and consistent way. I have tried some tricks and tweaks using > a second "modules" directory to look up shared modules but that wrecks quite > a couple of other things - caching, config handlers, validation etc are > affected and partially broken. > > To sum things up, the best way of having a "base" project that I have found > so far is using the merging capabilities of any VCS: You branch from the base > and if you do changes on the base, you merge them into any appropriate > derived project. Use whichever VCS suits you best (no semi-religious > discussions here, please). That way, any project is standalone, but knows > it's history. Still, changes can be pulled up or pushed down with relative > ease. If nothing else, I'm pleased that my "base" project thought isn't too ridiculous, I was worried I might be overcomplicating things somehow. But the VCS seems like an interesting idea. Especially with templates, where there isn't a class system to add "base" functionality. But I'm wary this is slightly a hack. Are there any long-term issues with such a setup? (My VCS usage so far is quite basic). Michal. _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
