The images below are screen captures showing different aspects of the pypes visual designer.
The main window of the pypes visual design studio. This shows pypes running in Google Chrome. The interface is very similar to Yahoo! Pipes in that you essentially drag components from the left pane onto the canvas area. Components can then be connected by dragging your mouse from the output port of one component to the input port of another.
The data stream can be split and merged when necessary. The small pink "x" in the upper right corner of the component is used to destroy or delete a component. The small blue "+" brings up a configuration dialog for the component, allowing users to define runtime parameters.
The upper right corner of the canvas displays a "canvas map" which provides an arial overview of the entire canvas. This is useful when you have large workflows that cause the canvas to scroll.
Pypes provides a basic authentication model that restricts the application using simple password protection.
This shows the configuration dialog for the DateNormalizer component. This component is used to transform dates to a defined format. The configuration dialog provides a way for users to specify input parameters specific to their needs. In this case we're specifying a few different input formats to look for, the field or fields that might contain dates we want to normalize, and the output format we would like to use.
Date format strings are standard Python strftime() format specifiers.
This image shows a focused view of the component pane. Components are broken into categories to ease the browsing of (potentially) large lists. Each group can be expanded or contracted by clicking on the group name. Here, the Adapters group is expanded to show various components that provide the ability to adapt incoming input types.
Pypes provides the ability to export project configurations. A project is nothing more than a JSON structure used to represent various aspects of the project (right down to the coordinates in the window). These configurations can be shared via email or otherwise and can safely be modified by hand. The typical use case here is exporting a configuration to other nodes acting as part of a document processing cluster. The prevents you from having to configure each node with the current project workflow.
An image showing the about dialog.