Re: [gtk-list] Handling the selection
- From: Otto Hammersmith <otto redhat com>
- To: gtk-list redhat com
- Subject: Re: [gtk-list] Handling the selection
- Date: Tue, 13 May 1997 13:25:41 -0400
On Tue, May 13, 1997 at 01:21:36PM -0400, Owen Taylor wrote:
> There seem to be a couple of possible options:
> 1) Pass along requests for all targets application and let it deal.
> Pro: easy
> Con: gdk/gtk is supposed to hide gunky X stuff from the application
> and this is about as gunky as it gets. (for those who have looked
> at this stuff, I don't think I have to say anything more than
> 2) Handle the worst of the gunk (in particular INCR and MULTIPLE) in
> gdk and pass the rest on to the application.
> Con: I'm not sure how feasible this separation of gunk and ungunk is.
> 3) Create a higher level abstraction in gtk (gdk?) - for instance, Tk does
> this by allowing clients to register handlers for various types
> of targets.
> Pro: easiest interface for the application.
> Con: most complicated implementation.
> Right now I'm leaning towards some combination of 2 and 3. I'd be
> interested in hearing what people's needs are in this area. (And also,
> since I have little experience in this area, if people think these
> ideas make sense at all.)
I'd have to say I'd prefer 3. It's much like the rest of GTK...
Of course, that's coming from a person who probably won't be writing
the code. :)
You're probably right, somewhere between 2 and 3... at least allow a
totally GTK handling of simple cases, and I'd be happy.
] [Thread Prev