[symfony-devs] Re: The new symfony CLI system

On 3 Aug., 14:05, "Luciano A. Andrade" <[EMAIL PROTECTED]> wrote: > theres is (or will be) a backward compatibile mechanism for old task? > I have a couple of task i like to keep using with the minimun alteration. Are there any information about this question? Is it possible to use good old pake

[symfony-devs] Re: The new symfony CLI system

theres is (or will be) a backward compatibile mechanism for old task? I have a couple of task i like to keep using with the minimun alteration. On 7/31/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > probaply not the right place here, but i think there should be a > special sync command that

[symfony-devs] Re: The new symfony CLI system

probaply not the right place here, but i think there should be a special sync command that automatically shrinks javascript code with that nice library located at http://dean.edwards.name/download/#packer --~--~-~--~~~---~--~~ You received this message because you

[symfony-devs] Re: The new symfony CLI system

Here is the output of the help command for cache:clear: ./symfony help cache:clear Usage: symfony cache:clear [application] [type] Aliases: cc, clear-cache Arguments: application The application name type The cache type to clear Description: The cache:clear task clears t

[symfony-devs] Re: The new symfony CLI system

Hi. I'd find some command useful that prints tasks with all the parameters they expect, like: symfony sync [go] symfony disable Is ":help" going to do that? Also it would be nice to have a task that can disable a whole project. The project:disable task expects an application and an enviro

[symfony-devs] Re: The new symfony CLI system

I kind of like this structure. On Jul 28, 8:52 pm, Fabien POTENCIER <[EMAIL PROTECTED]> wrote: > Here is the updated list of task names by namespace: > > Available tasks: >:help Displays help for a task (h) >:list Lists tasks > cache >:clear C

[symfony-devs] Re: The new symfony CLI system

Here is the updated list of task names by namespace: Available tasks: :help Displays help for a task (h) :list Lists tasks cache :clear Clears the cache (cc, clear-cache) generate :appGenerates a new application (init-app) :b

[symfony-devs] Re: The new symfony CLI system

Shortcuts are already availalbe in symfony 1.0 and I have implemented the same system for the new CLI. So all the following will execute the log:rotate task: ./symfony log:rotate ./symfony log:rot ./symfony log:r ./symfony l:rotate ./symfony l:r ./symfony log-rotate ./symfony log-rot ./symfon

[symfony-devs] Re: The new symfony CLI system

haha... I just thought of something :) You should be able to use arbitrary shortcuts like: proj:fr would be project:freeze, if "proj" and "fr" were not ambiguous shortcuts ;) On 7/28/07, Fabien POTENCIER <[EMAIL PROTECTED]> wrote: > > > Hi Fabian, > > Thanks for the feedback. I really like the

[symfony-devs] Re: The new symfony CLI system

Hi Fabian, Thanks for the feedback. I really like the project namespace. I'm sure about the cache namespace. I think those clear-* tasks belong to the project namespace too (ok, the names are quite long): project:clear-cache project:clear-controllers Fabien Fabian Lange wrote: > Good mornin

[symfony-devs] Re: The new symfony CLI system

Good morning I like it, has some maven touch :) I did never like really fix-perms because it is really not telling. However I admit that permissions is a long name... What about something like: project:freeze project:unfreeze project:permissions project:enable project:disble project:sync an

[symfony-devs] Re: The new symfony CLI system

] Re: The new symfony CLI system When you type just propel without the :build-all you should prompt the user with an interface to select the desired command this would ease the learning process for beginners --~--~-~--~~~---~--~~ You received this message because

[symfony-devs] Re: The new symfony CLI system

When you type just propel without the :build-all you should prompt the user with an interface to select the desired command this would ease the learning process for beginners --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google

[symfony-devs] Re: The new symfony CLI system

I have one project using both doctrine & propel, so they can co-exist. On 7月27日, 下午11時09分, "Javier Eguiluz" <[EMAIL PROTECTED]> wrote: > Hi Fabien, > > Regarding database tasks, I don't know if it could be possible to group all > tasks under a generic "db" namespace (like Rake >

[symfony-devs] Re: The new symfony CLI system

I believe aliases should be better for that. For example, keep propel:data-load, and make an alias to db:data-load according to what your ORM preferences are. On Jul 27, 12:09 pm, "Javier Eguiluz" <[EMAIL PROTECTED]> wrote: > Hi Fabien, > > Regarding database tasks, I don't know if it could be p

[symfony-devs] Re: The new symfony CLI system

Hi Fabien, Regarding database tasks, I don't know if it could be possible to group all tasks under a generic "db" namespace (like Rake of Ruby on Rails). Then, symfony CLI should automatically detect if the project uses Propel or Doctri

[symfony-devs] Re: The new symfony CLI system

And you can type: ./symfony list propel to only display the tasks in the Propel namespace. Fabien P.S.: I've just renamed help-summary to list. Dave Dash wrote: > I like the name-spacing as it makes it easier to follow. Especially > when plugins start adding their tasks, e.g. doctrine. We

[symfony-devs] Re: The new symfony CLI system

I like the name-spacing as it makes it easier to follow. Especially when plugins start adding their tasks, e.g. doctrine. We can be sure that doctrine:* are all related to the sfDoctrinePlugin. On 7/27/07, Fabien POTENCIER <[EMAIL PROTECTED]> wrote: > > > As I'm in the process of polishing the n