[Sugar-devel] [HELP] Writing activity that requires api key

[Naman Nimmo]

Thanks a lot @quozl
I'll let you know when I'm ready to release it.

On Thu, Dec 19, 2019 at 1:55 AM James Cameron <quozl at laptop.org> wrote:

> Once upon a time this made it difficult.  It was discouraged.  It
> looked very different.  It behaved different.  It cost extra resources
> on a tiny laptop to ensure each different graphics API was present in
> memory and on disk.  So we decided on GTK only, because that's what
> Sugar home view uses.
>
> However, computers are larger, and a tkinter module is part of Python,
> so if you have working code using tkinter inside the sugar3 wrapper,
> with a toolbar and stop button that works, then I would accept it on
> the basis that;
>
> - people who want to use the activity in a school will make sure
>   tkinter is also installed,
>
> - somebody may later port to GTK.
>
> Please mention tkinter as a dependency in the README.md file (see
> README.md in the Record activity as an example), and maybe add
> requirements.txt as used by PyPi if you have any additional modules
> needed.
>
> On Thu, Dec 19, 2019 at 01:35:58AM +0530, Naman Nimmo wrote:
> > Will do, thanks!
> > Just on a side note-- the activity uses tkinter package. Is that
> allowed?
> >
> > On Thu, Dec 19, 2019, 01:21 James Cameron <[1]quozl at laptop.org wrote:
> >
> >     No worries.  Let us know what you decide to do.
> >
> >     On Wed, Dec 18, 2019 at 09:28:53PM +0530, Naman Nimmo wrote:
> >     > Thank you for the clarification :)
> >     >
> >     > On Wed, Dec 18, 2019, 00:23 James Cameron <[1][2]quozl at laptop.org
> wrote:
> >     >
> >     >     Whether it is safe for you depends on the terms and conditions
> of the
> >     >     agreement between you and the API vendor.
> >     >
> >     >     For Sugar Labs to host and distribute your software, we
> require your
> >     >     source code to be covered by a license that would reveal the
> API key.
> >     >
> >     >     It should be up to you how you resolve those two legal issues.
> >     >
> >     >     If you need Sugar Labs to enter into an agreement with the API
> >     vendor,
> >     >     contact the oversight board.  We would still reveal the key
> though.
> >     >
> >     >     We have two other activities that have an API key clearly
> identified
> >     >     in the source code.  Random quote generator in TurtleBlocksJS,
> >     >     and currency conversion in Convert activity,
> >     >
> >     >     On Tue, Dec 17, 2019 at 03:14:36PM +0530, Naman Nimmo wrote:
> >     >     > I'm writing a new activity and for that, I'm using an open
> weather
> >     API
> >     >     but that
> >     >     > requires an API key which is personal. So is it safe to
> include my
> >     key
> >     >     along
> >     >     > with the code? And if not, then how can I use that?
> >     >     >
> >     >     > Regards,
> >     >     > Naman
> >     >
> >     >     > _______________________________________________
> >     >     > Sugar-devel mailing list
> >     >     > [2][3]Sugar-devel at lists.sugarlabs.org
> >     >     > [3][4]http://lists.sugarlabs.org/listinfo/sugar-devel
> >     >
> >     >     --
> >     >     James Cameron
> >     >     [4][5]http://quozl.netrek.org/
> >     >
> >     > References:
> >     >
> >     > [1] mailto:[6]quozl at laptop.org
> >     > [2] mailto:[7]Sugar-devel at lists.sugarlabs.org
> >     > [3] [8]http://lists.sugarlabs.org/listinfo/sugar-devel
> >     > [4] [9]http://quozl.netrek.org/
> >
> >     --
> >     James Cameron
> >     [10]http://quozl.netrek.org/
> >
> > References:
> >
> > [1] mailto:quozl at laptop.org
> > [2] mailto:quozl at laptop.org
> > [3] mailto:Sugar-devel at lists.sugarlabs.org
> > [4] http://lists.sugarlabs.org/listinfo/sugar-devel
> > [5] http://quozl.netrek.org/
> > [6] mailto:quozl at laptop.org
> > [7] mailto:Sugar-devel at lists.sugarlabs.org
> > [8] http://lists.sugarlabs.org/listinfo/sugar-devel
> > [9] http://quozl.netrek.org/
> > [10] http://quozl.netrek.org/
>
> --
> James Cameron
> http://quozl.netrek.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20191219/238f6115/attachment.html>