Hi Damion, Text fields are not currently able to be populated by dynamic_options, but in a dynamic_options select list you could access the user’s username directly. If you want the user to be able to override it, you could have a conditionally used empty text box that your tool defaults to using when it is populated.
An example that you might want to look at could be the GenomeSpace Export tool (tools/genomespace/genomespace_exporter.*), which queries the GenomeSpace API to get a list of available folders for export for a specific user using attributes of the current user’s preferences (GenomeSpace username and token). It generates a drill_down type select parameter, but the same can be done for a standard select list. Thanks for using Galaxy, Dan On Oct 9, 2014, at 8:37 PM, Dooley, Damion <damion.doo...@bccdc.ca> wrote: > This was asked a few years ago but no takers: Galaxy Tool Development: > (http://dev.list.galaxyproject.org/Reading-user-id-before-the-execution-of-the-tool-td4490324.html) > > Seems like this isn't possible, unless there's a way to plant user's name in > a text field on the tool's form, so that a dynamic_options() call can refer > to it? > > Thx for insights, > > Damion > ___________________________________________________________ > 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: > http://lists.bx.psu.edu/ > > To search Galaxy mailing lists use the unified search at: > http://galaxyproject.org/search/mailinglists/ ___________________________________________________________ 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: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
