Dear Galaxy Dev-Team,
when using the select parameter in conjunction with options loaded from a text file in the tool_data_path directory (e.g., <options from_file=available_options.txt>) and with the "multiple" attribute set to true, I found that the form of the corresponding HTML widget displayed in the webinterface depends on the number of options listed in the text file. Is there a way to avoid this behaviour in the sense that a fixed HTML form is used independent of the number of available options? It would be great if this was possible, for instance, by changing the value of the display attribute of the select parameter. However, I would also be glad if you could just tell me, where this behaviour of Galaxy is implemented in the source code, such that I can change it according to my needs.
Kind regards, Johannes
I have attached a patch to disable this. The swap over happens when the number of items gets sufficiently large and a jQuery-based widget called select2 replaces all select boxes in Galaxy - unless explicitly disabled. I understand the desire to disable this. I am not sure anyone is really very pleased with select2 for multiple select widgets - it might be worth just disabling it for multiple select form elements all together globally. I don't know.
-John
On Thu, Jan 23, 2014 at 4:23 AM, Johannes Eichner johannes.eichner@uni-tuebingen.de wrote:
Dear Galaxy Dev-Team,
when using the select parameter in conjunction with options loaded from a text file in the tool_data_path directory (e.g., <options from_file=available_options.txt>) and with the "multiple" attribute set to true, I found that the form of the corresponding HTML widget displayed in the webinterface depends on the number of options listed in the text file. Is there a way to avoid this behaviour in the sense that a fixed HTML form is used independent of the number of available options? It would be great if this was possible, for instance, by changing the value of the display attribute of the select parameter. However, I would also be glad if you could just tell me, where this behaviour of Galaxy is implemented in the source code, such that I can change it according to my needs.
Kind regards, Johannes
-- Dipl.-Inf. (Bioinf.) Johannes Eichner Univ. Tuebingen, WSI-RA, Sand 1, D-72076 Tuebingen, Germany Phone: (+49/0) 7071 / 29 78970 Fax: (+49/0) 7071 / 29 5091
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/
On Jan 27, 2014, at 9:57 AM, John Chilton chilton@msi.umn.edu wrote:
The swap over happens when the number of items gets sufficiently large and a jQuery-based widget called select2 replaces all select boxes in Galaxy - unless explicitly disabled. I understand the desire to disable this. I am not sure anyone is really very pleased with select2 for multiple select widgets
- it might be worth just disabling it for multiple select form
elements all together globally. I don't know.
The function 'replace_big_select_inputs' in galaxy.base.js is where the logic for this code is located. You could avoid applying select2 to selects with multiple using the following CSS selector on line 261 in place of $('select'):
$('select').not('[multiple]')
Best, J.
galaxy-dev@lists.galaxyproject.org
-
Jeremy Goecks -
Johannes Eichner -
John Chilton