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.

Sign up for GitHub

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

Jump to bottom

Port to QT #2

Open

fsimonis opened this issue Apr 12, 2024 · 0 comments

Member

fsimonis commented Apr 12, 2024

I am considering to port the application to QT as using GTK has some severe downsides:

Barely existent documentation for python bindings
Inconsistently packaged pygobject among distros making it tricky to install
xdot (which I use for the dot preview) not being maintained any more and locking us into gtk3

Upsides of QT:

Very good documentation for the python bindings
Consistently packaged single dependency

Loosing xdot:

Render to svg/pdf and display it in a Qt window.
No node highlighting
Not sure about mouse-over hints
More functionality possible via xdot conversion, but this requires implementing many things from scratch. Not worth it for the extra functionality.

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment