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 and naming
patterns of commands on the consoleI 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 that may be what you are describing?
Another issue I find, not sure if it's related or not, is the inability to use
the backspace key in the OpenSim console while running on various linux
distributions. I don't know where this is coming from, but I wonder if it's
something OpenSim could control?
On Thu, Feb 5, 2009 at 10:28 AM, Stefan Andersson <ste...@tribalmedia.se> wrote:
Just chipping in my 2c: How about the modules are supposed to register the
'command' whatever that is, but that the 'command' can include spaces? So,
"create user" should be a valid command, sending the remainder to that region
(via the registered delegate). which means another module can register "create
region" but not "create user", as that would have already been registered. Of
course, it cannot register a non-character terminated subset either, like
simply "create". the command parser would simply run thru the list, doing a
'starts with characters' match, probably with a non-character terminator in the
regexp. (If you're really anal on performance, the whole list of matches can be
concatenated into a regexp and compiled once) Of course, you would have to
register "help create user" as well, but it seems to me that there could be an
abstract base class providing some protected generative helper functions. (To
either create and register verb+" "+noun and/or noun+" "+verb, and the
corresponding help text in one go)This seems like the most flexible approach to
me, as it poses no limitations on what commands makes the most sense for each
context.Best regards,Stefan AnderssonTribal Media AB> Date: Thu, 5 Feb 2009
18:30:25 +0100> From: drscofi...@xyzzyxyzzy.net
> To: opensim-dev@lists.berlios.de> Subject: Re: [Opensim-dev] Organization and
> naming patterns of commands on the console
> > Justin Clark-Casey wrote:> > Ai Austin wrote:> >> Any chance we can have
> > the verb first, as this is much more intuitive? E.g.> >> create user> >>
> > create region> > i prefer addressing the entity that is supposed to do
> > something first (to get> it's attention, so to speak), then tell it what to
> > do:> > region create> user create> user reset password> > that approach
> > also has the advantage that it's up to the module what vocabulary> to
> > support.> > -- > dr dirk husemann ---- virtual worlds research ---- ibm
> > zurich research lab> SL: dr scofield ---- drscofi...@xyzzyxyzzy.net ----
> > http://xyzzyxyzzy.net/> RL: h...@zurich.ibm.com - +41 44 724 8573 -
> > http://www.zurich.ibm.com/~hud/>
> > _______________________________________________> Opensim-dev mailing list>
> > Opensim-dev@lists.berlios.de>
> > https://lists.berlios.de/mailman/listinfo/opensim-dev_______________________________________________Opensim-dev
> > mailing
> > listopensim-...@lists.berlios.dehttps://lists.berlios.de/mailman/listinfo/opensim-dev
_______________________________________________
Opensim-dev mailing list
Opensim-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/opensim-dev
