Debian releases a Gtk3 Lazarus

[dbannon]

So, some more news.
Firstly, the deadline to fix the Debian manifestation of Lazarus (and the apps dependent on it) has been pushed back to April the 13. Maybe they considered (last) Friday the 13th too unlucky ?

Today a new release of Lazarus 4.6 appeared in Unstable with a Gtk3 Lazarus binary. Seems they have taken some (or all ?) recent Gtk3 patches to main and apply them at source packaging time. I have just tried it and it seems remarkably stable but not without issues.

Important thing is that if this is allowed to migrate to Testing (ie Forky) then the FPC/Lazarus apps already in Forky (which of course are not Gtk3) will not be removed. Nice.

One thing to be aware of, if we see new users appearing asking questions about (Forky's) Lazarus 4.6 and Gtk3, lets remember that they are really using a 'main' for, at least, Gtk3 !

Forky is not due for formal release for another 18 months or so, so lots of time to catch up but  its necessary to use Testing to build source packages for submission to Debian and some people just like to use Testing.

Davo

[paweld]

Thank you very much, David, for the information.

[dbannon]

Some Further Observations.

I am a bit surprised to see that Debian "appear" to have fixed at least two annoying (one a breaker) bugs that still exist in our Lazarus Main.

• As well as showing a transparent Object Inspector (O.I) when the initial Project Wizard is shown, the Main version of Lazarus sometimes, usually, shows no content in the OI and,if its closed and reopened, is totally black (pictured]. OI always works in Debian version but main and Debian versions reopen the OI in micro size.
• The Main version does not open a project when its selected in the Project Wizard in the Recent Projects combo. Debian version works OK.
• Additionally, as mentioned above, closing and reopening windows such as Object Inspector or Messages reopens then with close to zero height and width. This seems a real killer IMHO and I am surprised it has ot been seen by others. Ayone else ?  I see it on my Bookworm working machine and the Unstable (Sid) VM. Can be resized if you know to look for them.

These tests done on a Debian Unstable box to ensure both are using same version of Gtk3. The Debian version as installed, for the Main version I built Main from source using the Debian FPC322. I see all three issues on my Bookworm box too.

Davo
 

[AmatCoder]

Lazarus package in Debian has been heavily patched up to switch to GTK3.

You can see all the patches that have been applied here.

[JuhaManninen]

The zero height and width must be related to Wayland. I haven't seen that with X11.
I saw a transparent Messages window.
True, project selected in the Project Wizard Recent Projects combo is not opened.

Lazarus package in Debian has been heavily patched up to switch to GTK3.
You can see all the patches that have been applied here.

Some GTK3 commits are backports from Zeljan, some are by Mazen Neifer.
Which one fixes the Project Wizard Recent Projects combobox issue? I could not find it by just looking at the commits.

[Thaddy]

Yes, the 0/0 bug is related to wayland in the sense that the widget set should take care of it.
The good news is that the new wayland expension API for window size and positioning can be used to solve it in a generic way.
That hasn't been done yet, because that API is extremely recent.

[dbannon]

The zero height and width must be related to Wayland. I haven't seen that with X11.

My Bad, I should have mentioned that I am NOT using Wayland on either of my test boxes.
Note, did I mention that the blank Object Inspector only shows up when you have opened Lazarus for the second (plus) time ? Clear away the config dir and it works fine the first time !

Some GTK3 commits are backports from Zeljan, some are by Mazen Neifer.
Which one fixes the Project Wizard Recent Projects combobox issue? I could not find it by just looking at the commits.

No, I went through the patches myself (downloaded the changes file) and it was not obvious to me. I'm getting ready to fit a new hard disk to my machine so, when and if that is successful, I'll go over that list again. Its interesting that the (Debian) Pascal Devs mailing list has been particularly quiet in the last week or so.

Davo

[dsiders]

Lazarus package in Debian has been heavily patched up to switch to GTK3.

You can see all the patches that have been applied here.

What could possibly go wrong? It compiles... ship it.

[zeljko]

Lazarus package in Debian has been heavily patched up to switch to GTK3.

You can see all the patches that have been applied here.

OMG, and then ppl will fill bugreports against laz 4.x gtk3

[theo]

Lazarus package in Debian has been heavily patched up to switch to GTK3.

You can see all the patches that have been applied here.

OMG, and then ppl will fill bugreports against laz 4.x gtk3

Yeah, I don't think that's a good idea.
You've done an incredible job over the last few days, and the GTK3 IDE is getting better and better.
But is it ready for “prime time” yet?
I don't know—maybe it's still a little too early?

[PascalDragon]

The good news is that the new wayland expension API for window size and positioning can be used to solve it in a generic way.
That hasn't been done yet, because that API is extremely recent.

And it also won't help, because the project leads for the Gnome and KDE compositors respectively said that they don't have a desire to support that extension. 🙄

[zeljko]

Yeah, I don't think that's a good idea.
You've done an incredible job over the last few days, and the GTK3 IDE is getting better and better.
But is it ready for “prime time” yet?
I don't know—maybe it's still a little too early?

Few days ? Well, ok, I'd say months , even years. If something is commited today, that does not mean that it is coded today or yesterday But yes, heavy work has been done. It is not yet ready for the prime time, printing is open task (we'll I think it can be done in a day or two - just copy and fix gtk2 implementation, since it already uses cairo there) and many small unimplementations or bugs.

[theo]

Few days ? Well, ok, I'd say months , even years. If something is commited today, that does not mean that it is coded today or yesterday

Sure. I just noticed that the commit tracker has had a lot of GTK3 entries lately.
Thanks for that! 

[dbannon]

OMG, and then ppl will fill bugreports against laz 4.x gtk3

Yes, that was the main reason I started this thread.

Davo

[dsiders]

Sure. I just noticed that the commit tracker has had a lot of GTK3 entries lately.

Commits to the main branch do not equate to commits to fixes_4. The Debian maintainer has been told he can't force these things through in that manner - but apparently doesn't care because ... you known ... Debian. They're creating this clusterfuck... they should have to deal with it. Unfortunately, in the end, it's going to ruin this projects' (Lazarus) reputation.

But hey, everyone's pet development projects get to stay in the Debian repos (even if they're broken)... so mission accomplished. Let's all pat ourselves on the back while we watch the community quietly wither away.