GTK3 is ready?

[xfnHb7]

That's one of the reasons why I lost will in maintaining gtk3 since every minor versions have new deprecations and api changes, so in case of gtk3 and especially gtk4 I must be full time concentrated on gtk3 changes and fix it in lazarus, sorry, no way.

Yes I understand. But GTK3 should be stable now.

I am more interested in the question of whether it is at all possible to bring this binding to a satisfactory state, or whether GTK3 is simply not suitable as an LCL interface.

I would be interested from anyone who has delved deeper into this if there is any point in trying to fix things or if it is just hopeless.
What are the major sticking points?

I'm in no position to talk about it. But, think it yourself. If they could make gtk2 works and worked perfectly, why don't they can't do that with gtk3? If gtk2 is a perfect LCL interface, why gtk3 can't? It's all because the lack of interest.

[wp]

It's all because the lack of interest.

You are excused because you are a new user and don't know better. But messages like this normally make me sad and angry simultaneously. Lazarus is developed by people like you in their spare time without any payment, just driven by their own motivation and interest in the subject. So, don't talk of "lack of interest".

[xfnHb7]

It's all because the lack of interest.

You are excused because you are a new user and don't know better. But messages like this normally make me sad and angry simultaneously. Lazarus is developed by people like you in their spare time without any payment, just driven by their own motivation and interest in the subject. So, don't talk of "lack of interest".

I'm sorry. My English was learned from the street. Sometimes what I wrote is not I wanted to mean and sounds impolite or even rude.

[dbannon]

Lets be clear here. We don't have a complete GTK3 because its hard job, lots and lots of things to do, test, debug, fix. 

I run my app up under GTK3 every few months. Every time I do, I am surprised to see more of it working. Every time !  There is a steady flow of new work going into the GTK3 interface all the time and its gradually getting better. There sure is NO lack of interest.

Just now, apart form a few sizing problems, my app almost usable under GTK3. Wow !

Davo

[theo]

My question was not intended as a basis for gossip.
I would like to get more information from people who know about it.
For example by Zeljko, Anton Kavalenka, Juha Manninen, Marco Van de Voort...
I'll try again:

That's one of the reasons why I lost will in maintaining gtk3 since every minor versions have new deprecations and api changes, so in case of gtk3 and especially gtk4 I must be full time concentrated on gtk3 changes and fix it in lazarus, sorry, no way.

Yes I understand. But GTK3 should be stable now.

I am more interested in the question of whether it is at all possible to bring this binding to a satisfactory state, or whether GTK3 is simply not suitable as an LCL interface.

I would be interested from anyone who has delved deeper into this if there is any point in trying to fix things or if it is just hopeless.
What are the major sticking points?
Is it possible to get Synedit working?

[zeljko]

@Theo, yes, everything is possible, primary target to get synedit and painting to work properly is proper implementation of winapi functions (gtk3winapi) and lclintf (gtk3lclintf). After that resizing and other events should be fixed for widgets.
EDIT: Start from simple project with one form and synedit. Enable -dGTK3DEBUGNOTIMPLEMENTED  and see in console what is missing

[dbannon]

Gossip ?

My "report" was based on my own tests using published (by me) code in my app, about 27K lines of pascal code. Not test cases, user code that runs in Linux, MacOS, Windows, x86_64, i386, Arm (64, el, hf) and ppc64el. See -
https://tracker.debian.org/pkg/tomboy-ng

I'll try again -

Progress is being made !

Davo