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.

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

Stop using lablgtk #1075

Open
gdt opened this issue Nov 1, 2024 · 2 comments
Open

Stop using lablgtk #1075

gdt opened this issue Nov 1, 2024 · 2 comments
Labels
discuss way forward is unclear; needs discussion of approach to take and why effort-high issue is likely to require >20h of effort, perhaps much more enhancement issue is a request for a feature, and not a defect impact-high high importance

Comments

@gdt
Copy link
Collaborator

gdt commented Nov 1, 2024

lablgtk seems to be not really maintained, and a number of serious bug reports remain open. Long term, we should stop using it, which means either not having a GUI, using some other bindings from ocaml, or having some kind of control API and a GUI written in some other language. Or something else I haven't thought of.

Followups on -hackers please. This is simply a placeholder issue that the current situation is unsound.
@gdt gdt added enhancement issue is a request for a feature, and not a defect effort-high issue is likely to require >20h of effort, perhaps much more impact-high high importance discuss way forward is unclear; needs discussion of approach to take and why labels Nov 1, 2024
Repository owner locked as too heated and limited conversation to collaborators Nov 1, 2024
@gdt
Copy link
Collaborator Author

gdt commented Nov 1, 2024

This comment (to be edited over time) is the list of lablgtk issues that have an impact on unison:

@gdt
Copy link
Collaborator Author

gdt commented Nov 1, 2024

This comment (to be edited over time) collects pointers to workarounds for issues with lablgtk:

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
discuss way forward is unclear; needs discussion of approach to take and why effort-high issue is likely to require >20h of effort, perhaps much more enhancement issue is a request for a feature, and not a defect impact-high high importance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gdt