Attendees

• Eric, TomG, Greg, Tristan

Agenda

• Action items
• ChimeraX
  • What version number for next release?
    • How to handle PySide2 -> Qt shim module change.
  • Who might take over ViewDockX dev? Can we get the SwissDock guys to work on supporting their output (#4232)? (currently their server provides a Chimera session)
  • Toolshed tickets
  • Bond-order depiction
    • approaches
    • priority
• Chimera

Discussion

• ChimeraX
  • Eric stuck with ViewDockX
  • Do nothing about version numbers since still PyQt5 compatible

• More ChimeraX
  • Bond order depiction requires knowing bond orders (Eric) and rendering (TomG). Make an enhancement ticket but seems too difficult.
  • ViewDockX is now owned by Eric. He can decide whether SwissDock is worth supporting.
  • Would be nice to improve the ViewDockX user interface replacing html by Qt in the future.
  • Next ChimeraX version
    • How to handle PySide2 being replaced by Qt shim module.
    • Discussed bumping core version to 2.0, or bumping ui version to 2.0 and requiring bundles to list a ui requirement.
    • Toolshed currently does not check whether the installed ChimeraX bundles meet requirements when presenting Install button on web page. If requirements are not met, pressing Install button will download wheel but fail when installing.
    • Discussed having separate ChimeraX app version, distinct from core version. App version could be a second version number defined in core.
    • Decided best to not bump core or ui version numbers. Next ChimeraX will use Qt shim but will also have PyQt5 which last ChimeraX 1.1 used so imports from PyQt5 will continue to work.
    • Next ChimeraX version will be 1.2, and core will be 1.2.
    • Remains to decide if bundles should list a requirement on Qt shim module. Discuss this at next meeting.

• Chimera

Action Items

• Make ticket for bond orders - Eric