Gtk3 becomes default widgetset on Linux

[zeljko]

It is mainly Wayland headache, not gtk3 or qt6.

[dbannon]

Q2: no. that requires a complete new architecture:
Although Lazarus goes a long way in making itself widget set agnostic, there are some problems to achieve that, because of the different signalling and messaging concepts between widget sets.

No, I disagree there Thaddy, the gtk2 components of FPC are really only there as an historical accident. There is no intrinsic or architectural reason why they reside in FPC. I think the debian people, who got very upset about that issue, demonstrated that pretty clearly. I think they also removed some Windows code too, but thats from memory and I sort of lost track of that whole process due to some private issue that have plagued me for the last 12 months.
Davo

[PascalDragon]

Q2: no. that requires a complete new architecture:
Although Lazarus goes a long way in making itself widget set agnostic, there are some problems to achieve that, because of the different signalling and messaging concepts between widget sets.

No, I disagree there Thaddy, the gtk2 components of FPC are really only there as an historical accident. There is no intrinsic or architectural reason why they reside in FPC. I think the debian people, who got very upset about that issue, demonstrated that pretty clearly. I think they also removed some Windows code too, but thats from memory and I sort of lost track of that whole process due to some private issue that have plagued me for the last 12 months.

It does in principle make sense to have the units included with FPC, because this way one can simply use FPC to develop applications for those widgetsets without a third party download and without Lazarus involved. At least that was the idea back then. Nowadays I'd prefer to keep such units outside of the FPC distribution, so that they can also evolve independantly of FPC.