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 renders using
the primary tool form found here:
This extends the form code found here:
And individual element types (a select box, for example) can be found here:
Does this help?
On Fri, Jul 22, 2016 at 7:40 AM Peter Cock <p.j.a.cock(a)googlemail.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.
Hopefully one of the Galaxy developers will be able to answer.
On Fri, Jul 22, 2016 at 7:29 AM, Katherine Beaulieu 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 parameter, but I
> haven't quite been able to implement that. The two files I have changed
> far are basic.py and form_builder.py but using these two files it still
> loads a text parameter.
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:
To search Galaxy mailing lists use the unified search at: