quickly-talk team mailing list archive

[tony byrne <tony.badwolf@xxxxxxxxx>]

Hi Didier
 Sorry to have annoyed you with my argument to keep -t. You said you
would remove it because it is not used but I use it. I suppose I
should have looked for the alternative instead of trying to keep an
unpopular and hard to maintain command. At no stage did I intend to
rant, I expressed myself badly if I could be read that way. :(

 I suppose this is all consistent with the difference between quickly
original's design, all code and no template, and my preferred project
model, less code and include configuration files. This is why, for me,
quickly add persistence, is an important option.

By my nature I looked into the template files (configuration) for
extending instead of the core code. You say that the virtual builtin
template can provide these any template commands.  But builtincommands
look like an internal quickly core module. How does a user (me) extend
it without, in effect, forking quickly on my machine ?


On 13/08/2012, Didier Roche <didrocks@xxxxxxxxxx> wrote:
> Le 11/08/2012 15:42, tony byrne a écrit :
>>   Alistair seems to want a command something like
>>
>> quickly create <any template> <project name>
>> cd <project name>
>> quickly add -t vcs git (this script also removes bzr etc)
>> quickly add -t vcs githost (this script also removes submitubuntu command
>> etc)
>>
>> (This is a version of his 2 templates proposal.)
>>
>> The argument against -t (misuse) seems counter to open source or
>> liberty itself. An analogy:
> Oh come on, please do not come with "linux is about choice", or look at
> that: http://islinuxaboutchoice.com/ and in particular the ML associated :)
> I hope we can avoid bringing the desktop ranting to Quickly and go on
> the "you are freedom hater" arguments because we don't want to support
> an option...
>
> The idea here is that we only propose commands that are be dully tested
> and under control in the environment. Sorry, I really think that it's
> something important and that developers don't have this button "do not
> click on me please", because we don't really know those effects. Leaving
> a bad choice is not about freedom, it's just about bad design.
>
> What I can propose for people really wanted "custom commands" that can
> be run anywhere, is to be able to extend the "builtin" template (which
> is a virtual template, the one providing the following commands:
> "commands, getstarted, help, quickly" in the ~ directory (in fact,
> extending all templates themselves with new command, including the
> builtin one). The builtin commands can be run anywhere. This has the
> advantage to:
> - force the quickly core code to stays logical and focused, but still
> modular (better for testing)
> - to give the extras command you want.
>
> Thanks,
> Didier
>