Hi Alex, I think I qualify as a reasonably active taverna user these days, so here are my votes.
1) Yes (non-modal) 2) Yes (run dialog persists) 3) Separate run dialog per workflow cheers, James On 19 Mar 2010, at 18:36, Alexandra Nenadic wrote: > Hi taverna-users, > > We'd like your opinion on the Run Dialog in Taverna (the one you get > when you try to run the Workflow and you need to specify your workflow > inputs). We are doing some changes to it and want to get it right, i.e. > do what most of you want. > > Currently, you get a dialog that is modal (i.e. stays on top of the main > Taverna window) and does not let you bring the main Taverna window at > the same time. Also, when you click the Run button on the dialog - it > closes it and switches to the Result perspective where you see the > progress of the workflow run. You can bring it up again if you click on > the Run button again in the main menu or in the toolbar and it will show > the dialog with the last used input values. > > So the questions are: > > (1) Do you want the run dialog to be non-modal so you can bring the main > Taverna window into focus? > > (2) Do you want the Run Dialog not to close after pressing the Run > button and to simply get minimised in the case it is non-modal? If it > gets closed then you can bring it up again from the File/Run menu of the > top toolbar. If it gets minimised you can always just click on it to > bring it up again. > > (3) Do you want a separate Run Dialog per workflow or only one RunDialog > for the currently run workflow? In the first case if you tried running 2 > different workflows you'd have two different Run Dialogs minimised that > you can bring up. If you ran the same workflow e.g. 10 times, there > would still be one Run Dialog for that workflow though. So one Run > Dialog per workflow, but multiple runs of the same workflow would get > the same Run Dialog with the last input values saved. In the second > case, the Run Dialog will only refer to the workflow currently being run > and you would not be able to see the input values you used when you ran > other workflows. > > The suggestion we got from our in-house users is to use non-modal Run > Dialogs, one per workflow, and not to close them but minimise them after > having finished with entering inputs. This is similar to Taverna 1, but > you do not get a different dialog for different runs of the same > workflow, rather you just have one dialog per workflow that remembers > last used values. > > > OK, cast your votes. > > Cheers, > Alex > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > taverna-users mailing list > [email protected] > [email protected] > Web site: http://www.taverna.org.uk > Mailing lists: http://www.taverna.org.uk/taverna-mailing-lists/ ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ taverna-users mailing list [email protected] [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/taverna-mailing-lists/
