Peter, Thanks for getting back to me. I'm working on an existing project where my predecessors have added a tool that enables a user to add REST and SOAP Web services as usable tools within Galaxy by providing their WSDL or WADL URLs. It makes sense that the tools that are added should show up in both the "Analyze" page and the Workflow editor, but the actual tool for adding Web services is not intended to be used in workflows. I understand that this tool should probably (more appropriately) be located on the "Admin" page, but in the short run, I'd like to hide this tool from showing up in the list of tools available in the Workflow editor (admittedly, this is the opposite of my original question). In the long run, is there an API for adding plugins (or similar) to the admin page? I ask because this particular tool is not designed to be used in a workflow, but rather, it is designed to add tools to Galaxy itself. Perhaps there is a way to work this into the Toolshed stuff you guys are working on? Any thoughts are much appreciated. Thanks! Sincerely, Michael E. Cotterell Ph.D. Student in Computer Science, University of Georgia Instructor of Record, Graduate RA & TA, University of Georgia mepcotterell@gmail.com (mailto:mepcotterell@gmail.com) mepcott@uga.edu (mailto:mepcott@uga.edu) mec@cs.uga.edu (mailto:mec@cs.uga.edu) http://michaelcotterell.com/ On Wednesday, June 5, 2013 at 11:08 AM, Peter Cock wrote:
On Monday, June 3, 2013 at 10:17 AM, Michael E. Cotterell wrote:
Suppose a tool didn't have any kind of configuration and therefore didn't need to be displayed in the "Analyze Data" part of Galaxy. Is there a way to modify tool_conf.xml so that a particular tool is only displayed in the Workflow editor?
Thanks!
Sincerely, Michael E. Cotterell
On Wed, Jun 5, 2013 at 4:02 PM, Michael E. Cotterell <mepcotterell@gmail.com (mailto:mepcotterell@gmail.com)> wrote:
Any ideas?
Thanks!
The only way this makes sense to me if is you have a tool with no inputs at all (not even an input data file), but it produces one or more output files. e.g. "Fetch the human genome as FASTA file, version hg18". But in that case you'd be better off just defining the file within a shared data library.
Perhaps you could give an example of the kind of tool you are interested in?
Thanks,
Peter