vistrails / vistrails Goto Github PK

[Originally Ticket 22, reported by emanuele]

Testing sending e-mail when creating tickets.

[Originally reported by cscheid]

Need some some way to ‘zoom’ in the canvases since it becomes difficult to see what is going on. NOTE: ‘option drag’ will do it, but there is no indication to the cursor to give indication of a change (or right mouse button on 3 button mouse). But how do I ‘drag’ around the canvas? Use ‘shift’ drag (or center mouse button on 3 button mouse). When I do the ‘drag’ the ‘grid’ lines in the pipeline are erased when they go outside the bounds. [Would be nice if the tool bar included ‘modes’ for the cursor and if you hold down the modifier key the appropriate mode is highlighted]. Would also be nice to have scroll bars and push-buttons to do zoom (a scroll wheel?)

[Originally Ticket 16, reported by cscheid]

Why can I choose a module ‘abstract’ base class (e.g. vtkBaseModule) and put it on the pipeline when it can’t do anything?

[Originally reported by cscheid]

The actual interpolation used for parameter exploration should be pluggable.

We should have at least these modes of operation:

1) Default per-type exploration (we currently have numbers → linear interpolation; string → lists)

2) Completely custom exploration:
2a) user defines a function (by typing it a la PythonSource)
2b) user chooses a function he’s already defined in his .vistrails/startup.py

3) How do we specify a custom GUI? We can’t have users touching Qt..

[Originally reported by eranders]

Many applications rely on user interaction in order to properly visualize the right things. For this, a new type of spreadsheet widget and communication must be created to take care of the “Display, Select, ReVisualize” type interactions. For instance, when visualizing the CORIE stuff, I wouldn’t be surprised if they wanted to see a visualization of their data as it is done now, but to further investigate some weird result they see, they want to be able to click on a labelled buoy and get the information about that one set of sensors. Or with Gil, click on a sensor and get sensor-specific data.

[Originally reported by cscheid]

We need some features from parameter exploration that are not there yet.

1) We need parameter exploration “by list”, and not only by linear interpolation, even if the values are floats. (I want to explore over values = {0.25, 0.5, 1.0, 2.0, 4.0})

2) We need to “split” explorations of a single function call along multiple dimensions. For example, the port “AB” in Teem’s ellipsoid generator right now has to be split in “A” and “B” so we can reproduce this figure using parameter explorations:

http://www.sci.utah.edu/~gk/vissym04/super/index.html

[Originally Ticket 28, reported by cscheid]

Since we’re releasing it with the GPL, we have to change this…

[Originally Ticket 1, reported by cscheid]

If we drop a module method inside the modulemethodarea’s textbox, we get python’s pickled string. We should simply disallow this drop.

[Originally Ticket 26, reported by cscheid]

HTTPFile should report a wrong address, not crash

[Originally reported by cscheid]

On linux, now the default mouse pointer is the “zoom” one. This doesn’t happen on the Mac.

[Originally Ticket 15, reported by cscheid]

If no ‘homeDirectory/.vistrails’ file/directory exists, VisTrails does not report a problem and runs ‘merrily’ along although it is missing all ‘external’ packages.

We should warn the user and tell him to use the file for packages, even though this will be all GUI in the future.

[Originally Ticket 25, reported by cscheid]

Too many bugs to mention any one in particular :) Arithmetic is incorrect, no handling of localtime vs GMT. I’ll reimplement it.

[Originally reported by cscheid]

When saving/loading a file that has a Tuple with more than one element connected to something else, the XML written is corrupted because the spec has extra spaces.

[Originally Ticket 7, reported by cscheid]

clicking the close button on the “Search & Refine”, “Properties” panels from the version tree ( and similar ones from the pipeline view and query view) deletes the panels without a way for them to come back. They could be added to the “view” main menu, for example.

[Originally reported by cscheid]

VisTrails should install a default startup.py if none is present.

[Originally Ticket 9, reported by cscheid]

