That's right,
symfony 1.2 default tasks (generate:app, generate:project, generate:module)
take them skeleton from SYMFONY_LIB_DIR/task/generator/skeleton and if you
have a look on any of these task class, they're using dirname() or
sfConfig::get('sf_data_dir') to find path to the skeleton.
That's means that skeletons must stand in this directory and cannot be
somewhere else. This is certainly due to the unexistence of any "data"
directory when symfony task create the project, I suppose.
Instead, when you're using the other syntax, you can create skeletons out of
the "data" directory where the default skeleton stands.
By example, I have my own skeleton for admin generator that stands in
SYMFONY_PLUGIN_DIR/myDoctrinePlugin/data/generator/sfDoctrineModule/my-theme
when the default one is in
SYMFONY_LIB_DIR/plugins/sfDoctrinePlugin/data/generator/sfDoctrineModule/default.
Be carefull, all generator have this behavior, but, unfortunely, forms and
filters tasks were not understand the "theme" option, whatever, you can
easily extends them and add you brand new forms and filters themeing
generation...
Loops
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---
