Version 2 - Revision history

Emanuele: /* Tommy's comments on tabs */

2011-06-07T15:59:21Z

Tommy's comments on tabs

← Older revision		Revision as of 15:59, 7 June 2011
Line 110:		Line 110:
	* What is a tab?		* What is a tab?
	** Each tab represents a view for a specific vistrail		** Each tab represents a view for a specific vistrail
	** All tabs ~~uses~~ the same global toolbar		** All tabs use the same global toolbar
	** We may need to have mode buttons for each tab to avoid confusion.		** We may need to have mode buttons for each tab to avoid confusion.
	** A tab should only contain one of the possible modes. PiP should be okay but the visual diff should open in a new window.		** A tab should only contain one of the possible modes. PiP should be okay but the visual diff should open in a new window.
Line 117:		Line 117:
	** The main window is responsible for switching vistrails.		** The main window is responsible for switching vistrails.
	Is it useful to have stacked tabs when we can only see one of them at a time and they are all a view of the current vistrail? Maybe we should always open them in a new window.		Is it useful to have stacked tabs when we can only see one of them at a time and they are all a view of the current vistrail? Maybe we should always open them in a new window.

			[ES] I agree that we need to improve the way we handle tabs.

			'''Currently''', when you create/open a vistrail, a vistrail view containing all the views (pipeline, history, parameter exploration, etc.) created in a stacked widget and you have a single tab that displays the current view. You switch views by pressing the buttons in the top toolbar. You can also create other pipeline tabs. All vistrail views (including their tabs) share the same toolbar and global palettes.

			'''My suggestion''' is that a vistrail view can use multiple tabbed windows. It starts with one single window, similar to what we have now, but when you drag the tab outside, it duplicates the top toolbar on the new window. You can add a tab to one of these windows. So the current state would be composed by current_vistrail_view, current_tab_window, current_tab. The palettes would still be global. In terms of implementation, we will just have to add another element in the hierarchy that will take over some of the behavior of the current vistrail view and vistrails window. Almost all the logic to keep track of action states that is in place wouldn't change. So notice that we don't have the concept of a main window anymore. The global palettes will function as the access point to the other views. For example, you change vistrails using the workspace panel.

Tommy at 13:58, 7 June 2011

2011-06-07T13:58:03Z

← Older revision		Revision as of 13:58, 7 June 2011
Line 104:		Line 104:

	===More Mashups Comments===		===More Mashups Comments===

			===Tommy's comments on tabs===

			* To support viewing multiple workflows from possibly different vistrails we need to improve the way we handle tabs.
			* What is a tab?
			** Each tab represents a view for a specific vistrail
			** All tabs uses the same global toolbar
			** We may need to have mode buttons for each tab to avoid confusion.
			** A tab should only contain one of the possible modes. PiP should be okay but the visual diff should open in a new window.
			** How to see which tab is currently selected?
			* Switching vistrail only does so for the main window. Detached tabs remain connected to their original vistrail.
			** The main window is responsible for switching vistrails.
			Is it useful to have stacked tabs when we can only see one of them at a time and they are all a view of the current vistrail? Maybe we should always open them in a new window.

Tommy: /* Dave's List */

2011-05-30T14:18:59Z

Dave's List

← Older revision		Revision as of 14:18, 30 May 2011
Line 37:		Line 37:

	* Diff currently being shown as a pipeline. Should we create a mode for this		* Diff currently being shown as a pipeline. Should we create a mode for this
	** [TE] What is the advantage with not having diff as a popup. It seems it worked well as a modal popup.		** [TE] What is the advantage with not having diff as a popup? It seems it worked well as a modal popup.

	* Buttons in Messages window look bad on the Mac, don't need all of them now as well, I think		* Buttons in Messages window look bad on the Mac, don't need all of them now as well, I think

Tommy: /* Dave's List */

2011-05-27T13:13:08Z

Dave's List

