I'm going to trim the replies a bit so my comments are easier to find. > Am 12.09.2015 um 00:09 schrieb Martin Čech:
>> In this case the naming kinda makes sense to me (lapps_stanford_2_0_0 and >> lapps_stanford_2_1_0 that is). However could the remote Standford API >> version be a parameter of the tool instead? i.e. you would have only >> 'lapps_stanford' and select the version you want to use from a dropdown and >> the tool form would adjust (this is technically possible and used) and >> after execution called the right underlying script? Yes, this wouldn't be very difficult, but I think I prefer keeping everything as distinct as possible. That way changes to the v1.1 wrapper for the lapps_stanford_2.1.0 tools are guaranteed to have no effect on the v1.0 wrapper for the lapps_stanford_2.0.0 tools. Also, all my wrapper XML files and test data are machine generated and keeping everything separate makes that process a little easier. On Sep 12, 2015, at 4:09 AM, Björn Grüning <bjoern.gruen...@gmail.com> wrote: > +1 for putting this all in one tool. > I (as admin) should not decide which API version to use :) The user would still be able to select which API version to use simply by selecting a different tool. However, keeping in mind TS best practices I will likely go with whatever is the easiest to implement and maintain. Cheers, Keith ___________________________________________________________ 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: https://lists.galaxyproject.org/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
