Make "usage open" report some option info

[goddard@…]

The following bug report has been submitted:
Platform:        Darwin-19.4.0-x86_64-i386-64bit
ChimeraX Version: 1.0 (2020-06-04 23:15:07 UTC)
Description
"usage open" gives no useful information on the options for the command.

Log:
UCSF ChimeraX version: 1.0 (2020-06-04)  
© 2016-2020 Regents of the University of California. All rights reserved.  
How to cite UCSF ChimeraX  

> usage open

open fileNames restOfLine  
— Open/fetch data files  
fileNames: file names to open  
restOfLine: the rest of line

open formats  
— report formats that can be opened  




OpenGL version: 4.1 ATI-3.8.24
OpenGL renderer: AMD Radeon Pro Vega 20 OpenGL Engine
OpenGL vendor: ATI Technologies Inc.Hardware:

    Hardware Overview:

      Model Name: MacBook Pro
      Model Identifier: MacBookPro15,3
      Processor Name: 8-Core Intel Core i9
      Processor Speed: 2.4 GHz
      Number of Processors: 1
      Total Number of Cores: 8
      L2 Cache (per Core): 256 KB
      L3 Cache: 16 MB
      Hyper-Threading Technology: Enabled
      Memory: 32 GB
      Boot ROM Version: 1037.100.362.0.0 (iBridge: 17.16.14281.0.0,0)

Software:

    System Software Overview:

      System Version: macOS 10.15.4 (19E287)
      Kernel Version: Darwin 19.4.0
      Time since boot: 27 days 21:23

Graphics/Displays:

    Intel UHD Graphics 630:

      Chipset Model: Intel UHD Graphics 630
      Type: GPU
      Bus: Built-In
      VRAM (Dynamic, Max): 1536 MB
      Vendor: Intel
      Device ID: 0x3e9b
      Revision ID: 0x0002
      Automatic Graphics Switching: Supported
      gMux Version: 5.0.0
      Metal: Supported, feature set macOS GPUFamily2 v1

    Radeon Pro Vega 20:

      Chipset Model: Radeon Pro Vega 20
      Type: GPU
      Bus: PCIe
      PCIe Lane Width: x8
      VRAM (Total): 4 GB
      Vendor: AMD (0x1002)
      Device ID: 0x69af
      Revision ID: 0x00c0
      ROM Revision: 113-D2060I-087
      VBIOS Version: 113-D20601MA0T-016
      Option ROM Version: 113-D20601MA0T-016
      EFI Driver Version: 01.01.087
      Automatic Graphics Switching: Supported
      gMux Version: 5.0.0
      Metal: Supported, feature set macOS GPUFamily2 v1
      Displays:
        Color LCD:
          Display Type: Built-In Retina LCD
          Resolution: 2880 x 1800 Retina
          Framebuffer Depth: 24-Bit Color (ARGB8888)
          Main Display: Yes
          Mirror: Off
          Online: Yes
          Automatically Adjust Brightness: No
          Connection Type: Internal

PyQt version: 5.12.3
Compiled Qt version: 5.12.4
Runtime Qt version: 5.12.8

[Tom Goddard]

The old "usage open" gave some useful options like "models <spec>", .... In fact it gave all the options and you didn't know which formats they applied to. That was not great but was better than what it does now. Not sure how to make it give nice output since there are many formats and spewing options for all formats is probably too much. Spewing all options like it did before would still be better than what it does now.

I looked for another ticket on this since I know you are aware of the problem, but I didn't find an earlier ticket.

[Eric Pettersen]

This is fixed, but the fix isn't committed to the develop branch yet because I want to put a 1.0-compatible open-command bundle on the toolshed (for a different set of changes), and the usage changes require a 1.1 core (I made part of the core command-usage API public). So, I _was_ going to wait until we were putting bundles on the Toolshed to do these things. Alternatively, I could stash the open-command wheel somewhere and then go ahead and push the usage changes.

[goddard@…]

Up to you.  Wanting usage for open and save is probably not too uncommon, probably save is more frequent.  If it is going to be delayed 3 months might be worth doing the stash to allow pushing the usage upgrade.

[Eric Pettersen]

I guess I'll see what shakes out toolshed-wise in the next week and make a command decision next Friday.

[Eric Pettersen]

Since 1.1 is going to be "sooner rather than later", I decided to put basically no new bundles on the Toolshed, which means I could just go ahead and push this usage implementation to develop.