← Older revision		Revision as of 13:13, 27 May 2011
Line 37:		Line 37:

	* Diff currently being shown as a pipeline. Should we create a mode for this		* Diff currently being shown as a pipeline. Should we create a mode for this
			** [TE] What is the advantage with not having diff as a popup. It seems it worked well as a modal popup.

	* Buttons in Messages window look bad on the Mac, don't need all of them now as well, I think		* Buttons in Messages window look bad on the Mac, don't need all of them now as well, I think

	* Missing callbacks for Merge and Control Flow Assistant menu items		* Missing callbacks for Merge and Control Flow Assistant menu items
			** [TE] Merge can now be done by dragging a vistrail to another vistrail in the workspace window.

	* Move execute button so it doesn't look like a mode		* Move execute button so it doesn't look like a mode

Tommy: /* Juliana's notes about new interface */

2011-05-27T13:09:57Z

Juliana's notes about new interface

← Older revision		Revision as of 13:09, 27 May 2011
Line 28:		Line 28:
	* When I click on the workflow tab (in the main window,lower left corner) it always shows an "untitled.vt". This looks like a bug... And if I click on untitled.vt, nothing happens.		* When I click on the workflow tab (in the main window,lower left corner) it always shows an "untitled.vt". This looks like a bug... And if I click on untitled.vt, nothing happens.
	** [DK] Yes, Emanuele mentioned this at the meeting. I'm also not happy with the current interface.		** [DK] Yes, Emanuele mentioned this at the meeting. I'm also not happy with the current interface.
			** [TE] This has been fixed. "untitled.vt" will disappear when a vistrail is opened. It will also reappear when all vistrails are closed.

	=== Dave's List ===		=== Dave's List ===

Emanuele: /* Juliana's notes about the mashup functionality */

2011-05-27T02:16:12Z

Juliana's notes about the mashup functionality

