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

Adopting a common branch #433

Open
rhfogh opened this issue Sep 6, 2022 · 1 comment
Open

Adopting a common branch #433

rhfogh opened this issue Sep 6, 2022 · 1 comment

Comments

@rhfogh
Copy link
Collaborator

rhfogh commented Sep 6, 2022

Unfortunately I missed the August meeting where this was on the agenda, but it would be good if we could discuss how we are planning to move towards using a common branch at the different beam lines. There are separate discussions for mxcubecore and mxcubeqt.

I do have a selfish interest: I am trying to integrate the GPhL workflow at different beamlines, and currently I have to code independently in four completely different branches: ALBA, EMBL-Hamburg, ESRF, and SOLEIL. Having one branch that many/all beamlines were at least close to would be a huge help. Of course upgrading production code is a lot of work, but it would be useful to agree on what we are aiming at and how current plans look.

mxcubeqt/develop has been mostly quiet since Ivars Karpics left. Could those of us who use the Qt version agree on a shared goal, and how we should move towards it? Can we agree on using either Qt4 or Qt5, and on other dependencies (including Python version)?

@rhfogh
Copy link
Collaborator Author

rhfogh commented Sep 7, 2022

Considering that PyQt4 is now barely downloadable, and that even four years ago other programs were stopping to support it in new versions, it would be really great if we could move up to PyQt5

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

1 participant