Simple Python Scripting

From ParaQ Wiki
Revision as of 14:58, 7 August 2008 by Utkarsh (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

GUI and server manager API should be as close to each other as possible.

  • Sources and filters are similar - they both have objects (python and visual) associated with them. Users create them and manipulate them.
  • Readers - create server manager reader factory and have GUI and python use it both. There should be a method that returns a reader object given a filename.
  • Writers - similar to readers. Add method that writes a file given a source proxy and a filename.
  • Views - similar between GUI and python. Server manager should keep the layout so that it can be controlled from python also. When created from python, views should behave same as when created from GUI. We need to be able to set defaults - background color, manipulators etc.
  • Representations - more advanced that others but still a useful concept. We should make its API simpler by creating a python wrapper. For example, it is hard to set a color map.
  • Animations - need to create a wrapper layer in server manager.
  • Meta-data - create a more python friendly data structure for meta-data (dictionary?)
  • If data is fetched to client, it should be accessible from the numpy interface
  • There should be a way of "pushing" data to server
  • Instead of registration group, use addToGUI() and remoteFromGUI() methods.
  • Have a servermanager level array name to lookup table mapper which the the GUI as well as python use to assign LUT for coloring. Provide simple API in python to select array to color and use default LUT.
  • Python should have LUT presets.