Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

Hi, James Actually Sugar has files, directories and a command shell (Terminal activity). It is relatively easy to switch activities via the Frame. I say this from several years of experience developing on the XO (easier than using usb keys to move code to the XO to test). The fact that

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

Tony, The code for the EPUB utility is here: https://github.com/sugarlabs/ebooktools This is the repository I set up for *E-Book Enlightenment.* The relevant files are: striphtml.py and genbook.sh You export your manuscript as HTML with the file name input.html, then run genbook.sh. That

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

Hi, James I think your code to convert html to epub could be useful. At the moment, my preferred scheme is to write tutorials using the Zim Wiki, then export them to html. However, epub files might be easier to download and to read with Browse. I have patched Browse so that it downloads pdf,

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

Tony, I strongly agree that students should be exposed to the command line and learn all about Software Tools. The key, I think, is to give them fun things to do that demonstrate the power of the command line. They need something more interesting than Hello World and calculating the current value

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

Gonzalo, I did look at the activity. However, I think there is immense value in introducing learners to the Terminal activity and the nano text editor. Through the shell, Sugar users have access to the file system and to all of the power of the Unix programming environment. At the moment

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

Gonzalo, I looked at it maybe two years ago. I still lurk on the mailing lists for this project but I'm not actively developing anything, so my opinions may have passed their sell by date. James Simmons On Thu, Mar 16, 2017 at 6:33 AM, Gonzalo Odiard wrote: > Have you

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

James, Sugar now provides in the Journal a link to the Documents directory. This, of course, has the problem that the display does not show subdirectories. I have toyed with the idea of having the tutorials use Sugar Commander and the excellent gedit activity instead of the shell and nano.

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

Tony, I own an XO laptop from the first Give One Get One promotion, so I know what it can do. I've used the Terminal Activity and I wrote the Sugar Commander Activity because I thought that the original design of Sugar, which made your thumb drive look like the Journal, was not such a hot idea.

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

Hi, James If you go to activities.sugarlabs.org, you can register via the register link at the top right. This is not registration for Sugarlabs but for ASLO. As I understand the github repository, access with the ability to commit changes is closely held. The enables proposed changes to be

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

All, I only meant to make the manual actually tell where we currently put our code repositories, without rewriting the whole chapter. (I had hoped that a Google Code-In mentee might do that, but it didn't happen). The one piece of information that is still lacking is how to have your account

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

On Tue, Mar 14, 2017 at 10:28 AM, Laura Vargas wrote: > > > 2017-03-14 7:13 GMT-05:00 Walter Bender : > >> >> >> On Tue, Mar 14, 2017 at 12:45 AM, Tony Anderson >> wrote: >> >>> >>> >>> On 03/14/2017 12:03 PM, Alex Perez

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

2017-03-14 7:13 GMT-05:00 Walter Bender : > > > On Tue, Mar 14, 2017 at 12:45 AM, Tony Anderson > wrote: > >> >> >> On 03/14/2017 12:03 PM, Alex Perez wrote: >> >> >> I would think ASLO could simply be made to inspect the contents of an >>

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

On Tue, Mar 14, 2017 at 12:45 AM, Tony Anderson wrote: > > > On 03/14/2017 12:03 PM, Alex Perez wrote: > > > I would think ASLO could simply be made to inspect the contents of an > activity, upon upload, (since it’s just a zip file), and look for the > necessary string

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

On 03/14/2017 12:03 PM, Alex Perez wrote: I would think ASLO could simply be made to inspect the contents of an activity, upon upload, (since it’s just a zip file), and look for the necessary string within activity.info , such that it could be displayed under a

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

Hi, Walter On 03/14/2017 11:02 AM, Alex Perez wrote: ASLO is not a source code repository. It’s a convenience to end users. I know you think they should be one and the same, and in theory they could be, but I don’t necessarily see the benefit. The source code repository for a Sugar activity

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

Hi, Walter and Alex Alex, if you are referring to maintaining ASLO, +1. My point was not about either gitorious or github but the fact that by design the source code for every activity (with some binary exceptions) is in the bundle. It is always clear where the source is located, in the

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

Tony/Walter, > On Mar 13, 2017, at 7:28 PM, Walter Bender wrote: > > Tony, > > Not sure I agree about your asserts regarding github vs gitroious. Count me in here.. > > (1) the were/are many activities that were not hosted in gitorious long > before we switched to

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

Tony, Not sure I agree about your asserts regarding github vs gitroious. (1) the were/are many activities that were not hosted in gitorious long before we switched to github, so it wasn't obvious where to find the source repo *before* the switch. This is one of the reasons I started add the repo

Re: [Sugar-devel] Minor update to Make Your Own Sugar Activities!

Hi James, Your book is a wonder and should be much more actively promoted. It is one of the major contributions of Sugar to constructive learning. I believe the use of git.sugarlabs.org and github are major steps backwards from the original conception of Sugar activities as something which

[Sugar-devel] Minor update to Make Your Own Sugar Activities!

All, I have been neglecting the manual *Make Your Own Sugar Activities!* ever since I first wrote it. However, I did manage to make one needed update in the laziest way possible. Since Sugar Labs has moved away from git.sugarlabs.org in favor of GitHub since I wrote the version control chapter I