I've brainstormed a few ways this could happen: A setting is added to /config/settings.yml when the first application is created (similar to how the first application gets the index.php front web controller). This can be edited by hand or with a configure:default-application task. No code is generated by symfony; the default application is selected on the fly (perhaps the first alphabetically) unless otherwise overridden in /config/settings.yml or ProjectConfiguration. ...
The propel tasks will have to be updated also, in one of any number of ways: Those tasks that need an application configuration include an "application" option (not argument). If this option is not provided, the system falls back to the configured default application. The propel base task is modified to somehow auto-magically provide the application argument if a valid one is not provided. I'm not sure this is even possible, considering that a tasks arguments are by definition required, but it may provide better BC. ... Kris On Jul 22, 2008, at 6:55 AM, Nicolas Perriault wrote: > > On Tue, Jul 22, 2008 at 3:18 PM, Ian P. Christian > <[EMAIL PROTECTED]> wrote: > >> sfDoctrine used to do this - I think it just selected 'randomly' (I >> think it was the first alphabetically) from the available apps. >> I'm not >> sure where such a default would best be set though.... propel.ini >> doesn't seem like the right place to me. > > Maybe in the ProjectConfiguration class ? > > ++ > > -- > Nicolas Perriault > http://prendreuncafe.com - http://symfonians.net - http://sensiolabs.com > Phone: +33 660 92 08 67 > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
