taverna-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ian Dunlop (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAVERNA-838) Integrating the Taverna Player API and server REST API into the App
Date Thu, 18 Jun 2015 13:52:01 GMT

    [ https://issues.apache.org/jira/browse/TAVERNA-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14591814#comment-14591814

Ian Dunlop commented on TAVERNA-838:

I think it makes sense for workflows to come from myexperiment or be user uploaded to their
device. The player should only really be to run a workflow. The fact that workflows are present
on a player instance is just a convenience.

> Integrating the Taverna Player API and server REST API into the App
> -------------------------------------------------------------------
>                 Key: TAVERNA-838
>                 URL: https://issues.apache.org/jira/browse/TAVERNA-838
>             Project: Apache Taverna
>          Issue Type: Task
>          Components: GSOC: Taverna Mobile
>    Affects Versions: parent 1
>         Environment: Android Studio version 1.1.0, backtrack Linux distros
>            Reporter: larry akah
>            Assignee: larry akah
>              Labels: newbie
>             Fix For: parent 1
>   Original Estimate: 336h
>  Remaining Estimate: 336h
> Adding support for creating workflow runs through Taverna Player. Viewing and organizing
workflows on the user's device. Generally, we are leveraging the Taverna Player API to manage
runs and workflows.

This message was sent by Atlassian JIRA

View raw message