Tool wrappers - Triggering warnings on specific options?
Hello all, I was wondering if anyone else writing Galaxy tools has wanted to be able to show warning messages conditional on tool options? For example, setting a parameter to a deprecated value could trigger a warning message (with an OK/Cancel dialogue to allow continuation or returning to the tool options). More generally, a warning might be desirable only if certain options are used together. Even stricter, for some tools it would be useful to show an error message with particular option combinations, and refuse to submit the job. Any thoughts? Peter
Peter, I quite like this idea, and I think it might be possible to do as a simple extension to the validator framework. Basically, a flag indicating that failing a certain validation would be able to be considered a warning rather than an error. Or, allow a validator to return a sentinel indicating warning vs error. -- James Taylor, Assistant Professor, Biology/CS, Emory University On Wed, Feb 20, 2013 at 11:08 AM, Peter Cock <p.j.a.cock@googlemail.com>wrote:
Hello all,
I was wondering if anyone else writing Galaxy tools has wanted to be able to show warning messages conditional on tool options?
For example, setting a parameter to a deprecated value could trigger a warning message (with an OK/Cancel dialogue to allow continuation or returning to the tool options). More generally, a warning might be desirable only if certain options are used together.
Even stricter, for some tools it would be useful to show an error message with particular option combinations, and refuse to submit the job.
Any thoughts?
Peter ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:
On Wed, Feb 20, 2013 at 11:13 PM, James Taylor <james@jamestaylor.org> wrote:
Peter, I quite like this idea, and I think it might be possible to do as a simple extension to the validator framework. Basically, a flag indicating that failing a certain validation would be able to be considered a warning rather than an error. Or, allow a validator to return a sentinel indicating warning vs error.
The current validator framework works at a single parameter level (right?), but yes, generalising that somehow would probably work. I agree that warning vs error as a severity flag makes perfect sense. Regards, Peter
participants (2)
-
James Taylor
-
Peter Cock