Forking GTK+ 3 #688
Closed
Secret-chest
started this conversation in
Ideas
Replies: 2 comments 3 replies
-
To see why GTK 4 is a bad choice, look at the new Inkscape menus which had to be used because GTK 4 doesn't support real menus. No nesting (!) - it just replaces the main menu, and much more. |
Beta Was this translation helpful? Give feedback.
3 replies
-
Indeed, AWF GTK 4 has submenus. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I agree GTK 3 is a very good toolkit and it's the best available. It has nice, powerful themeing, good layout features, clean bindings, touch support... It's a pleasure to work with, and I wouldn't want to switch to something else, nor do you have any plans to.
But the GTK 3 has some missing features: its file browser is very bad, it should be configurable; it will be unsupported and is considered outdated. Are you going to fork it?
Beta Was this translation helpful? Give feedback.
All reactions