Difference between revisions of "Undocumented Features"
Jump to navigation
Jump to search
m |
|||
Line 2: | Line 2: | ||
* Many items in the [http://www.vistrails.org/index.php/FAQ FAQ] | * Many items in the [http://www.vistrails.org/index.php/FAQ FAQ] | ||
* New syntax for specifying modules in packages (<code>_input_ports</code>, <code>_output_ports</code>, <code>_modules</code> | * New syntax for specifying modules in packages (<code>_input_ports</code>, <code>_output_ports</code>, <code>_modules</code>) | ||
* Shortcuts for specifying ports (default to current package, allow 'edu.utah.sci.vistrails.basic' to shorten to 'basic') | * Shortcuts for specifying ports (default to current package, allow 'edu.utah.sci.vistrails.basic' to shorten to 'basic') | ||
* Manipulate workflows via the shell (<code>load_package</code> and then add modules, connections, and parameters) | * Manipulate workflows via the shell (<code>load_package</code> and then add modules, connections, and parameters) |
Revision as of 22:10, 23 February 2011
Features that should be added to the VisTrails Users' Guide
- Many items in the FAQ
- New syntax for specifying modules in packages (
_input_ports
,_output_ports
,_modules
) - Shortcuts for specifying ports (default to current package, allow 'edu.utah.sci.vistrails.basic' to shorten to 'basic')
- Manipulate workflows via the shell (
load_package
and then add modules, connections, and parameters) - Better docs on groups/subworkflows and some integration with control flow
- Publication tools (embed in LaTeX, PowerPoint)
- crowdLabs publishing
- Merge documentation (Tommy's code to merge vistrails)
- Persistence package documentation and general tips on data management with VisTrails
- Vistrail/workflow browser documentation
- ...