[Circle-dev] Tab-complete in frontends

[Paul LeoNerd Evans]

With appologies to Asimov, I think we might be able to summarise some
basic rules of Circle/Tangence as:

 1. Roundtrips are bad. Try to minimise them.

 2. Bandwidth use is bad. Try to minimise it except if it saves
    roundtrips.

 3. Memory usage is bad. Try to minimise it except if it saves
    roundtrips or bandwidth.
 
 4. CPU usage is bad. Try to mimimise it except if it saves roundtrips,
    bandwidth, or memory usage.


With this in mind... How might tab-complete work?

This is a somewhat non-trivial question really, as it all depends on how
much magic we want.

Trivially we can complete on nicks in channel without too much
difficulty, but what beyond that? Channel names? Of course these are
IRC-specific things. What about other windows?

What about commands - just their names? Their option names? Values for
options? Fixed enumerated ones; variable ones?


I have some ideas for implementation and behaviour, but before I go
polluting the discussion with those, I thought I'd poll for thoughts
from anyone else...

-- 
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/20090317/7a83d014/attachment.pgp>