taverna-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stian Soiland-Reyes <st...@apache.org>
Subject Re: Taverna Mobile Release
Date Tue, 13 Sep 2016 01:54:09 GMT
Androids and folks,

There have been quite a bit of work on the Taverna Mobile over th
esummer, thanks to all of you!

I am wondering if we are now getting closer to a release? I don't
think we need to be too ambitious - but I agree we shouldn't let too
many things "hang in the air" either.

I don't know if Apache Software Foundation has ever done a Google Play
/ .apk release - so it might be worth asking on dev@community or
general@incubator about any tips on doing such a release.  I know ASF
has a Apple store signing thing - but not sure if there's something
similar for Android.

But if that ends up being tricky - I think we can still do a first
source release of Taverna Mobile - just to get a good milestone, and
so we can make a download page etc - even just a .apk file to

We can also always do the Play upload "out of bands" as long as we are
careful with the Apache trade mark.

BTW Here's a walk-through I did with the 2013
https://github.com/myGrid/taverna-mobile (pre-Apache) prototype by
Hyde Zhang.


On 27 July 2016 at 15:39, Ian Dunlop <ianwdunlop@gmail.com> wrote:
> Hello,
> I don't think the app is quite ready for release yet. It looks like there
> is now a lot of duplicated code in it. For example, there is
> adapters/WorkflowAdpater and ui/adapter/WorkflowAdapter. I guess that the
> original one is not used any more. It would be nice if we could clean uo
> the codebase and remove the legacy bits. I think that was one of the
> original ideas behind the GSoC plan but it may have got lost somewhere.
> Another one of the ideas was to document what things do and use simple
> design patterns so that other devs could add functionality. I'm not sure we
> have quite achieved that yet.
> I think something that has been lost along the way is that the mobile app
> was to allow people to run workflows via a tav server/player. However, we
> have lost that functionality (well, it's not visible to the user anyway).
> I'm not too bothered if the favourites sync to their myExperiment account
> or not. The app was never meant to be a mobile version of myExperiment.
> Showing workflows is great. Running them even better.
> Cheers,
> Ian
> On 26 July 2016 at 15:59, Rajan Maurya <rajanmaurya154@gmail.com> wrote:
>> Hi Folks,
>> Now our main functionality are stable and ready for release.
>> As stain told earlier that you are thinking to relaese first version of
>> Taverna mobile.
>> I wanna know that Is there any date etc you throught to release the app ?
>> Sagar is working on Login Screen and Shifting code according to MVP with
>> bug fix and adding some great functionalities like logout and etc.
>> *Ian as you told about the "Favourite" funcationlity, you want this
>> funcationlity in Dashboard*.
>> Yes, It is good if we put favourite in Dashboard but when we go though the
>> REST API and found, we have API to sync user favourite to their account and
>> when ever he will change or uninstall and install the app again he will get
>> his favourite again.
>> and After implementing this feature in favourite. this feature carry many
>> REST API calls and if put this feature in Dashboard. our Dashborad will be
>> heavy. and may be produce API calls conflict.
>> So I told Sagar to make this spreate feature.
>> BTW I wanna expected date, So I will schedule everything accourdingly.
>> --
>> *Thanks*
>> *Namaste*
>> Rajan Maurya
>> Contact Number : +91 8010665248
>> Github : https://github.com/therajanmaurya
>> College : Cluster Innovation Centre, University of Delhi
>> Student : B.Tech. (Information Technology & Mathematical Innovations)

Stian Soiland-Reyes

View raw message