Why is the ‘view the whole version tree with all move actions’ widget selectable when the version tree is not being shown?

[Originally Ticket 23, reported by cscheid]

VisTrails Diff between two version whose common parent is the empty version doesn’t work

[Originally Ticket 6, reported by cscheid]

There should be an undo-redo stack. This should be trivial to implement by simply keepiong a stack of the visited versions. Undo pushes the stack, redo pops.

[Originally reported by cscheid]

Ports that have tuple types are not working on the trunk. Test case: take vtk_http.xml, add a contour filter to tetra mesh and SetValue to anything. Now do the same on r389.

[Originally reported by emanuele]

[Originally Ticket 19, reported by cscheid]

The command-line option to load a vistrail will only work for one vistrail. If the user tries to open more than one, only the first one gets loaded.

We should either signal an error or load all of them.

[Originally Ticket 20, reported by cscheid]

I don’t think the PIP window should ever be disabled. Also, we should just find a sensible place for it and not allow changes in size. It gets confusing to see whether mouse actions will change the PIP widget or the contents of it.

[Originally Ticket 2, reported by cscheid]

resolveAliases() has GUI code, and when workflow execution happens on a separate thread, this calls GUI code. Qt can’t be called from different threads, and that’s why we get the race condition and crash. I worked around that by making everything single-threaded again, but we want to fix that in the future.

[Originally reported by emanuele]

[Originally Ticket 4, reported by cscheid]

If no ‘version node’ is selected, then you can not drag a module to the pipeline and there is no feedback as to why the operation is not allowed. If there is only one version node, then it should not be ‘unselectable’. Also, does anything work if no versions selected? If so, then the GUI should not let an ‘unselect’ happen.

[Originally reported by emanuele]

The button is not there nor a menu option to toggle the complete tree.
Have I missed any commit messages?

[Originally Ticket 13, reported by cscheid]

Double clicking on a Module in the pipeline you get a ‘modal’ dialog to modify it. It would be nicer if this was non-modal.

[Originally reported by hvo]

When holding Alt on Linux, the cursor switch to Zoom mode with a magnifier icon. But if we then press Alt+Tab, then the Alt key release signal is lost to the system causing the frozen magnifier icon. Also when we Alt+Left Click on Linux, it doesn’t zoom because of the shortcut from most Linux manager, e.g. Alt+Left Click == Move the current window

[Originally reported by eranders]

During resizing of a spreadsheet cell, the cell ‘snaps’ back and forth between where the cursor is and somewhere in between the cursor and original position.

This has been tested on Windows XP.

To reproduce:
Open spreadsheet
Go to resize a single cell in a multi-cell spreadsheet.
During resizing, the snapping behavior will happen

[Originally Ticket 17, reported by cscheid]

The GUI lets you save the workflow without an extension and then you can not reopen it (without adding the extension).

[Originally Ticket 21, reported by cscheid]

VTKCell spreadsheet widgets don’t work on Linux. Everytime a pipeline with a VTKCell gets executed, a new VTK window pops up, but no interaction with that or the spreadsheet cell is possible. The VTK window only goes away when the application is terminated.

[Originally reported by cscheid]

subprocess.popen seems to trigger a race condition when used in conjunction with wait(). This seems to be a python bug, not a VisTrails bug, but we’ll have to work around it.

Here’s some more info on the same problem:

http://twistedmatrix.com/trac/ticket/733

Thanks for Marty for spotting this on the ImageMagick package.

One possible workaround is to change all the subprocess calls to a os.system(“foo >redirect”), but that’s reasonably ugly.

[Originally reported by emanuele]

[Originally Ticket 30, reported by emanuele]

The default behavior of dragging a item from a QTreeWidget on Macs is to remove the item from the list. The user must press alt when dragging for the item tobe copied.

[Originally reported by cscheid]

PythonSource should have a checkbox that enables caching. Right now, the only way of making this work is too ugly (write ‘self.is_cacheable = lambda *args: True’ in the code)

