Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gtk2 is very old and being replaced by gtk3 or even gtk4 #530

Open
alexmyczko opened this issue Aug 25, 2022 · 7 comments
Open

gtk2 is very old and being replaced by gtk3 or even gtk4 #530

alexmyczko opened this issue Aug 25, 2022 · 7 comments
Labels

Comments

@alexmyczko
Copy link

What is the state for lazpaint about GTK?

@circular17
Copy link
Collaborator

That’s the state of the LCL, Lazarus Component Library, which LazPaint relies on.

@alexmyczko
Copy link
Author

do you of them plans to upgrade to 3 or 4 this or next year?

@fredvs
Copy link
Member

fredvs commented Sep 7, 2022

Or migrate to msegui?
Ok je sors....

@circular17
Copy link
Collaborator

Well that's not absurd actually, but... I would need much spare time.

I suppose it would solve all widget sets problems as it is all custom drawn?

@fredvs
Copy link
Member

fredvs commented Sep 8, 2022

Well that's not absurd actually, but... I would need much spare time.

I would help with great pleasure.

I suppose it would solve all widget sets problems as it is all custom drawn?

Yes all is configurable, even the shape of the frames. I did a rapid check and all the widgets used in LCL LazPaint have equivalent in msegui.

Also you would be totally independent of widget-set versions (like GTK2, GTK3, Qt2, Qt3).
Even more LazPaint will run on a "Pure X" system ( without GTK or Qt or other widgetset installed.)

Of course lt will need some work but all the methods can be copied and, big advantage, msegui is BGRAbitmap already compatible.

The bemol, msegui, at the moment, is only Linux, FreeBSD and Windows compatible but not yet Mac (that could still use the LCL version).

@circular17
Copy link
Collaborator

Ok I understand. So one would need to be able to handle either LCL or mseGUI.

@fredvs
Copy link
Member

fredvs commented Sep 10, 2022

You mean that Lazpaint-LCL and LazPaint-mseGUI should share the same lazpaint-units for what is not graphic (like type, var, methods, ...)?
If so that is the best, you can also imagine to use other widget-sets.

But lot of work... ( tant mieux ;-) )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants