From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] Raw Input Driver
Date: Fri, 20 Mar 2009 17:17:57 +0200 [thread overview]
Message-ID: <7263e2a3ccf283886f301cf803427ada@proxima.alt.za> (raw)
In-Reply-To: <2C0788DC-E14D-4C9E-9623-FFA4A01CB761@lsub.org>
> The only problem is to come up with a
> widget abstract and generic enough.
That's because one can't resist generalisations. Maybe one should be
looking for generalisations at a different level of abstractions. Off
the cuff, if I could install sprites through a synthetic filesystem, I
may only need a channel in which to exchange commands and responses
with the sprites. The sprites themselves can contain the semantics
appropriate to their functions.
Or one may create TK objects, then submit TK commands to them and
accept responses on a multiplexor/demultiplexor channel depending on
need.
I'm shooting from the hip, of course, but that would the direction I
would be heading in.
++L
next prev parent reply other threads:[~2009-03-20 15:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 14:22 Francisco J Ballesteros
2009-03-20 14:32 ` roger peppe
2009-03-20 15:17 ` lucio [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-20 14:46 Francisco J Ballesteros
2009-03-20 14:35 Francisco J Ballesteros
2009-03-20 14:18 Francisco J Ballesteros
2009-03-20 14:29 ` roger peppe
2009-03-20 7:00 James Tomaschke
2009-03-20 7:07 ` lucio
2009-03-20 7:57 ` James Tomaschke
2009-03-20 9:12 ` erik quanstrom
2009-03-20 11:05 ` Charles Forsyth
2009-03-20 10:54 ` Francisco J Ballesteros
2009-03-20 11:07 ` cinap_lenrek
2009-03-20 11:28 ` roger peppe
2009-03-20 11:39 ` Fco. J. Ballesteros
2009-03-20 12:04 ` erik quanstrom
2009-03-20 11:32 ` erik quanstrom
2009-03-20 12:23 ` Charles Forsyth
2009-03-20 12:16 ` erik quanstrom
2009-03-20 13:03 ` roger peppe
2009-03-20 13:37 ` tlaronde
2009-03-20 14:26 ` roger peppe
2009-03-20 15:02 ` tlaronde
2009-03-20 15:14 ` tlaronde
2009-03-20 12:52 ` maht
2009-03-20 22:23 ` James Tomaschke
2009-03-20 9:13 ` lucio
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7263e2a3ccf283886f301cf803427ada@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).