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
Port GUIs from PyGTK/Gnome-2 to PyGobject/Gnome-3 #112
Comments
I did some lookup in the Web and it seems to be a good idea to do this change to prevent running into a dead-end on the long term. It seems to be no too difficult as there is some supporting tools for this. Nevertheless it'll take some time. So, it would be good, to have this sometimes in the 'near' future. |
I think it'll be quite a while before we can assume people will have pygobject and GTK-3 - even though I already have it on my home machines. It was also a little cheeky of them to recommend porting a year and a half ago, when the documentation is still a work in progress! |
(Or move to another modern GUI technology?) |
Any suggestions? I imagine that upgrading the existing GUI to pygobject and gtk-3 will be relatively easy, but making a completely new GUI that can compete with the current one would be a BIG job - we have invested a lot in it so far [update: I meant "in a short time", as we've long planned to move to RESTful http comms, which will open the door to other UI technologies]. |
(discussion of web UI technologies taken offline) |
[meeting] we agreed:
|
@cylc/core - extreme difficulty of installing PyGTK is frequently reported by those who don't have it available out of the box on their systems. Any updates on previous comment re going to PyGobject in the short term? |
This issue should cover |
Haven't we more or less decided not to do this, and go straight (within the next year, maybe) to web tech? |
Superseded by #1873. |
Software is a moving target ... The latest PyGTK release is the last of the line. The release announcement says:
The text was updated successfully, but these errors were encountered: