Attendees

Elaine, Eric, Conrad, Greg, TomG

Agenda

• Updates [All]
• split alias into command vs. selector
• cli command recording API
• error handling
• help
• toolshed web site
• motion/movie/animation commands
  • currently listed under "Eventually" in the EarlyReleaseRequirements and Needed Command Functionality

Discussion

• Updates
  • Eric
    • Chain merging works at C++ level
    • Refactored io.open to io.open_filename and io.open_data
    • Finished record dialog for command line
    • Status line immediately updates instead of "callAfter"
    • Started mol2io (2 lines of code)
    • Started refactoring error exceptions
  • Greg
    • Single quotes are accepted in strings as well as backslashed quotes (quotes only are quoted when surrounded by whitespace or ends of strings)
    • Fixed unicode escapes in strings
    • Made alias part of cli public so other commands can use it
  • Conrad
    • "Finished" main save dialog
    • Working on "ecolor" command, "sequential" keyword
  • TomG
    • Low-res Gaussian molecular surfaces
    • "sym" command to show mmCIF molecular assemblies (mmCIF API extension to return requested table data will be the approach to take in the future)
    • Investigate headless Chimera 2 (mainly for PDB). "Looks bad." OSMESA probably will not work since it provides only OpenGL 2 and older shader language. EGL on Linux requires running X server (but may be the best option).
    • 2D labels and movie commands added for Megan.
• cli command recording API
  • option 1 is to have cli function that takes the command function and arguments, log and execute. This is problematic if the command function is in a tool module.
  • option 2 is to require caller to generate the command text and run it through cli. cli will provide function to quote (if necessary) arguments and keywords.
  • option 2 is the current plan.
  • Commands are displayed in log. Do they appear in command history (so they can be easily reused)? Yes, with the command line providing option to display "all commands" or "typed commands".
  • Make registered command function have return values. The return values are discarded by, for example, command line tool, but can be very useful when used in scripts. result = runCommand("my command")
• error handling
  • Greg will look into ctypes handling of C vs Python shared libraries.
  • Eric will look into how hard it would be to eliminate existing throws.
• Meeting adjourned
• help
• toolshed web site

Action Items

• Greg will look into ctypes using C vs Python shared libraries to minimize error checking overhead. Report back on performance hit compared to no error checking. How does an error deep down the stack exit in the throw-like manner?