<dsc_>
which means the Qt6 QPA xcb maemo5 plugin cannot be compiled with those features, any compile definition passed will get overriden by the defs in those headers (QT_CONFIG(feature) macro uses it)
joerg has quit [Killed (silver.libera.chat (Nickname regained by services))]
joerg has joined #maemo-leste
apac has quit [Ping timeout: 276 seconds]
System_Error has quit [Remote host closed the connection]
<Wizzup>
freemangordon: dsc is working on qt6 porting
<Wizzup>
he's got very far but there I think has issues with some maemo specific widgets in the style part
<Wizzup>
freemangordon: we're working on being able to use debos for images, I made a post online about the forgejo migration
<Wizzup>
freemangordon: forgejo does code search like github now, instance wide (but some repos are excluded, most upstream forks are)
<Wizzup>
freemangordon: and I'm going to work on the daedalus news post next
<dsc_>
i managed to port all the plugins (qpa/input/plaformtheme/style) to Qt6
_fab has quit [Quit: _fab]
_fab has joined #maemo-leste
<dsc_>
which was NOT trivial
_fab has quit [Quit: _fab]
_fab has joined #maemo-leste
xmn has quit [Ping timeout: 260 seconds]
_fab has quit [Quit: _fab]
_fab has joined #maemo-leste
<sicelo>
silly question ... the qt parts seem to have migrated nicely from qt4 originally, through 5, and now 6. what makes it different/difficult for gtk2 -> 3 (and maybe) -> 4?
<sicelo>
i know nothing about toolkits, but who knows ... maybe i could learn a bit to lend a hand
<sicelo>
nice work dsc_
parazyd has quit [Ping timeout: 260 seconds]
parazyd has joined #maemo-leste
<Wizzup>
sicelo: theming for gtk3 is the problem
<Wizzup>
gtk does not care about compat, at all
_fab has quit [Quit: _fab]
<Wizzup>
and qt4-qt5 took many months
_fab has joined #maemo-leste
<Wizzup>
sicelo: so we'd lose all our themes
ceene has quit [Ping timeout: 245 seconds]
<Wizzup>
we'd have to remake them
_fab has quit [Quit: _fab]
_fab has joined #maemo-leste
_fab has quit [Quit: _fab]
_fab has joined #maemo-leste
Daanct12 has quit [Quit: WeeChat 4.6.3]
<sicelo>
so theoretically, if one didn't care a lot about the theming, they could somewhat transition to gtk3 already?
<sicelo>
just trying to think (out loud) where/how one could help with migration from gtk2, where one would have to start
<Wizzup>
it wouldn't look like maemo, but yes.
<Wizzup>
the help is either in making some tooling to migrate our gtk2 themes to gtk3, or just recreating the themes from scratch in gtk3 style
<Wizzup>
gtk2 is bitmap theming, gtk3 is css
<sicelo>
oh i see. sounds difficult but perhaps somehow doable, with some time invested in learning this a little bit
<Wizzup>
also: Starting from GTK 3.14, the theming engine modules are deprecated in favor of pure CSS themes, and GTK will not load them.
<sicelo>
know if gtk3 would be happy with gconf2? or gconf2->gsettings migration should be higher priority?
<Wizzup>
don't know
<Wizzup>
at this point neither are imo until we get to excalibur
<inky>
will maemo ported to gtk3 or 4 work slower because of that? but can we stay on gtk2 "forever"?
<inky>
s/maemo/hildon
<Wizzup>
forever does not exist
<inky>
other question. on daedalus i got update to hamster filer, i got that exclamation mark in the upper bar, then if you click on it the popup (window coming from the bottom) comes and it says:
<inky>
New software updates
<inky>
Ovi software(1)
<inky>
should that be Ovi? (:
<inky>
> forever does not exist
<inky>
yes that's why i said "forever". (:
<Wizzup>
you can fix the translations not to asy ovi I think
<inky>
i didn't enable any translations, i guess it's in the source code.
<inky>
if i understand correctly, gettext and other tools work in a way that english is in the source code, they extract the strings to .po files and then translations are in dedicated .po and later compiled .mo files?
<inky>
so the important part is that ovi is probably in the source code.