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

Suggestion: Use AI or Github co-pilot to convert source to utilize latest Python version (3.x+) and GTK 4. #34

Open
mknepper opened this issue Nov 19, 2024 · 1 comment

Comments

@mknepper
Copy link

Just throwing this out there, but it might be possible to have GPT4 or GPT4o or Co-Pilot help in converting the codebase to Python 3+ and GTK4. I'm really new to this and I have co-pilot, but I'm not sure where to start. Perhaps we can make a Discord, Teams, or Matrix channel to discuss this?

@takluyver
Copy link
Member

Interesting idea, but in fact I've already done most of the move to Python 3 & GTK 3 in a branch called gtk3. The bits that I imagine AI could do well are probably done already, and also aren't that difficult to do with find & replace.

The bits that it got stuck on are very specific. For a long time certain pango APIs were just not accessible through the introspection layer, so there was no way to port parts of the old pygtk code to PyGObject. Eventually that got fixed, but by the time it did I don't have much time to spend on Labyrinth, and the longer I leave it, the closer it is to understanding a project from scratch when I get back to it.

The last time I did anything on it was in 2021. I think if I got it working well enough, I was planning to give it a new storage location and a way to migrate maps from the old storage, so that people would have the original files if it messed anything up. I forget how close I came - feel free to try that branch and see. I think there might have been some challenges with coordinates (what's relative to the widget, the window, the screen or the desktop).

Perhaps we can make a Discord, Teams, or Matrix channel to discuss this?

Feel free to keep using this issue tracker for discussions; I don't think it's worth setting up another communication channel for a project that's so barely alive. It's been over 2 years since someone last opened an issue!

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

No branches or pull requests

2 participants