Data Interface¶
Architecture¶
There are modules with the core data structures for each native data type: molecular data, sequence data, and volume data.
New data formats are registered with the “data formats” manager, and functions to read and/or write formats are registered with the “open command” and “save command” managers respectively. This is summarized briefly in Defining a File/Data Format, Opening Files, and Saving Files, and in more detail in the Bundle Example: Read a New File Format, Bundle Example: Save a New File Format, and Bundle Example: Fetch from Network Database tutorials.
Bundles may want to be able to react to various kinds of events, such as new models being opened, or the graphics window background coloring changing. When such events occur, a “trigger” will be fired, and functions that have been registered with the trigger will be executed and given data related to the trigger. The nuts and bolts of how to register for a trigger is described in triggerset: Support for managing triggers and handlers. Information about where widely-used triggers can be found, their names, and what data they provide can be found in Well Known Triggers.
Modules¶
- commands: Register user commands
- data_events: Support for bulk tracking of data changes
- objects: Manage objects
- session: Application session support
- triggerset: Support for managing triggers and handlers
- scripting: support reading and executing scripts
open_command_script()open_compiled_python_script()open_python_script()
C++ helper Modules¶
See also
- Readcif
C++ library for reading mmCIF files.
