Re: [Sugar-devel] [sugar-sur] Develop Python-Web on Sugar, Sugarizer or Standalone - [RELEASE] Jappy 1
Please add internationalization at your earliest convenience. cjl On Mon, May 15, 2017 at 1:42 AM, Sebastian Silva wrote: > Hello Sugar friends! > > As perhaps some of you are aware, I've been working on an Activity for web > programming in Python. > > I think Python is a wonderful language for learning programming and have > always found installing Python itself a barrier. Now we can work directly > in a browser and programs will run in anywhere with very little overhead, > at very reasonable speeds! > > Currently Jappy Activity has the following features: > >- Python 3 syntax and comparable performance >- Tabbed Code editor with syntax highlighting and Solarized color >scheme >- Supports multiple files using Python's *import *syntax >- Six examples demonstrating language and API features: > - Mandala Maker > - Memorize Game > - Emoji Selector 👽 > - ... more! by me and soon, *you! 😉* > - Yes, it has built in support for ~900 Emojis you can use directly >in your code! >- Run your creations in full screen! >- Runs on Webkit2 / Chrome / Firefox browser engines (IE not tested) >- Gives access to HTML5, CSS3 *and* Javascript >- Saves session in Sugar or Sugarizer Journal if available >- Export to .zip (compiled JS code + source) >- Import from .zip or as individual files >- Jappy library offers browser friendly *print*, *inputAsync, >clearScreen* statements >- Jappy itself is written in Python / RapydScript >- Experimental standalone Android build and .XO bundle > > Under the hood, Jappy uses the excellently supported RapydScript-NG > compiler by Kovid Goyal (the author of Calibre e-book manager). This means > that although the Python semantics are well supported, the "batteries > included" actually come from Javascript-land. You may use any Javascript > library from Jappy. It's a fun way to program the browser and get over the > quirks of Javascript. > > I would sincerely appreciate your feedback and testing for this tool which > I plan to put to good use in our Artisan Videogame Workshop. Special thanks > to Laura Vargas, as well as our two children Inti and Mariana, for their > enthusiastic testing, feedback, design direction, support and patience. > This edition, version 1, "Mother's Day Edition" is dedicated to all three > of them. 👪 > > With your testing and any fixes that result, I hope to offer a pull > request for it to be included in Sugarizer. > > You can try Jappy directly at: > > http://people.sugarlabs.org/~icarito/artisan/Jappy.activity/ > > Or clone the repository and try it standalone at: > > https://github.com/somosazucar/artisan > > Experimental Android and Sugar builds are at: > > https://github.com/somosazucar/artisan/releases/tag/v1 > > Looking forward to reading your impressions, have a nice week! > > From the rainforest of Peru, > > Sebastian > > SomosAzucar.Org > > ___ > sugar-sur mailing list > sugar-...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-sur > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Develop Python-Web on Sugar, Sugarizer or Standalone - [RELEASE] Jappy 1
2017-05-15 0:42 GMT-05:00 Sebastian Silva : > Hello Sugar friends! > > As perhaps some of you are aware, I've been working on an Activity for web > programming in Python. > > I think Python is a wonderful language for learning programming and have > always found installing Python itself a barrier. Now we can work directly > in a browser and programs will run in anywhere with very little overhead, > at very reasonable speeds! > > Currently Jappy Activity has the following features: > >- Python 3 syntax and comparable performance >- Tabbed Code editor with syntax highlighting and Solarized color >scheme >- Supports multiple files using Python's *import *syntax >- Six examples demonstrating language and API features: > - Mandala Maker > - Memorize Game > - Emoji Selector 👽 > - ... more! by me and soon, *you! 😉* > - Yes, it has built in support for ~900 Emojis you can use directly >in your code! >- Run your creations in full screen! >- Runs on Webkit2 / Chrome / Firefox browser engines (IE not tested) >- Gives access to HTML5, CSS3 *and* Javascript >- Saves session in Sugar or Sugarizer Journal if available >- Export to .zip (compiled JS code + source) >- Import from .zip or as individual files >- Jappy library offers browser friendly *print*, *inputAsync, >clearScreen* statements >- Jappy itself is written in Python / RapydScript >- Experimental standalone Android build and .XO bundle > > Under the hood, Jappy uses the excellently supported RapydScript-NG > compiler by Kovid Goyal (the author of Calibre e-book manager). This means > that although the Python semantics are well supported, the "batteries > included" actually come from Javascript-land. You may use any Javascript > library from Jappy. It's a fun way to program the browser and get over the > quirks of Javascript. > > I would sincerely appreciate your feedback and testing for this tool which > I plan to put to good use in our Artisan Videogame Workshop. Special thanks > to Laura Vargas, as well as our two children Inti and Mariana, for their > enthusiastic testing, feedback, design direction, support and patience. > This edition, version 1, "Mother's Day Edition" is dedicated to all three > of them. 👪 > Thank you my dear Sebastian!!! It's been a great journey! Jappy has become not only a fun toy for our children but also a great tool for them to start modifying the code. Definitely made with love. 💟💟 > With your testing and any fixes that result, I hope to offer a pull > request for it to be included in Sugarizer. > > You can try Jappy directly at: > > http://people.sugarlabs.org/~icarito/artisan/Jappy.activity/ > > Or clone the repository and try it standalone at: > > https://github.com/somosazucar/artisan > > Experimental Android and Sugar builds are at: > > https://github.com/somosazucar/artisan/releases/tag/v1 > > Looking forward to reading your impressions, have a nice week! > > From the rainforest of Peru, > > Sebastian > > SomosAzucar.Org > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > -- Laura V. * I&D SomosAZUCAR.Org* “Solo la tecnología libre nos hará libres.” ~ Laura Victoria Happy Learning! #LearningByDoing #Projects4good #IDesignATSugarLabs #WeCanDoBetter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] (Goals and Mission) with Microsoft in it?
I'm using 13.2.7 . I would use the workaround. Thanks. *Ibiam Chihurumnaya* On Sun, May 14, 2017 at 9:58 PM, James Cameron wrote: > Thanks. Are you using 13.2.8? > > The Fedora repositories for Fedora 18 moved, and this was fixed in > 13.2.8, see here; > > http://wiki.laptop.org/go/Release_notes/13.2.7#Fedora_Repositories_Missing > > If you are using 13.2.7 or earlier, please use the workaround on that > page. > > I've just tested "sudo yum install vlc" on XO-1.5 with 13.2.8 and no > problem seen, just "No package vlc available.", so I'm not sure how > your system is configured; if the above workaround does not fix, > please show me your changed yum.repos.d files. > > On Sat, May 13, 2017 at 08:48:54PM +0100, Chihurumnaya Ibiam wrote: > > Hey James, since you're still maintaining fedora18, "sudo yum vlc" - any > > activity- returns this error "Error cannot retrieve metalink for > repository > > fedora18/i386" , editing the *fedora.repo files in /etc/yum.repos.d/ and > > changing > > all "https" to "http" solves the problem. > > > > Ibiam Chihurumnaya > > > > On Sat, May 13, 2017 at 1:58 AM, James Cameron <[1]qu...@laptop.org> > wrote: > > > > Composite reply to several posts, in context, see below; > > > > Samson wrote: > > > I think we should really join the trend so that we can get more > > > people using Sugar for Learning. So what are your thought on this > > > development? > > > > I don't think it will work, as we don't have developers interested in > > it. If you're interested in it and are happy to commit fully without > > relying on others, go for it. But don't expect other resources to > get > > involved; as the argument from numbers is not compelling enough. > > > > There are more learning tools available for Windows. > > > > But the numbers are not the only reason why our customers choose > > Linux. > > > > Sebastian wrote: > > > Sugar barely runs [...] > > > > Yes, you're right. > > > > > committed releasing Sugar every six months [...] we have no release > > > schedule. > > > > Yes, you're right. > > > > A new release of Sugar with the bug fixes since 0.110 would help > solve > > the "barely runs" problem. > > > > (also a release of the critical activities, not just the core; > > newcomers to our community should note the term Sucrose has been in > > our Taxonomy for many years, see the Wiki if you don't know what it > > means.) > > > > [2]https://wiki.sugarlabs.org/go/Taxonomy > > [3]https://wiki.sugarlabs.org/go/Glossary > > > > > I don't see Sugar Labs organization as capable of strategically > > > funding Sugar development in any direction. Of course, volunteers > > > can work in whatever they like, if it fits their principles. > > > > I agree, and that's the basis of my engagement; subject to also > > stabilising Sugar for OLPC OS on Fedora 18 and Ubuntu 16.04 for > > delivery to OLPC customers; as a custom system with all obvious (to > > me) bugs fixed. > > > > Sugar Labs is heavily benefiting from my work for OLPC, and OLPC is > > benefiting from other volunteers at Sugar Labs. > > > > Dave wrote: > > > codebase could be returned to OLPC > > > > No thanks. Where would the Sugar Labs volunteers go who are focused > > on this codebase? > > > > OLPC already maintains a fork with the fixes, and the changes that > > Sugar Labs has not accepted. All fixes have been pushed back to > Sugar > > Labs, but there has been no release, hence the exceedingly low > quality > > of the Fedora, Debian and Ubuntu experience at the moment. > > > > OLPC fork version numbers are like 0.110.0.olpc.12 > > > > > Sugar Labs could focus on the JS Sugarizer codebase. > > > > Sugarizer isn't integrated into Sugar Labs; the repositories are > > split, cooperation is minimal, and the code for activities isn't > > portable to execution environments other than Sugarizer; such as > > sugar-web-activity. > > > > So I'm certainly not inclined to support any activity development on > > Sugarizer; because that development won't pay back for OLPC. > > > > I'm probably going to have to port the Moon activity from GTK+ 2 to > > GTK+ 3 unless someone can make the JavaScript version work on > desktop. > > ;-) I did get half way through. > > > > Zeeshan Khan also has the task for GsoC, so we might do it together. > > > > I'd like to hear from Ignacio, Sam Parkinson and Abhijit what they > > think of the port of Moon vs the JavaScript port; it may be simpler > to > > port the JavaScript version back to Sugar. > > > > Samuel Cantero wrote: > > > We should work to find out a new release manager [...] > > > > Ignacio is the release manager at the moment, but my guess is that > > he'd welcome someone else taking the job. Hopefully he'll speak up. > > > > Dave wrote: > > >
