URL:
<http://gna.org/patch/?6057>
Summary: gtk3x-client
Project: Freeciv
Submitted by: cazfi
Submitted on: Thu 30 Apr 2015 03:23:37 AM EEST
Category: client
Priority: 5 - Normal
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Planned Release: 3.0.0
_______________________________________________________
Details:
The next compatibility break in gtk toolkit, gtk4, will come eventually. They
have not published exact schedule yet, but they do make preparatory steps
toward it, and gtk+3 already goes in 3.16 series (last gtk+2 series was 2.24).
My guess is that gtk4-client is something we are going to have in freeciv-3.1
or freeciv-3.2 - which probably means that we're going to have *3* gtk clients
simultaneously, due to fact that our transition from gtk2 to gtk3 has not been
as succesfull as we hoped for. So it's too early to obsolete gtk2-client
completely yet in freeciv-3.1.
I don't know if there's much we can do for gtk3 -> gtk4 transition to be
easier than gtk2 -> gtk3 one has been. On thing I do want to do is to prepare
in advance. I think we should start working on gtk3x-client in freeciv-3.0
cycle already. Bumping minimum gtk3 version for gtk3-client is something we
want to avoid now on - any such bump will mean that a bit newer systems are
too old for running gtk3-client -> forces us to maintain gtk2-client longer.
gtk3x-client on the other hand would be updated to match latest gtk3 version,
at least modernizing away any deprecations but ideally also taking advantage
of the new features already. One gtk4 gets released, gtk3x-client would be
renamed and updated to gtk4-client.
That plans involves reverting patch #5891 (--with-glgtk configure option).
It's better to leave any such stuff to clean implementation in gtk4-client
than to try messy implementation (heavily conditional compilation depending on
gtk3 version) in gtk3-client, when it would not get completed sooner anyway.
The idea of adding one more client makes it even more important than before to
get rid of some of the more obsolete ones.
Removal of sdl-client from 3.0 should not be controversial in any way, as it
had sdl2-client as direct replacement. I'm not for removing it just yet,
though, as it has proved to be rather handy reference in sdl2-client
development (one can test with sdl-client how things are supposed to work).
Quite soon, when there's less need for this kind of use, the fact that S2_6
has sdl-client to test with will be enough.
Xaw-client was declared unmaintained in S2_5. So far I have been thinking
about keeping it around for 3.0 cycle as a last chance for it to get someone
to take care of it, and to drop it from 3.1 if nobody does. However, I now see
even less future for a client directly using X-libraries when the world is
moving to Wayland. So I would be for dropping xaw-client immediately. (The EOL
of freeciv-3.0 is probably something like 7 years away - keeping xaw-client in
3.0 would keep it with us that far. And that's only our point of EOL - some
distribution may take our last 3.x release to their LTS release for another 5
years)
I've also checked what information there's about Qt6 and SDL3. It seems that
Qt5 -> Qt6 will be relatively easy for us - the compatibility break would be
mostly in things we're not concerned about (at the moment, at least).
SDL3 was barely mentioned, and given the fact that SDL2 goes in version 2.0.1
only, I think it's still very far away.
_______________________________________________________
Reply to this item at:
<http://gna.org/patch/?6057>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Freeciv-dev mailing list
[email protected]
https://mail.gna.org/listinfo/freeciv-dev
