I would say it is a ways off yet, it doesn't even validate all proper
XML yet, let alone have proper documentation tags. I was hoping adding
the validation feature to planemo would spur some development on it,
but it hasn't happened yet. Some people are trying it out though
). Maybe the next
mini hackathon/contribution event we organize should be on fixing that
up. It is a really pretty easy way to contribute Galaxy IMO.
On Wed, Sep 9, 2015 at 9:13 PM, Peter Cock <p.j.a.cock(a)googlemail.com> wrote:
I like that plan - is the XSD at the point where we can declare
it in Galaxy Tool definition XML files s & validate them (via
planemo or otherwise)?
On Wed, Sep 9, 2015 at 7:03 PM, John Chilton <jmchilton(a)gmail.com> wrote:
> Updated the wiki with this information.
> We got to get away from using the wiki page and start documenting this
> stuff in the XSD (https://github.com/JeanFred/Galaxy-XSD
) directly and
> build the documentation from that. Maybe Eric or Björn will find a
> couple free hours some day to get that wiki information ported over
> Thanks for the catch Peter,
> On Tue, Sep 1, 2015 at 11:43 AM, Peter Cock <p.j.a.cock(a)googlemail.com> wrote:
>> Hello all,
>> I've just noticed that dollar signs for accessing environment
>> variables must be escaped in the XML <command> tag,
>> but must not be escaped in the <version_command> tag:
>> I presume this is because <command> is parsed as a
>> Cheetah template where dollar means a Python variable
>> (like the input and output parameters), while for the
>> <version_command> this does not happen?
>> Has anyone else been caught out by this? Is it worth adding
>> a note about this to the wiki?
>> 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: