On Tue, Aug 28, 2012 at 2:30 PM, Greg Von Kuster <g...@bx.psu.edu> wrote:
> HI Peter,
>
> On Aug 23, 2012, at 9:52 AM, Peter Cock wrote:
>
>> Hi Greg,
>>
>> Could you include <repository name>.txt on the list of README
>> filenames looked for by the ToolShed as you said please?
>>
>> I've just checked and it isn't working at the moment. e.g. blast2go,
>> seq_rename, clinod, venn_list, ... - in fact most of my tools :(
>>
>> Thanks,
>>
>> Peter
>
> I've checked each of your listed repositories and the information
> in each of your <repository name>.txt files is in fact displayed
> when installing into a local Galaxy instance.

That's good - so the wiki needs updating:
http://wiki.g2.bx.psu.edu/Tool%20Shed

> This works only if
> using the tool shed installation process, so for example, if
> installing the venn_list repository, clicking "Install to local Galaxy"
> in this screenshot:

Ah. I see now it just isn't doing what I expected - apologies for
any misdirection.

I had assumed if a README file was present, it would be shown
prominent while browsing on the ToolShed. On closer examination
of an example repository where there is a file named exactly
'README' (e.g. fubar's clustalw tool) that isn't shown either.

Is there any reason not to show the contents of the README file
(using the discussed name variations) on the main ToolShed
repository view, e.g. under a new yellow section header?

Thanks,

Peter

P.S. It would be nice to automatically line wrap the "Detailed
description", as in many cases the raw text doesn't do this.
For example, fubar's clustalw tool.
___________________________________________________________
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/

Reply via email to