[Originally Ticket 29, reported by cscheid]

Copy and Paste stops working after you pasted things once on the pipeline. Here’s how to reproduce it.

Create a new vistrail, drag two pythoncalcs, connect them, copy them, paste them.

Now try to select two other modules and copy them. VisTrails freezes for ~5 seconds and the terminal reports “QClipboard: Cannot transfer data, no data available” ~10 times.

[Originally Ticket 10, reported by cscheid]

Setting ‘ports’ in PythonSource is tricky, I have to ‘tab’ and not hit ‘return’ since the ‘return’ seems to make me lose what I did.

[Originally Ticket 27, reported by cscheid]

Here’s the traceback:

Traceback (most recent call last):
File “C:\Documents and Settings\vgcuser\Desktop\vistrails_svn\trunk\vistrails\gui\builder_window.py”, line 335, in saveVistrailAs
self.viewManager.saveVistrail(None, str(fileName))
File “C:\Documents and Settings\vgcuser\Desktop\vistrails_svn\trunk\vistrails\gui\view_manager.py”, line 158, in saveVistrail
vistrailView.controller.writeVistrail(str(fileName))
File “C:\Documents and Settings\vgcuser\Desktop\vistrails_svn\trunk\vistrails\gui\vistrail_controller.py”, line 569, in writeVistrail
if self.vistrail and (self.changed or fileName!=name):
NameError: global name ‘name’ is not defined

I haven’t tried to fix this because there’s no “name” variable in the function, so I don’t know where it should come from.

[Originally reported by cscheid]

We should be able to drag Tuple modules into the builder just like Floats, Strings, etc. When double-clicking on the tuple, it should be possible to specify the type (arity and values), and the output should be the appropriate tuple.

[Originally reported by hvo]

After being used by several pipelines, a VTK cell on the spreadsheet can get very slow. Looks like OpenGL context leaks.

[Originally Ticket 24, reported by cscheid]

We must design and implement a way to document which packages are required by a vistrail.

[Originally reported by emanuele]

If we are going to allow this, the resolveAlias mechanism and bookmarks must be reviewed.

[Originally reported by eranders]

Vistrails under Ubuntu Linux does not seem to have spreadsheet cell synchronization working. After running several visualizations and selecting any combination of active cells, either by shift + click, the whole row, the whole column OR the whole spreadsheet interaction is not synchronized across the cells. The cells change color to indicate they are grouped, but interaction remains localized to the currently active cell.

This may be unique to Ubuntu Edgy distribution.

[Originally Ticket 5, reported by cscheid]

There should be a shortcut for running a pipeline.

[Originally Ticket 8, reported by cscheid]

PIP mode should be enabled by default, with preferably no way to disable. There’s no reason users might not want it. The clutter of the additional button is worse than the clutter of the PIP there, particularly since the PIP window size can be tweaked.

[Originally Ticket 14, reported by cscheid]

Having the ‘toolbar’ with the ‘run pipeline’ icon at the bottom of the main window breaks the standard layout where toolbars are at the top. I continually find myself sending the cursor to the top of the window in order to ‘run the pipeline’ and then remembering that the icon is at the bottom. I did determine that I can drag that toolbar up to the top of that frame.

[Originally Ticket 3, reported by cscheid]

On the new interface, double-clicking on the link with the ellipsis (the three “dots”) does not expand it to the full view.

[Originally reported by cscheid]

When we Copy/Paste a Tuple we should either make sure the types are equivalent (using the right registry) or we should erase the parameters passed to it.

[Originally Ticket 12, reported by cscheid]

On the Mac, if I start VisTrails from the terminal shell, the messages are sent to that shell until I open a ‘VisTrails shell’ and then it goes to VisTrails shell and not the terminal shell.

[Originally Ticket 18, reported by cscheid]

The -w option to give a startup workflow does not appear to work when running interactively.