I've got a nice html report of blast results by query, and tabular subject result listing a handful of columns. It was set up so that checkboxes by each row and a submit button for each subject sent form data to another tool we have. I'd tricked the other tool's form into thinking it had all the right input for a refresh, including the tool_state string, borrowed from a previous view of that tool. It worked great - it automatically submitted and generated a resulting dataset when the html report/form submitted to it - UNTIL ALAS it seems a change in history or session caused the tool form's tool_state string to fail and trigger an error on load (I guess it encodes some stuff that references the history panel?). Looking at http://dev.list.galaxyproject.org/Feature-suggestion-quot-Re-Run-quot-button-td4132627.html it seemed like there might be a chance to encode a dummy tool_state?
So, its a long shot, but is there a bare-bones tool_state code that doesn't care what's in the history for any given galaxy tool?
Since this code is entirely in the html report rendering tool itself python doesn't seem to have access to galaxy system code.
P.s. this is what the form html template looks like (borrowed mostly from the tool's html form itself):
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: