Re: [galaxy-dev] [API] About workflow parameters :)
Hi Jen, Hum.. what is a bitbucket ticket? How do you get there? There's no real hurry anyway, as far as I'm concerned. I made API-versions of the tools I need where the python wrapper gets the needed parameters from a database. But yeah, I'm still very interested in how the API evolves. By the way, is there (or will there be) a way to share and delete histories through the API? Thanks, L-A Le 09/08/2011 02:58, Jennifer Jackson a écrit : Hi L-A, Should we make a bitbucket ticket to keep track of this enhancement request? If you would like to make one, that would be great since you could put in all the details, or just write back and I can create a simple ticket. Thanks! Jen Galaxy team On 8/5/11 6:59 AM, Louise-Amélie Schmitt wrote: Hello, Just a quick message to ask if you had the time to work on passing parameters to workflows through the API. Just to know, since I'm using workflows with the API. Best, L-A ___ 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/ ___ 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/
Re: [galaxy-dev] [API] About workflow parameters :)
Hello L-A, On 8/9/11 12:06 AM, Louise-Amélie Schmitt wrote: Hi Jen, Hum.. what is a bitbucket ticket? How do you get there? http://bitbucket.org/galaxy/galaxy-central/src Tickets are created the same place that the galaxy-central source repository is located. Click on the Issues tag to see the list of requests for enhancements, etc. It is strongly recommended to get feedback about a request on the galaxy-dev list first before opening a bitbucket ticket, to organize with the development team here. Your idea seemed like something that would be interesting to consider for the primary build, so to keep track of it, a ticket would allow both you and our team to track status/feedback (better than email, once a specific task is defined). Example: submitted patches should get a ticket, followed by an email to galaxy-dev with the bitbucket ticket's link and a description of what is being offered. And for others that may be reading this: bitbucket is not the place to report bugs. It is also not the correct place to ask a question. Please use the mailing lists: - galaxy-u...@bx.psu.edu scientific, data, and tool use discussion - galaxy-...@bx.psu.edu technical problems, local install, cloud, tool/core development - if using the public server, submit an error dataset by clicking on the green bug icon to reach an internal bug list (data would be private) There's no real hurry anyway, as far as I'm concerned. I made API-versions of the tools I need where the python wrapper gets the needed parameters from a database. But yeah, I'm still very interested in how the API evolves. By the way, is there (or will there be) a way to share and delete histories through the API? We will have to ask Dannon about that, I'll put him on the cc. Thanks!! Jen Galaxy team Thanks, L-A Le 09/08/2011 02:58, Jennifer Jackson a écrit : Hi L-A, Should we make a bitbucket ticket to keep track of this enhancement request? If you would like to make one, that would be great since you could put in all the details, or just write back and I can create a simple ticket. Thanks! Jen Galaxy team On 8/5/11 6:59 AM, Louise-Amélie Schmitt wrote: Hello, Just a quick message to ask if you had the time to work on passing parameters to workflows through the API. Just to know, since I'm using workflows with the API. Best, L-A ___ 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/ -- Jennifer Jackson http://usegalaxy.org http://galaxyproject.org/Support ___ 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/
Re: [galaxy-dev] [API] About workflow parameters :)
Hi L-A, Should we make a bitbucket ticket to keep track of this enhancement request? If you would like to make one, that would be great since you could put in all the details, or just write back and I can create a simple ticket. Thanks! Jen Galaxy team On 8/5/11 6:59 AM, Louise-Amélie Schmitt wrote: Hello, Just a quick message to ask if you had the time to work on passing parameters to workflows through the API. Just to know, since I'm using workflows with the API. Best, L-A ___ 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/ -- Jennifer Jackson http://usegalaxy.org http://galaxyproject.org/Support ___ 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/
[galaxy-dev] [API] About workflow parameters :)
Hello, Just a quick message to ask if you had the time to work on passing parameters to workflows through the API. Just to know, since I'm using workflows with the API. Best, L-A ___ 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/
