Changes between Initial Version and Version 1 of 2015-7-23


Ignore:
Timestamp:
Jul 23, 2015, 3:37:07 PM (10 years ago)
Author:
Conrad Huang
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • 2015-7-23

    v1 v1  
     1= Attendees =
     2
     3  Elaine, Eric, Conrad, Greg, TomG
     4
     5= Agenda =
     6 * Updates [All]
     7 * split alias into command vs. selector
     8 * cli command recording API
     9 * error handling
     10 * help
     11 * toolshed web site
     12 * motion/movie/animation commands
     13   * currently listed under "Eventually" in the [[EarlyReleaseRequirements]] and [[Needed Command Functionality]]
     14
     15= Discussion =
     16 * Updates
     17   * Eric
     18     - Chain merging works at C++ level
     19     - Refactored io.open to io.open_filename and io.open_data
     20     - Finished record dialog for command line
     21     - Status line immediately updates instead of "callAfter"
     22     - Started mol2io (2 lines of code)
     23     - Started refactoring error exceptions
     24   * Greg
     25     - Single quotes are accepted in strings as well as backslashed quotes (quotes only are quoted when surrounded by whitespace or ends of strings)
     26     - Fixed unicode escapes in strings
     27     - Made alias part of cli public so other commands can use it
     28   * Conrad
     29     - "Finished" main save dialog
     30     - Working on "ecolor" command, "sequential" keyword
     31   * TomG
     32     - Low-res Gaussian molecular surfaces
     33     - "sym" command to show mmCIF molecular assemblies (mmCIF API extension to return requested table data will be the approach to take in the future)
     34     - 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).
     35     - 2D labels and movie commands added for Megan.
     36 * cli command recording API
     37   - 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.
     38   - 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.
     39   - option 2 is the current plan.
     40   - 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".
     41   - 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")''
     42 * error handling
     43   - Greg will look into ctypes handling of C vs Python shared libraries.
     44   - Eric will look into how hard it would be to eliminate existing throws.
     45 * ''Meeting adjourned''
     46 * help
     47 * toolshed web site
     48
     49= Action Items =
     50 * 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?