+1 - Agreed - nothing fancy, just one mega-scroll should do, like the
big-name apps do. :)
Added it as a new task to Jira:
https://issues.apache.org/jira/browse/TAVERNA-1012
On 21 September 2016 at 16:19, Gale Naylor wrote:
> That sounds good!
>
> On Wed, Sep
That sounds good!
On Wed, Sep 21, 2016 at 8:02 AM Rajan Maurya
wrote:
> Yes, We can show opensource licences of all the library in the menu action
> button.
>
> For an example : open google gmail app -> click navigation home button ->
> scroll to botton -> click on
Yes, We can show opensource licences of all the library in the menu action
button.
For an example : open google gmail app -> click navigation home button ->
scroll to botton -> click on Settings -> open settings action menu -> click
on Help & feedback ->
open Help & feedback action menu -> click
Hello,
I agree with Gale that we can add it to the play read more but we also need
to think about people who will just download the apk. So maybe we do need
to add some details to the "about" section within the app. It's not a big
deal to do. I guess we will discover what to do when we release.
Yes, I think that would somewhat count as "provided with" in these cloud
days :-)
(I am not a lawyer, etc)
On 20 Sep 2016 5:48 p.m., "Gale Naylor" wrote:
> Could we put the license and notice in the "read more" section of the play
> store window that is used to
Could we put the license and notice in the "read more" section of the play
store window that is used to describe the app? Or a summary of the info?
On Tue, Sep 20, 2016, 3:12 AM Stian Soiland-Reyes wrote:
> Hi,
>
> If we're going to release a Taverna Mobile binary .apk (or
Hi,
If we're going to release a Taverna Mobile binary .apk (or whatever
the extension is today) - then that would also bundle the third-party
dependencies, right?
We would then need to include a variant of the LICENSE and NOTICE file
- but how can that be readable from within the app? (As you