Changes between Initial Version and Version 1 of 2014-09-11

Timestamp:

Sep 11, 2014, 4:13:39 PM (11 years ago)

Author:

Conrad Huang

Comment:

--

2014-09-11

@@ +1 @@
+= 11 September 2014 meeting =
+
+== Attendees ==
+
+TomF, Greg, Eric, Conrad
+
+== Agenda ==
+
+Discussion about how Chimera2 start up sequence.
+
+== Action Items ==
+
+Conrad: Toolshed API
+Eric: Path Initialization API
+Greg: Command-line Parsing API
+Greg: Environment Preservation and Monkey Patch API
+TomG: Presentation of Hydra architecture and migration path
+
+== Results ==
+
+After much discussion, we agreed to the following initialization sequence:
+
+1. Command line parsing
+1. Preserve execution environment and monkey patch Python
+ - Programs included with Chimera, eg al2co, will execute with the same environment as Chimera while system programs will execute with the preserved environment
+1. Setup paths
+ - Chimera paths (where "system" files live)
+ - Per-user paths (where user data and tools live)
+1. Initialize "stdio" or UI toolkit, eg splash screen
+ - Establish presence and both status and error reporting channels
+1. Initialize preferences
+1. Initialize core, eg molecular data, surface, triggers, etc.
+1. Initialize tool shed
+ - Tool shed should support "safe mode" where no tools are loaded
+ - Tool shed can support, possibly in conjunction with preferences, disabling certain tools
+ - Find list of "tool" (which can be Chimera-style tools, commands, data formats, libraries, shared objects, etc)
+ - Each tool has attributes, eg commands, menus, buttons, that can be queried, eg by UI
+ - Each tool has methods, eg "start" for creating an instance of the tool
+  - This is how tools can communicate
+  - "start" returns a !ToolInstance that implements the actual functionality
+ - !ToolInstance has a different API than Tool
+ - Some Tool's have a singleton !ToolInstance while others may be multi-instanced
+1. Initialize UI and OpenGL
+1. Add tool interfaces to UI
+ - App queries tool shed for list of tools and then tells UI what to do
+1. Execute custom Tool initialization code
+ - App queries tool shed for list of tools and use Tool API to check for init code
+1. Process command line requests
+ - Open files
+ - Run scripts
+ - Start Tools
+ - Restore sessions
+1. Enter event loop
+
+Eric described his approach to replacing Qt with wx in Hydra.  We decided that we need more information on the Hydra architecture in order to decide on how best to proceed with further development (eg continue Hydra code base, move components into core, etc.)