Any chance we can have the verb first, as this is much more intuitive? E.g.
create user
create region
Also, we really want to then avoid having some commands with hyphen
if some do not. That awkward to get right . I always do
create-user and then realise it does not work. E,g,
Justin, I like this idea - it also greatly simplifies the initial help,
which can simply refer the user to the sub command helps - e.g. user
help These new sub command helps can then be much more lengthy if need
be...
Justin Clark-Casey wrote:
Hello,
I want to add more commands to the
Ai Austin wrote:
Any chance we can have the verb first, as this is much more intuitive? E.g.
create user
create region
Also, we really want to then avoid having some commands with hyphen
if some do not. That awkward to get right . I always do
create-user and then realise
+1 on having a clear *and* documented interface for console commands.
I think that the verb + target paradigm is much more universal in Unix,
SQL (create Table, not table create) and people can remember easily.
Also commands should help people in understand why there are similar
commands
I always liked a feature often seen on some older unix terminal based
programs, like some curses based IRC clients, where just typing enough
characters of a command to resolve any ambiguity would give you the complete
command, and where the help section is nicely organized. It sounds to be
like
Well, I don't mean anything that advanced; It just struck me that commands
could just as well contain spaces.
Best regards,Stefan AnderssonTribal Media AB
Date: Thu, 5 Feb 2009 10:53:26 -0800From: dahliatrim...@gmail.comto:
opensim-...@lists.berlios.desubject: Re: [Opensim-dev] Organization
Hello,
I want to add more commands to the archiving module but I want to do this
within the module itself rather than adding
any specific logic to core.
The terrain module already has a 'module commander' to help do this, but this
prefixes all commands with the word
terrain (e.g. terrain
A common parsing routine that used keywords as commands and triggered off
of those would work best.
show users: users module receives: show
The parser would be looking for the module level first (users
etc), and since it is the 2nd word, it would strip it, and pass the
remaining
On Wed, Feb 4, 2009 at 9:50 PM, Justin Clark-Casey jjusti...@googlemail.com
wrote:
Any thoughts on this? Just kind of thinking about it at this stage - part
of me prefers typing things like show users
or help terrain while another part of my mind likes the 'tidiness' of
prefixing every
