[Circle-dev] Tab-complete in frontends

[Paul LeoNerd Evans]

On Wed, Mar 18, 2009 at 12:55:03PM -0400, Philip Kovac wrote:
> > 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?
> >
> The problem is that lazy population will make the UI feel "sluggish." If we
> do this we should demand it all upfront and populate/update the information
> as we would anything else, or turn it off entirely. The "middle case" where
> bandwidth is scarce but roundtrips are cheap/fast doesn't seem terribly
> common. If anything, you usually have the case where bandwidth is cheap and
> plentiful but you have high latency (satellite broadband, "good" cellular
> links.)

Hrm, that is perhaps a fair point. It should be instantly available, or
it should not do it at all.. Jumping in after a delay would just be
confusing.

Perhaps this might make a case for pushing the completion data to the
frontend after connection, right at the end; i.e. after all the display
buffers are present, etc...

Something to muse apon, wrt. scheduling...

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