[Circle-dev] Tab-complete in frontends

[Philip Kovac]

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."

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.leonerd.org.uk/pipermail/circle-dev/attachments/20090317/26073854/attachment.htm>