> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Paul Fisher
> Subject: Re: alternative to gtk...
>
>
> Brian Jones <[EMAIL PROTECTED]> writes:
>
> > It wasn't about a 'switch', just another alternative. Alternatives
> > will happen eventually... free software just doesn't stay the same
> > forever. ;)
>
> You're more than welcome to write a peer implementation for your new
> favorite toolkit, but *I'm* not going to help. :) Writing a peer
> implementation is far from easy -- it's an extremely time consuming
> process that can drive you insane. Once Jim and I finish with the GTK
> peers, there would have to be some _really_ important reason for us to
> start work on peers for a different widget set.
>
> I understand way too much of the internals of Xlib, GDK, and GTK --
> more than I ever wanted to know, and I'll know even more by the time
> we're finished. Writing a peer implementation requires that you
> become one with the toolkit.
>
Is there any way to make it easier? Some abstraction layer that people
could plug new widget sets into?
If you could let us know (when you're done, of course) what the major
challenges you ran into were, maybe even write a little something up on the
general pieces required to create a peer widget set, it'd be cool. No use
reinventing *everything* each time we port.
--John Keiser
