Difference between revisions of "New features"

From VistrailsWiki
Jump to navigation Jump to search
(Created page with 'This is a list of work-in-progress features, or features that haven't been released in a 2.0.x version. == Core == === vistrails prefix === 'vistrails.' prefix added to package…')
 
 
(20 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This is a list of work-in-progress features, or features that haven't been released in a 2.0.x version.
This is a list of work-in-progress or unreleased features. See also the [[Development Branches|list of development branches]].*


== Core ==
== Features not on v2.1 branch ==


=== vistrails prefix ===
These features are on master but not on the v2.1 branch. (v2.1..master)
'vistrails.' prefix added to package names. Allows to use VisTrails as a library.


=== Multi-line string parameters ===
=== Packages ===


=== Bundles ===
Tabledata now has writer modules, BuildTable, Microsoft Excel support, JSON, join/select/project
Fixed and updated the bundle installation system. It allows to automatically install required Python packages when they are first imported without restarting VisTrails or entering commands.


Supports the 'pip' installer (on both UNIX and Windows), apt (through Python binding) and Fedora (with yum -- '''binding currently broken, only uses cmd''')
SQL package now uses SQLAlchemy. COMPATIBILITY: not compatible, because now returns a Table.


=== Automatic conversion ===
GMaps package
Connecting incompatible ports is possible if a Converter subclass exists for these specific types.


Documented in the users' guide.
RemoteQ package


=== Enumeration for module ports ===
HTTPDirectory, SSHDownloader, URLEncode, URLDecode, Cross, StringFormat, ReadFile
It is possible to declare the possible values on a module's input port; the UI then shows a combobox.


=== [[multithreaded-interpreter|Parallel execution]] ===
=== Improved module/parameter/widget configuration APIs ===
Changes to the interpreter allowing the parallel execution of modules in a pipeline.
 
rename-api, ???
 
=== Allows default values to be set by Python value ===
 
=== Associate with .vt and .vtl files on Linux ===
 
=== Schema and migrations for startup.xlm ===
 
=== Don't leak temporary files ===
 
=== Suspending modules and the job monitor ===
 
=== Package upgrades get chained ===
 
=== Automatic loops and streaming ===
 
???
 
=== Keeps input/output port of unconnected port when ungrouping ===
 
=== Allows reloading a disabled package ===
 
=== Export cells in different formats ===
 
=== Exporting version tree to graphviz DOT format ===
 
=== Control parameters ===
 
???
 
=== Debugger for code or package issues ===
 
=== Output modules ===
 
???


This is opt-in for modules and thus doesn't break modules that use thread-unsafe code. Supports threads, multiprocessing and IPython clusters.
=== Module Parmeter Widgets ===


Replaces parallelflow.
== Other features ==


== Packages ==
These features are not on master yet but rather on different branches. (--branches --not master)


=== parallelflow ===
=== Core ===
Provides a way to execute modules or groups on an IPython cluster, via a Map module. Also has IPython UI to set it up, and an API to use IPython in other modules.


Documented in the users' guide. First implemented in Oct, 2012 by Fernando.
==== [[multithreaded-interpreter|Parallel execution]] [work in progress, documented] ====
''(branches: multithreaded-interpreter, multithreaded-interpreter-target-seletion)''


Note that it becomes obsolete with multithreaded-interpreter although a lot of code was reused.
Changes to the interpreter allowing the parallel execution of modules in a pipeline.


=== matplotlib ===
This is opt-in for modules and thus doesn't break modules that use thread-unsafe code. Supports threads, multiprocessing and IPython clusters.
Replaces pylab with a better interface (specialized modules autogenerated from matplotlib's docstrings).


Lots of examples in examples/matplotlib/
Replaces parallelflow.


=== tabledata ===
==== New subworkflows (design phase) ====
A package allowing to load CSV files and NumPy arrays, to display them as a table and to convert between datatypes.
See [[SubworkflowsDesign]]

Latest revision as of 13:41, 1 October 2014

This is a list of work-in-progress or unreleased features. See also the list of development branches.*

Features not on v2.1 branch

These features are on master but not on the v2.1 branch. (v2.1..master)

Packages

Tabledata now has writer modules, BuildTable, Microsoft Excel support, JSON, join/select/project

SQL package now uses SQLAlchemy. COMPATIBILITY: not compatible, because now returns a Table.

GMaps package

RemoteQ package

HTTPDirectory, SSHDownloader, URLEncode, URLDecode, Cross, StringFormat, ReadFile

Improved module/parameter/widget configuration APIs

rename-api, ???

Allows default values to be set by Python value

Associate with .vt and .vtl files on Linux

Schema and migrations for startup.xlm

Don't leak temporary files

Suspending modules and the job monitor

Package upgrades get chained

Automatic loops and streaming

???

Keeps input/output port of unconnected port when ungrouping

Allows reloading a disabled package

Export cells in different formats

Exporting version tree to graphviz DOT format

Control parameters

???

Debugger for code or package issues

Output modules

???

Module Parmeter Widgets

Other features

These features are not on master yet but rather on different branches. (--branches --not master)

Core

Parallel execution [work in progress, documented]

(branches: multithreaded-interpreter, multithreaded-interpreter-target-seletion)

Changes to the interpreter allowing the parallel execution of modules in a pipeline.

This is opt-in for modules and thus doesn't break modules that use thread-unsafe code. Supports threads, multiprocessing and IPython clusters.

Replaces parallelflow.

New subworkflows (design phase)

See SubworkflowsDesign