> 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
