Yes this does help thanks Dannon!:)
On Fri, Jul 22, 2016 at 8:08 AM, Dannon Baker
wrote:
> Hi Katherine,
>
> This all happens in javascript these days, and it's unfortunately a little
> harder to track down all the moving parts than it used to be when this was
> all rendered serverside. The cli
Hi Katherine,
This all happens in javascript these days, and it's unfortunately a little
harder to track down all the moving parts than it used to be when this was
all rendered serverside. The client requests tool information (like which
parameters are necessary, etc) from the API, which it then
No I have not sorry.
On Fri, Jul 22, 2016 at 7:43 AM, Mohamed Kassam wrote:
> Hello Katherine,
> it is Mohamed from the NIHS.
> So have you find a way to incluse the password tahg in the xml file ?
>
> Mohamed
>
> 2016-07-22 13:34 GMT+02:00 Katherine Beaulieu <
> katherine.beaulieu...@gmail.com>
Sorry, I know relatively little about how Galaxy loads the tool XML
files and turns this into the HTML pages. I've mostly searched
the codebase with grep at the command line (also searching
directly on GitHub works pretty well) trying to trace functionality
when I was debugging something.
Hopefull
On Fri, Jul 22, 2016 at 7:29 AM, Katherine Beaulieu <
katherine.beaulieu...@gmail.com> wrote:
> No I'm really asking about which files in Galaxy, will load those
> parameters on the screen. I believe you were the one to give me a link to
> adding a new parameter type in Galaxy via the password par
Hi Katherine,
Are you asking about the XML files which described Galaxy Tools
by listing all the options to show the user, any help text to show the
user, and instructions for how to turn the options picked into a
command line to be executed:
https://wiki.galaxyproject.org/Admin/Tools/ToolConfigS
