Why Gtkmm Over Qt? · Issue #413 · Giuspen/cherrytree - GitHub

Skip to content Dismiss alert {{ message }} giuspen / cherrytree Public

• Notifications You must be signed in to change notification settings
• Fork 500
• Star 3.8k

• Code
• Issues 906
• Pull requests
• Discussions
• Actions
• Projects
• Security

  Uh oh!

  There was an error while loading. Please reload this page.

• Insights

Additional navigation options

Why gtkmm over qt? #413New issueCopy linkNew issueCopy linkClosedClosedWhy gtkmm over qt?#413Copy linkLabelstopic: install\running\future

Description

ghostopened on Oct 19, 2018

1. Qt is the best option because it's a C++ native library. GTK+ is a C library and gtkmm is a C++ wrapper that leads to some problems... A lot of people just don't like how it feels.

2. Either you code the GUI by hand or you switch to Qt and use QtCreator.

3. IMO C++ is a mess that also has its part on why gtkmm is so hard.

4. https://www.youtube.com/watch?v=ON0A1dsQOV0

Gtk is badly documented. The Gtk community is indifferent to issues at best and gives non answers or abuse to questions. Gtk is primarily a GNOME project, cross platform (anything outside GNOME) is ugly, buggy and not a priority.

I really like this project and wanted to help expand it. Finding the ridiculous 5K LOC core.py file with repeated functionality was very depressing so I was glad that a transition to C++ was occurring, but I've noticed the progress is slow. Of course you've mentioned your family keeping you busy, but I can't also help but feel like GTK is part of the problem...

What am I not seeing in gtkmm that you're seeing?

👍React with 👍1huseyin1419

Metadata

Metadata

Assignees

No one assigned

Labels

topic: install\running\future

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

You can’t perform that action at this time.