<div dir="ltr"><div>I think 'pip install jupyter' should do the trick. I think doing that we might be able to bundle jupyter and then run it. Not sure if this is recommended in sugar.</div><div> </div><div>Thanks,</div><div>Muhammad Usman</div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Mar 30, 2019 at 2:23 PM <<a href="mailto:sugar-devel-request@lists.sugarlabs.org">sugar-devel-request@lists.sugarlabs.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">Message: 2 Date: Sat, 30 Mar 2019 15:01:18 +0800 From: Tony Anderson <<a href="mailto:tony_anderson@usa.net" target="_blank">tony_anderson@usa.net</a>> To: <a href="mailto:sugar-devel@lists.sugarlabs.org" target="_blank">sugar-devel@lists.sugarlabs.org</a> Subject: Re: [Sugar-devel] GSoC: Proposal for "Create new activities" Message-ID: <<a href="mailto:22693bf3-d39b-6eac-941e-0a7180b662f9@usa.net" target="_blank">22693bf3-d39b-6eac-941e-0a7180b662f9@usa.net</a>> Content-Type: text/plain; charset="utf-8"; Format="flowed" Good start. A reasonable way to start would be to install the server in gnome so that it works on the XO. This is going to be a bit tricky because Sugar on the XO is based on Fedora 18. One of the current modules required by pip is not supported by Fedora 18. In considering how I might proceed, I decided it would be easiest to install Jupyter on Ubuntu 18.04 and use the sucre install of Sugar to build and test the 'Jupyter-activity' wrapper, pushing off the XO dependency issues. Tony On 3/30/19 1:49 PM, Muhammad Usman wrote: > I have personally used jupyter for a long time, so I have a fair > amount of experience using it. > > As I can see, jupyter-notebook kind of requires the whole GSoC period, > therefore I would consider it as a separate project from the other and > write a different proposal for it. > > As for the design of the project, My understanding of going about > doing the project is: > - Install jupyter using pip. Install additional libraries such as > Latex to allow for the rendering of notebook as pdf and so on. > - Start with the jupyter server and modify the server to use journal, > removable devices along with using the file system. > - Make changes to frontend to display the notebook options appropriately. > - Display each language as a separate notebook option. > - Write a wrapper around the server controlling the starting of server > and the shutdown on exiting. > - Have examples and getting started tutorials. > - Lastly, have a detailed user documentation. > > Thanks, > Muhammad Usman > > On Sat, Mar 30, 2019 at 5:09 AM > <<a href="mailto:sugar-devel-request@lists.sugarlabs.org" target="_blank">sugar-devel-request@lists.sugarlabs.org</a> > <mailto:<a href="mailto:sugar-devel-request@lists.sugarlabs.org" target="_blank">sugar-devel-request@lists.sugarlabs.org</a>>> wrote: > > Message: 3 > Date: Fri, 29 Mar 2019 16:38:47 +0800 > From: Tony Anderson <<a href="mailto:tony_anderson@usa.net" target="_blank">tony_anderson@usa.net</a> > <mailto:<a href="mailto:tony_anderson@usa.net" target="_blank">tony_anderson@usa.net</a>>> > To: <a href="mailto:sugar-devel@lists.sugarlabs.org" target="_blank">sugar-devel@lists.sugarlabs.org</a> > <mailto:<a href="mailto:sugar-devel@lists.sugarlabs.org" target="_blank">sugar-devel@lists.sugarlabs.org</a>> > Subject: Re: [Sugar-devel] GSoC: Proposal for "Create new activities" > Message-ID: <<a href="mailto:a3f8d544-a6f6-35be-5fe1-6cc8e138dcd2@usa.net" target="_blank">a3f8d544-a6f6-35be-5fe1-6cc8e138dcd2@usa.net</a> > <mailto:<a href="mailto:a3f8d544-a6f6-35be-5fe1-6cc8e138dcd2@usa.net" target="_blank">a3f8d544-a6f6-35be-5fe1-6cc8e138dcd2@usa.net</a>>> > Content-Type: text/plain; charset=utf-8; format=flowed > > The Jupyter Notebook project is of particular interest to me. > > Over the past several GSOC periods, developers have had a problem > completing their projects within the allotted time. You are > proposing to > take on several projects, any one of which is a big load for one > summer. > > If you undertake the Jupyter Notebook project, I would hope that > is your > only task for the summer. Completing it in a usable form in the GSOC > period would be a major, noteworthy accomplishment. > > The Jupyter Notebook started life as ipython. The Jupyter > implementation > supports multiple programming languages (e.g. bash, python, web > (javascript, html5, css), and many others. It can also be used to > make > interactive lessons on science and mathematics topics independent of > programming). > > The essence of the ipython server is that it accepts a url for a file > (*.ipynb). It then processes this file displaying cells and running > cells interactively based on the requirements of the notebook > author and > input from the user. > > As an activity, (called for example, Jupyter-activity), it should > resume > .ipynb files in the Journal. The browser for this activity can be the > Browse activity (testing to be sure that the WebKit browser in the > Browse activity supports Jupyter). This is unlikely to be a > show-stopper. If executed with start-new, it should enable the > user to > designate a notebook to run (among those in the Journal, Documents > folder, or a mounted removable device). It should also enable a > user to > create a notebook. > > The technology involved in this project is Jupyter. The team at > Jupyter > is friendly and helpful, in my experience. I doubt there will be an > significant need to modify the Browse activity. One limitation that > could be addressed en passant is that when Browse is resumed, it > launches a new instance rather than opening a tab in a running copy. > This is OK but seems primitive compared to other browsers. > > There is a large library online of Jupyter notebooks with many > tutorials. The first step in this project is to become familiar with > these notebooks. Jupyter can be installed on Linux distributions via > Anaconda - but this is overkill for the XO. It can also be > installed by > yum (apt for Ubuntu) but better by pip. > > The storage available to the XO is extremely limited (XO has 1GB, > other > models have 4GB). This means that the Anaconda implementation which > incorporates many additional valuable packages is probably too > large for > Sugar on an XO (still over 80% of the systems in the wild). Even > so, the > Pip install may need some optional capabilities such as Latex and > MatLab. > > One of the critical parts of an implementation frequently gets > left to > the end and then is not done - user documentation. Thanks to Gonzalo > Odiard, Sugar has an excellent documentation capability based on > Sphinx > - see <a href="http://help.sugarlabs.org" rel="noreferrer" target="_blank">help.sugarlabs.org</a> <<a href="http://help.sugarlabs.org" rel="noreferrer" target="_blank">http://help.sugarlabs.org</a>>. The > 'Jupyter-activity' will need documentation > that meets the needs of primary school students with limited computer > experience and limited skills in Englsih. This could include a > recommended library of Jupyter notebooks which can be used on the XO > (esp. bash, python, and web langauges). > > Tony > > Tony > > On 3/29/19 3:52 PM, James Cameron wrote: > > Thanks, interesting. > > > > Technical comments; Jupyter Notebook Activity, you suggest stripping > > down Browse activity. You might instead presume Browse is present > > and call it directly. This is what the Wikipedia activity does. It > > isn't what the Help activity does. > > > > Please also consider the design and user requirements input in this > > closed issue; <a href="https://github.com/sugarlabs/GSoC/issues/13" rel="noreferrer" target="_blank">https://github.com/sugarlabs/GSoC/issues/13</a> Especially > > note Jupyter Lab; a richer environment than a browser alone. > > > > On Thu, Mar 28, 2019 at 06:22:03PM +0530, Muhammad Usman wrote: > >> Hello all! > >> I am Muhammad Usman. I am sharing my draft proposal for Create > New Activities > >> and Write activity in Sugarizer. Please do take a look at it > and let me know > >> your thoughts. > >> > [1]<a href="https://gist.github.com/usmanmuhd/ce60a3dd2c43fd5c5fe5154b5bc18750" rel="noreferrer" target="_blank">https://gist.github.com/usmanmuhd/ce60a3dd2c43fd5c5fe5154b5bc18750</a> > >> > >> Regards, > >> Muhammad Usman > >> > >> References: > >> > >> [1] > <a href="https://gist.github.com/usmanmuhd/ce60a3dd2c43fd5c5fe5154b5bc18750" rel="noreferrer" target="_blank">https://gist.github.com/usmanmuhd/ce60a3dd2c43fd5c5fe5154b5bc18750</a> > >> _______________________________________________ > >> Sugar-devel mailing list > >> <a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a> > <mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a>> > >> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > > > > > _______________________________________________ > Sugar-devel mailing list > <a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a> > <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> -------------- next part -------------- An HTML attachment was scrubbed... URL: <<a href="http://lists.sugarlabs.org/archive/sugar-devel/attachments/20190330/658934cf/attachment.html" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/archive/sugar-devel/attachments/20190330/658934cf/attachment.html</a>> ------------------------------ Subject: Digest Footer _______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> ------------------------------ End of Sugar-devel Digest, Vol 125, Issue 82 ******************************************** </blockquote></div></div>