← Older revision		Revision as of 02:16, 27 May 2011
Line 89:		Line 89:
	** [ES] In the mashup preview tab, pressing "Update" will run the pipeline with the values filled in the gui. It doesn't change anything in the mashup. I am still not sure what to do with the "save" button. I just wanted a button where the user could tell that he wants that mashup to be in the list, but for that he can just tag the mashup on inspector. What do you think?		** [ES] In the mashup preview tab, pressing "Update" will run the pipeline with the values filled in the gui. It doesn't change anything in the mashup. I am still not sure what to do with the "save" button. I just wanted a button where the user could tell that he wants that mashup to be in the list, but for that he can just tag the mashup on inspector. What do you think?
	** [JF] From the interface, it is not clear that by just changing the tag, the mashup will be saved. Maybe, when the user hits save, if a tag has not been entered (i.e., the default tag is being used), we could prompt the user to enter a tag name? Also, while editing the mashup using the inspector, it might be better to have the name of the workflow on the top, don't you think? (and the mashup tag right below).		** [JF] From the interface, it is not clear that by just changing the tag, the mashup will be saved. Maybe, when the user hits save, if a tag has not been entered (i.e., the default tag is being used), we could prompt the user to enter a tag name? Also, while editing the mashup using the inspector, it might be better to have the name of the workflow on the top, don't you think? (and the mashup tag right below).
			** [ES] I've reorganized the panels. It seems more crowded, but I think it looks more usable. I temporarily removed the "save" button while I finish the dialogs. It will be called "Keep this" and it will be enabled when the version is not tagged.
	* [JF] Should we have a special widget for entering file names?		* [JF] Should we have a special widget for entering file names?
			** [ES] You mean when the alias point to a filename? Or to any string, a user might define it as a file widget using the display widget combo box?
	* [JF] How do I view the actual mashup interface? And how to I execute the mashup on my laptop?		* [JF] How do I view the actual mashup interface? And how to I execute the mashup on my laptop?
			** [ES] When you select a version that has at least a mashup saved, you will see a Mashups (#) button below the thumbnail preview widget. Clicking on that button, will show the mashups and selecting one of them will execute it.
	* I made some changes to the "Alias Details" and then clicked on "Save" and then "Preview", nothing happened. After I clicked on these two buttons a few times, the workflow executed, but the actual mashup preview was not displayed.		* I made some changes to the "Alias Details" and then clicked on "Save" and then "Preview", nothing happened. After I clicked on these two buttons a few times, the workflow executed, but the actual mashup preview was not displayed.
	** [ES] I am working on fixing this now.		** [ES] <del>I am working on fixing this now.</del> It should be fixed in the current mashups branch and in the binary uploaded on --[[User:Emanuele\|Emanuele]] 20:16, 26 May 2011 (MDT)

	* <del>It would be nice if it were possible to center and resize the workflow to fit in the window (cmd-shift-R)</del>		* <del>It would be nice if it were possible to center and resize the workflow to fit in the window (cmd-shift-R)</del>
	** [ES] This is supported in the current mashups branch (I haven't built a new binary yet)		** [ES] This is supported in the current mashups branch. (I haven't built a new binary yet)

	===More Mashups Comments===		===More Mashups Comments===

Ctuttle: /* Claurissa's Notes V2.0 */

2011-05-26T01:09:45Z

Claurissa's Notes V2.0

← Older revision		Revision as of 01:09, 26 May 2011
Line 53:		Line 53:

	=== Claurissa's Notes V2.0===		=== Claurissa's Notes V2.0===

			* It is unclear to me how to get group and subworkflow options enabled. If I start VisTrails, open a file, and then try to group some of its modules, the options remain disabled. However, if I create a pipeline on the untitled workspace, group and subworkflow are enabled, and then I can open the other file and the options remain enabled.

	* In the Module Configuration window, I can click on the check boxes, but it makes me save after each one and doesn't update the builder window. Configuring ports to be visible works on the Module Information tab.		* In the Module Configuration window, I can click on the check boxes, but it makes me save after each one and doesn't update the builder window. Configuring ports to be visible works on the Module Information tab.

Ctuttle: /* Claurissa's Notes V2.0 */

2011-05-25T17:40:20Z

Claurissa's Notes V2.0

← Older revision		Revision as of 17:40, 25 May 2011
Line 53:		Line 53:

	=== Claurissa's Notes V2.0===		=== Claurissa's Notes V2.0===

			* In the Module Configuration window, I can click on the check boxes, but it makes me save after each one and doesn't update the builder window. Configuring ports to be visible works on the Module Information tab.

	* Parameter Exploration doesn't work. When I hit the execute button, nothing seems to happen.		* Parameter Exploration doesn't work. When I hit the execute button, nothing seems to happen.

Ctuttle: /* More Mashups Comments */

2011-05-25T03:29:55Z

More Mashups Comments

← Older revision		Revision as of 03:29, 25 May 2011
Line 96:		Line 96:

	===More Mashups Comments===		===More Mashups Comments===
	* [CT] When I open the terminator.vt example and select mashups and preview, the center panel is made really wide to fit in all four images that it want to display. The problem then becomes that I can't shrink the window back down to a normal size.

Ctuttle at 03:27, 25 May 2011

2011-05-25T03:27:34Z

← Older revision		Revision as of 03:27, 25 May 2011
Line 94:		Line 94:
	* <del>It would be nice if it were possible to center and resize the workflow to fit in the window (cmd-shift-R)</del>		* <del>It would be nice if it were possible to center and resize the workflow to fit in the window (cmd-shift-R)</del>
	** [ES] This is supported in the current mashups branch (I haven't built a new binary yet)		** [ES] This is supported in the current mashups branch (I haven't built a new binary yet)

			===More Mashups Comments===
			* [CT] When I open the terminator.vt example and select mashups and preview, the center panel is made really wide to fit in all four images that it want to display. The problem then becomes that I can't shrink the window back down to a normal size.