Changes between Version 1 and Version 2 of Ticket #56139, comment 3


Ignore:
Timestamp:
Apr 13, 2018, 9:04:41 PM (6 years ago)
Author:
jwhowarth
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #56139, comment 3

    v1 v2  
    1 A few notes on how upstream has wired in the PyQt support. Pymol defaults to using PyQt if available and reverts to the Tk interface if it can't be found. However on darwin, the pymol display window only renders properly under PyQt if pymol is built with the --osx-frameworks option passed to setup.py. So on darwin, a single build really can't render properly on both Tk and X11. If the packaging were enhanced to support a -x11 variant that would have to be built without the --osx-frameworks setup.py option. Also, since pymol now defaults to using PyQt if available, such a -x11 variant would have to explicity pass '-N pmg_tk' to the shell script that starts up pymol in order to suppress the use of PyQt.
     1A few notes on how upstream has wired in the PyQt support. Pymol defaults to using PyQt if available and reverts to the Tk interface if it can't be found. However on darwin, the pymol display window only renders properly under PyQt if pymol is built with the --osx-frameworks option passed to setup.py. So on darwin, a single build really can't render properly on both PyQt and Tk/X11. If the packaging were enhanced to support a -x11 variant that would have to be built without the --osx-frameworks setup.py option. Also, since pymol now defaults to using PyQt if available, such a -x11 variant would have to explicity pass '-N pmg_tk' to the shell script that starts up pymol in order to suppress the use of PyQt.