<div dir="ltr">Thanks a lot @quozl<div>I'll let you know when I'm ready to release it.</div></div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Dec 19, 2019 at 1:55 AM James Cameron <<a href="mailto:quozl@laptop.org">quozl@laptop.org</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">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]<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a> 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]<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a> 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]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a> > > > [3][4]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > > > > -- > > James Cameron > > [4][5]<a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a> > > > > References: > > > > [1] mailto:[6]<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a> > > [2] mailto:[7]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a> > > [3] [8]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > > [4] [9]<a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a> > > -- > James Cameron > [10]<a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a> > > References: > > [1] mailto:<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a> > [2] mailto:<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a> > [3] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a> > [4] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > [5] <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a> > [6] mailto:<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a> > [7] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a> > [8] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > [9] <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a> > [10] <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a> -- James Cameron <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a> </blockquote></div>