[Circle-dev] Tab-complete in frontends

[Paul LeoNerd Evans]

On Tue, Mar 17, 2009 at 04:57:05PM -0400, Philip Kovac wrote:
> I think it's fairly unreasonable to have sufficient magic to do full
> "intelligent completion" for complex commands on the client-side. I'm not
> totally sure how you would convey the information "what is a valid argument
> combination for this command."

Not so much combinations, just simply a tree of commands -> option names
-> option value enumerations. Obviously only the enumerations are
particularly completable; either fixed ones, or ones based on some
running data list (channels/nicks/etc...)

> Performing any sort of tab completion on the server side seems reasonable as
> an option, but in cases where the user is aware that the link is slow, they
> should be allowed to explicitly disable it.
> 
> But I think for trivial operations like JOIN and QUERY, there may be
> sufficient information that we already care about on our end to have the
> client handle it. Most single-argument options ccould probably have tab
> completion available, as describing "what property we should treat as a list
> for autocompletion" shouldn't be too difficult.

That was roughly where I was aiming, possibly via some laziness. Perhaps
roundtrip is "good enough" to lazily populate the options to a command
the first time the command's name gets completed?

-- 
Paul "LeoNerd" Evans

leonerd at leonerd.org.uk
ICQ# 4135350       |  Registered Linux# 179460
http://www.leonerd.org.uk/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://mail.leonerd.org.uk/pipermail/circle-dev/attachments/20090318/54378055/attachment.pgp>