[crossfire] gtkv2 client vs gtk client gap list.

[Brendan Lally]

On 2/5/06, Mark Wedel <mwedel at sonic.net> wrote:
> > I'm not sure that is necessary, not so long ago there was a patch to
> > gcfclient to make it compile against gtk2, I will assume that this
> > gets accepted in the move towards 2.0, with the few bugs it isolates
> > picked up on the way.
>
>   I do wonder if at some point, gtk itself may drop support for the stuff from
> gtk1 they obsoleted.  For example, if gtk3 is released, they may very well say
> 'gtk1 code is going away - we kept and entire released version, but we don't
> want it anymore'.  I'd imagine that may be years away (and gtkv2 may continue to
> be commonly available on distributions for a while even after gtk3 is released),
> but a random thought.  Note that I have no indication that this is actually
> going to happen, but I imagine at some point, the gtk1 stuff that they stopped
> supporting will go away.

But long before that time, gcfclient can have been compiled against
gtk2, and it can use a lot of the code from gcfclient2 to replace
deprecated stuff.

>   Maybe - I'm not 100% sure how big gtk-common would be.  But this goes back to
> the original question, which is why keep the gtk-v1 client.  If the gtkv2 client
> has all the same features, is there a reason to keep the gtk-v1 client (this is
> driven people using it, but then perhaps the question is why are people using it
> over gtkv2).
>
>   If it is a matter of layout (I like the layout of gtk1 better), I wonder how
> hard it would be to do a 'gtk API' type of thing - take a glade config file, and
> say 'these are the callbacks you use' - one could whip up a new layout pretty
> darn quickly.

That's pretty much the reasoning behind a gtk-common/ however, I'd
rather have at least one client done manually, since glade is fairly
complicated.

>   IIRC, I did the entire layout of the gtkv2 client in glade in a single evening
> - it was the back end portion that was harder, and in some cases, because of the
> difference in gtk 1 and 2.


>   IIRC, to be 100% gtk2, the text windows (messages) and the lists (inventory,
> look) use new widgets.  If you take those pieces out, what is then left as
> common is the map (which does share code to a good extent right now), and the
> stat/resistances windows (which are pretty trivial).

If we assume that gcfclient is in future compiled against gtk2 by
default then the inventory and text code could be taken directly from
gcfclient2, given that they operate almost identically anyway.