Folks,
After checking a little closer last night, I have one clarification.
The Tool Shed does use POSTs as well as GETs, but even when it's
POSTing, the encoded dictionaries (encoded_repo_info_dicts) are part
of the query string. The encoded_repo_info_dicts should probably
become part of the
You're not missing anything; using validators is the right way for checking
parameter values. However, the page refreshes + validation errors is certainly
less than ideal for usability. We're in the process of transitioning tool forms
to a JavaScript-based framework so that full page refreshes
Take a look at the histories controller (histories.py) for an example +
documentation on how Galaxy realizes a RESTful interface. In short, you'll want
to implement different methods for create, read, update, and delete. Kwds are
miscellaneous parameters included in a request that are not
Sweet!
Thanks
Ted
On Sep 14, 2013, at 11:04 AM, Jeremy Goecks jeremy.goe...@emory.edu wrote:
Take a look at the histories controller (histories.py) for an example +
documentation on how Galaxy realizes a RESTful interface. In short, you'll
want to implement different methods for create,
