Repeats shown upside down on galaxy-central
Hi all, I'm running galaxy-central as my development server, and noticed what to me is a regression with repeat parameters, e.g. https://github.com/peterjc/pico_galaxy/blob/master/tools/clc_assembly_cell/c... Read group: [+ insert read group] * 1: Read Group * 2: Read Group which on clicking becomes: Read group: [+ insert read group] * 2: Read Group * 1: Read Group This to me is upside down, the current behaviour on galaxy-dist is more natural (and also pluralises the group heading): Read Groups * Read Group 1 [Add new Read Group] which on clicking becomes: Read Groups * Read Group 1 * Read Group 2 [Add new Read Group] Is this a deliberate change? If so, why? Peter
Hi Peter, Yes we changed this on purpose, however it is open to discussion. The advantage is that the user does not have to scroll down after adding a new repeat block. Additionally it enables users to easily add more than one repeat block quickly, since the insert button does not relocate on the screen after adding new repeat blocks. Thanks, Sam On Mon, Nov 3, 2014 at 7:25 AM, Peter Cock <p.j.a.cock@googlemail.com> wrote:
Hi all,
I'm running galaxy-central as my development server, and noticed what to me is a regression with repeat parameters,
e.g. https://github.com/peterjc/pico_galaxy/blob/master/tools/clc_assembly_cell/c...
Read group: [+ insert read group] * 1: Read Group * 2: Read Group
which on clicking becomes:
Read group: [+ insert read group] * 2: Read Group * 1: Read Group
This to me is upside down, the current behaviour on galaxy-dist is more natural (and also pluralises the group heading):
Read Groups * Read Group 1 [Add new Read Group]
which on clicking becomes:
Read Groups * Read Group 1 * Read Group 2 [Add new Read Group]
Is this a deliberate change? If so, why?
Peter ___________________________________________________________ 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/
Hi Sam, I found the old approach (new repeat blocks at bottom) worked fine when adding blocks one by one and completing them as I went (which means once you have filled in the new block, you have scrolled down to the button ready to add another block if needed). If find the new approach (new blocks inserted at top) visually confusing as I am used to filling in forms from top to bottom. I do concede the approach makes it easy to add several repeats with a few clicks, and then fill them in - but personally that isn't a common thing for me to do, and I do not think this change is worth the confusion. There are a number of other visual changes on galaxy-central compared to the current release, so of which seem harmless like the boolean parameters becoming a yes/no toggle in place of a tick box, others are more daunting/scary (e.g. collection related changes to the file picker for automatic batch jobs). Is there any draft documentation on these changes being prepared to go into the next release notes? This is the sort of thing local Galaxy Admins would appreciate to anticipate local user queries. Thanks, Peter On Thu, Nov 6, 2014 at 12:45 PM, Aysam Guerler <aysam.guerler@gmail.com> wrote:
Hi Peter,
Yes we changed this on purpose, however it is open to discussion. The advantage is that the user does not have to scroll down after adding a new repeat block. Additionally it enables users to easily add more than one repeat block quickly, since the insert button does not relocate on the screen after adding new repeat blocks.
Thanks, Sam
On Mon, Nov 3, 2014 at 7:25 AM, Peter Cock <p.j.a.cock@googlemail.com> wrote:
Hi all,
I'm running galaxy-central as my development server, and noticed what to me is a regression with repeat parameters,
e.g. https://github.com/peterjc/pico_galaxy/blob/master/tools/clc_assembly_cell/c...
Read group: [+ insert read group] * 1: Read Group * 2: Read Group
which on clicking becomes:
Read group: [+ insert read group] * 2: Read Group * 1: Read Group
This to me is upside down, the current behaviour on galaxy-dist is more natural (and also pluralises the group heading):
Read Groups * Read Group 1 [Add new Read Group]
which on clicking becomes:
Read Groups * Read Group 1 * Read Group 2 [Add new Read Group]
Is this a deliberate change? If so, why?
Peter
Alright, I think you are right. The possible confusion is not worth the benefits. I have switched the ordering back to the classic sorting. I will now look into the dataset selector and see how to revise it. Thanks for pointing these things out. Thanks, Sam On Thu, Nov 6, 2014 at 8:18 AM, Peter Cock <p.j.a.cock@googlemail.com> wrote:
Hi Sam,
I found the old approach (new repeat blocks at bottom) worked fine when adding blocks one by one and completing them as I went (which means once you have filled in the new block, you have scrolled down to the button ready to add another block if needed).
If find the new approach (new blocks inserted at top) visually confusing as I am used to filling in forms from top to bottom.
I do concede the approach makes it easy to add several repeats with a few clicks, and then fill them in - but personally that isn't a common thing for me to do, and I do not think this change is worth the confusion.
There are a number of other visual changes on galaxy-central compared to the current release, so of which seem harmless like the boolean parameters becoming a yes/no toggle in place of a tick box, others are more daunting/scary (e.g. collection related changes to the file picker for automatic batch jobs).
Is there any draft documentation on these changes being prepared to go into the next release notes? This is the sort of thing local Galaxy Admins would appreciate to anticipate local user queries.
Thanks,
Peter
On Thu, Nov 6, 2014 at 12:45 PM, Aysam Guerler <aysam.guerler@gmail.com> wrote:
Hi Peter,
Yes we changed this on purpose, however it is open to discussion. The advantage is that the user does not have to scroll down after adding a new repeat block. Additionally it enables users to easily add more than one repeat block quickly, since the insert button does not relocate on the screen after adding new repeat blocks.
Thanks, Sam
On Mon, Nov 3, 2014 at 7:25 AM, Peter Cock <p.j.a.cock@googlemail.com> wrote:
Hi all,
I'm running galaxy-central as my development server, and noticed what to me is a regression with repeat parameters,
e.g.
https://github.com/peterjc/pico_galaxy/blob/master/tools/clc_assembly_cell/c...
Read group: [+ insert read group] * 1: Read Group * 2: Read Group
which on clicking becomes:
Read group: [+ insert read group] * 2: Read Group * 1: Read Group
This to me is upside down, the current behaviour on galaxy-dist is more natural (and also pluralises the group heading):
Read Groups * Read Group 1 [Add new Read Group]
which on clicking becomes:
Read Groups * Read Group 1 * Read Group 2 [Add new Read Group]
Is this a deliberate change? If so, why?
Peter
Great :) My other niggle is with the new appearance of select parameters. In general, the drop down controls for select parameters are "just wide enough" for their longest entry. Sometimes under the unreleased code from galaxy-central they seem to span the full width of the frame. e.g. Using v0.0.4 of my mummer dotplot tool (latest version not yet on the main ToolShed pending a dependency pacakge), https://github.com/peterjc/pico_galaxy/tree/master/tools/mummer https://testtoolshed.g2.bx.psu.edu/view/peterjc/mummer On the current stable release: [image: Inline image 2] While on galaxy-central, notice how the algorithm selector is now taking up the full available width: [image: Inline image 3] This may be linked to the batch input mode bit? Peter On Thu, Nov 6, 2014 at 2:02 PM, Aysam Guerler <aysam.guerler@gmail.com> wrote:
Alright, I think you are right. The possible confusion is not worth the benefits. I have switched the ordering back to the classic sorting. I will now look into the dataset selector and see how to revise it. Thanks for pointing these things out.
Thanks, Sam
On Thu, Nov 6, 2014 at 8:18 AM, Peter Cock <p.j.a.cock@googlemail.com> wrote:
Hi Sam,
I found the old approach (new repeat blocks at bottom) worked fine when adding blocks one by one and completing them as I went (which means once you have filled in the new block, you have scrolled down to the button ready to add another block if needed).
If find the new approach (new blocks inserted at top) visually confusing as I am used to filling in forms from top to bottom.
I do concede the approach makes it easy to add several repeats with a few clicks, and then fill them in - but personally that isn't a common thing for me to do, and I do not think this change is worth the confusion.
There are a number of other visual changes on galaxy-central compared to the current release, so of which seem harmless like the boolean parameters becoming a yes/no toggle in place of a tick box, others are more daunting/scary (e.g. collection related changes to the file picker for automatic batch jobs).
Is there any draft documentation on these changes being prepared to go into the next release notes? This is the sort of thing local Galaxy Admins would appreciate to anticipate local user queries.
Thanks,
Peter
On Thu, Nov 6, 2014 at 12:45 PM, Aysam Guerler <aysam.guerler@gmail.com> wrote:
Hi Peter,
Yes we changed this on purpose, however it is open to discussion. The advantage is that the user does not have to scroll down after adding a new repeat block. Additionally it enables users to easily add more than one repeat block quickly, since the insert button does not relocate on the screen after adding new repeat blocks.
Thanks, Sam
On Mon, Nov 3, 2014 at 7:25 AM, Peter Cock <p.j.a.cock@googlemail.com> wrote:
Hi all,
I'm running galaxy-central as my development server, and noticed what to me is a regression with repeat parameters,
e.g.
https://github.com/peterjc/pico_galaxy/blob/master/tools/clc_assembly_cell/c...
Read group: [+ insert read group] * 1: Read Group * 2: Read Group
which on clicking becomes:
Read group: [+ insert read group] * 2: Read Group * 1: Read Group
This to me is upside down, the current behaviour on galaxy-dist is more natural (and also pluralises the group heading):
Read Groups * Read Group 1 [Add new Read Group]
which on clicking becomes:
Read Groups * Read Group 1 * Read Group 2 [Add new Read Group]
Is this a deliberate change? If so, why?
Peter
Hey Peter, I have modified the data selectors appearance by adding a single select field as default option. It resembles the previous functionality now and I think its an improvement. Regarding the length of the select box I think that the tool form overall looks more organized now since almost all the input elements have the same length. However I will discuss this with the others and see what the consensus is. Thanks again, Sam On Thu, Nov 6, 2014 at 9:30 AM, Peter Cock <p.j.a.cock@googlemail.com> wrote:
Great :)
My other niggle is with the new appearance of select parameters. In general, the drop down controls for select parameters are "just wide enough" for their longest entry. Sometimes under the unreleased code from galaxy-central they seem to span the full width of the frame.
e.g. Using v0.0.4 of my mummer dotplot tool (latest version not yet on the main ToolShed pending a dependency pacakge),
https://github.com/peterjc/pico_galaxy/tree/master/tools/mummer https://testtoolshed.g2.bx.psu.edu/view/peterjc/mummer
On the current stable release:
[image: Inline image 2]
While on galaxy-central, notice how the algorithm selector is now taking up the full available width:
[image: Inline image 3]
This may be linked to the batch input mode bit?
Peter
On Thu, Nov 6, 2014 at 2:02 PM, Aysam Guerler <aysam.guerler@gmail.com> wrote:
Alright, I think you are right. The possible confusion is not worth the benefits. I have switched the ordering back to the classic sorting. I will now look into the dataset selector and see how to revise it. Thanks for pointing these things out.
Thanks, Sam
On Thu, Nov 6, 2014 at 8:18 AM, Peter Cock <p.j.a.cock@googlemail.com> wrote:
Hi Sam,
I found the old approach (new repeat blocks at bottom) worked fine when adding blocks one by one and completing them as I went (which means once you have filled in the new block, you have scrolled down to the button ready to add another block if needed).
If find the new approach (new blocks inserted at top) visually confusing as I am used to filling in forms from top to bottom.
I do concede the approach makes it easy to add several repeats with a few clicks, and then fill them in - but personally that isn't a common thing for me to do, and I do not think this change is worth the confusion.
There are a number of other visual changes on galaxy-central compared to the current release, so of which seem harmless like the boolean parameters becoming a yes/no toggle in place of a tick box, others are more daunting/scary (e.g. collection related changes to the file picker for automatic batch jobs).
Is there any draft documentation on these changes being prepared to go into the next release notes? This is the sort of thing local Galaxy Admins would appreciate to anticipate local user queries.
Thanks,
Peter
On Thu, Nov 6, 2014 at 12:45 PM, Aysam Guerler <aysam.guerler@gmail.com
wrote:
Hi Peter,
Yes we changed this on purpose, however it is open to discussion. The advantage is that the user does not have to scroll down after adding a new repeat block. Additionally it enables users to easily add more than one repeat block quickly, since the insert button does not relocate on the screen after adding new repeat blocks.
Thanks, Sam
On Mon, Nov 3, 2014 at 7:25 AM, Peter Cock <p.j.a.cock@googlemail.com
wrote:
Hi all,
I'm running galaxy-central as my development server, and noticed what to me is a regression with repeat parameters,
e.g.
https://github.com/peterjc/pico_galaxy/blob/master/tools/clc_assembly_cell/c...
Read group: [+ insert read group] * 1: Read Group * 2: Read Group
which on clicking becomes:
Read group: [+ insert read group] * 2: Read Group * 1: Read Group
This to me is upside down, the current behaviour on galaxy-dist is more natural (and also pluralises the group heading):
Read Groups * Read Group 1 [Add new Read Group]
which on clicking becomes:
Read Groups * Read Group 1 * Read Group 2 [Add new Read Group]
Is this a deliberate change? If so, why?
Peter
Hi Sam, On Thu, Nov 13, 2014 at 6:25 AM, Aysam Guerler <aysam.guerler@gmail.com> wrote:
Hey Peter,
I have modified the data selectors appearance by adding a single select field as default option. It resembles the previous functionality now and I think its an improvement.
Great. I won't be able to try this until next week at the earliest though. Regarding the length of the select box I think that the tool form overall
looks more organized now since almost all the input elements have the same length. However I will discuss this with the others and see what the consensus is.
Perhaps a confounding variable is how wide your screen is? In my screenshots the visual cue that this is a select box is on the extreme right and thus separated from the text it is connected to. I think that makes it a bad GUI design choice (as well somehow not liking the visual aesthetic, which is a more personal impression). Thanks, Peter
I see your point maybe a maximum width will fix the issue for wide screens. I look into it. Thanks, Sam On Wed, Nov 12, 2014 at 7:42 PM, Peter Cock <p.j.a.cock@googlemail.com> wrote:
Hi Sam,
On Thu, Nov 13, 2014 at 6:25 AM, Aysam Guerler <aysam.guerler@gmail.com> wrote:
Hey Peter,
I have modified the data selectors appearance by adding a single select field as default option. It resembles the previous functionality now and I think its an improvement.
Great. I won't be able to try this until next week at the earliest though.
Regarding the length of the select box I think that the tool form overall
looks more organized now since almost all the input elements have the same length. However I will discuss this with the others and see what the consensus is.
Perhaps a confounding variable is how wide your screen is? In my screenshots the visual cue that this is a select box is on the extreme right and thus separated from the text it is connected to. I think that makes it a bad GUI design choice (as well somehow not liking the visual aesthetic, which is a more personal impression).
Thanks,
Peter
participants (2)
-
Aysam Guerler -
Peter Cock