Re: [IAEP] [Sugar-devel] (Goals and Mission) with Microsoft in it?
Thanks, I'll review it. On Thu, May 18, 2017 at 11:09:06PM -0500, Sebastian Silva wrote: > Hi James, > > I've found a moment to make Moon (JS) work in Sugar again. The version > in the original repo was only missing a small patch. > > https://github.com/zhirzh/sugarizer-activity-moon/pull/13 > > Hope you find it useful, > > Regards, > > Sebastian > > > On 12/05/17 19:58, James Cameron wrote: > > 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. > > -- James Cameron http://quozl.netrek.org/ ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] (Goals and Mission) with Microsoft in it?
Hi James, I've found a moment to make Moon (JS) work in Sugar again. The version in the original repo was only missing a small patch. https://github.com/zhirzh/sugarizer-activity-moon/pull/13 Hope you find it useful, Regards, Sebastian On 12/05/17 19:58, James Cameron wrote: > 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. ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] New ASLO Project Definition
Hi Chris Currently there are two text fields per activity in ASLO: Summary and Description. This gets a bit more complicated since these text fields edited by the developer in github. Perhaps this might work. Have a po directory in the activities/ directory of the bundle. When the activity page is selected Django can select the summary string from the appropriate po and send it to the html template. This method would work for both summary and description. With the pootle default to display the POT string, no harm can be done. Sam Cantaro mentioned using webhooks to notify ASLO when a new activity version has been released. Perhaps such a hook could be used to notify you of the need to review localization for the activity and another hook to notify ASLO to update the bundle to integrate the localization. Tony On 05/19/2017 10:08 AM, Chris Leonard wrote: On Thu, May 18, 2017 at 9:57 PM, Tony Andersonwrote: On 05/19/2017 09:24 AM, Chris Leonard wrote: The more difficult question is how to localize the summary and description of the individual activities. At present, it appears we don't attempt to localize this information. The first thought that pops into my mind is the very brief Activity description that is in the activity.info file and is frequently, but not always captured in the PO file for localization. With that as background, making changes to activity,info format to include a richer description seems feasible as does doing a better job of tooling the i18n so that these activity.info fields are more consistently captured in the PO files. Having ASLO parse the activity.info file of the hosted packages relevant PO file seems a reasonable approach that would mean that ASLO doesn't have to have separately maintained knowledge of the Activities being hosted, it justs picks it up from the upload of the package itself. . Just a thought. cjl . ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Sugarizer - I18n/L10n query
I will look at it. Have been using webL10n.js which, via a simple script can leverage the power files. On May 18, 2017 11:21 PM, "Chris Leonard"wrote: > Have any of our Javasript / Sugarizer folks played around with > xgettext-js yet? > > https://www.npmjs.com/package/xgettext-js > > If it helps us improve the L10n of Sugarizer via leveraging Pootle > hosting or even just all of the hopefully similar strings already > completed for corresponding Python versions of Activities in Pootle, > it would possibly be a big win. > > cjl > ___ > Sugar-devel mailing list > sugar-de...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] New ASLO Project Definition
I mis-phrased that slightly. ASLO would parse the PO files for the lines drawn from the activity,info file during POT generation (i18n), not parse the activity.info file itself (which I think ASLO already does for versuion number, etc.). The idea is that the activity,info description in Engiish would be localized in the relevant PO files at the time of L10n of the Activity's UI strings. cjl On Thu, May 18, 2017 at 10:08 PM, Chris Leonardwrote: > On Thu, May 18, 2017 at 9:57 PM, Tony Anderson wrote: >> On 05/19/2017 09:24 AM, Chris Leonard wrote: >>> >> The more difficult question is how to localize the summary and description >> of the individual activities. At present, it appears we don't attempt to >> localize this information. > > The first thought that pops into my mind is the very brief Activity > description that is in the activity.info file and is frequently, but > not always captured in the PO file for localization. With that as > background, making changes to activity,info format to include a richer > description seems feasible as does doing a better job of tooling the > i18n so that these activity.info fields are more consistently captured > in the PO files. Having ASLO parse the activity.info file of the > hosted packages relevant PO file seems a reasonable approach that > would mean that ASLO doesn't have to have separately maintained > knowledge of the Activities being hosted, it justs picks it up from > the upload of the package itself. . Just a thought. > > cjl ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] New ASLO Project Definition
On Thu, May 18, 2017 at 9:57 PM, Tony Andersonwrote: > On 05/19/2017 09:24 AM, Chris Leonard wrote: >> > The more difficult question is how to localize the summary and description > of the individual activities. At present, it appears we don't attempt to > localize this information. The first thought that pops into my mind is the very brief Activity description that is in the activity.info file and is frequently, but not always captured in the PO file for localization. With that as background, making changes to activity,info format to include a richer description seems feasible as does doing a better job of tooling the i18n so that these activity.info fields are more consistently captured in the PO files. Having ASLO parse the activity.info file of the hosted packages relevant PO file seems a reasonable approach that would mean that ASLO doesn't have to have separately maintained knowledge of the Activities being hosted, it justs picks it up from the upload of the package itself. . Just a thought. cjl ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] New ASLO Project Definition
Dear Jatin, Welcome to the Sugar Labs community, When reworking ASLO (a very valuable project), please do keep internationalization (i18n) and localization (L10n) in mind. You may or may not know that we do host PO files for L10n of NewASLO on our Pootle translation server: https://translate.sugarlabs.org/projects/NewAslo/ We currently have very complete coverage in the following languages: Swedish, Spanish, Russian, Guaraní (Paraguay), English (United Kingdom), English, Dutch, Danish, Catalan, Albanian, Igbo. Obviously the fewer un-necessary UI string changes, the better we will be in terms of localizing the new product of your work, The Translation Team will obviously take care of any strings that must be changed to produce a better ASLO, but changes for the sake of changes can hopefully be avoided if the existing strings serve the intended purpose. Having the Spanish translation complete in a production instance is probably more important than any other language given the number of Spanish-speaking users we typically want to reach, but as FOSS, if you're going to accommodate more than one language, you might as well make it easy for all of them. When you get ready to go-live with the new ASLO service, we'd obviously love to have the chance (a week or two of string freeze) to catch up with your work and make sure what gets deployed reaches our key audiences in their native language(s). Laura Vargas would be a fine guide to i18n/L10n practices in Sugar Labs, but if you have any questions, feel free to reach out to me and I'll try to help, I'll probably be the one to contact about grabbing a new POT template from your repository and uploading it to Pootle for the localizers to work on, as well as generating the pull request when they have completed their work on the specific language's PO file. Looking forward to seeing your work blossom. cjl On Thu, May 18, 2017 at 3:37 AM, Jatin Dhankharwrote: > Hi, > Thank you Laura for attaching the proposal. > I will be glad if you can point me in the right direction regarding my GSOC > project, suggest flaws and how it can be improved. If anyone has any > questions or speculations, feel free to ping me. I am also writing weekly > summary of GSOC here https://jatindhankhar.in/posts/. > If something is missing or incorrect, let me know. > > Thanks, > Jatin Dhakhar > > On Thu, May 18, 2017 at 9:10 AM, Laura Vargas > wrote: >> >> >> Hi Jatin welcome to Sugar Labs Community! >> >> Hi Aleksey, >> >> I hope to find time to be able to follow Jatin's project proposed time >> line. I hope you can find some time too. See pdf attached for project's >> details. >> >> Regards and blessings to all the team, >> >> >> Laura Victoria >> >> >> >> >> -- Forwarded message -- >> From: Tony Anderson >> Date: 2017-05-17 18:57 GMT-05:00 >> Subject: Re: [Sugar-devel] New ASLO Project Definition >> To: Laura Vargas >> >> >> Hi, Laura >> >> Done. >> >> Tony >> >> >> On 05/18/2017 12:56 AM, Laura Vargas wrote: >> >> Samuel and new ASLO team, >> >> Can you please attach the pdf with the project description? >> >> In my opinion, as ASLO is such a powerful resource used today by active >> deployments, a successful successor will provide at least the same services. >> >> Regards >> >> Laura V. >> I SomosAZUCAR.Org >> >> “Solo la tecnología libre nos hará libres.” >> ~ Laura Victoria >> >> Happy Learning! >> #LearningByDoing >> #Projects4good >> #IDesignATSugarLabs >> #WeCanDoBetter >> >> >> ___ >> Sugar-devel mailing list >> sugar-de...@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> >> > > > ___ > IAEP -- It's An Education Project (not a laptop project!) > IAEP@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/iaep ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] New ASLO Project Definition
s/These are my notes/These are some notes/g :) Walter Bender has helped me to shape this first proposal. On Thu, May 18, 2017 at 4:22 PM, Samuel Canterowrote: > Hi all, > > These are my notes in order to augment current proposal: https://goo.gl/ > VEIzCr > > You can add comments/suggestions to the document. > > Best regards, > > Sam C. > > On Thu, May 18, 2017 at 3:37 AM, Jatin Dhankhar > wrote: > >> Hi, >> Thank you Laura for attaching the proposal. >> I will be glad if you can point me in the right direction regarding my >> GSOC project, suggest flaws and how it can be improved. If anyone has any >> questions or speculations, feel free to ping me. I am also writing weekly >> summary of GSOC here https://jatindhankhar.in/posts/. >> If something is missing or incorrect, let me know. >> >> Thanks, >> Jatin Dhakhar >> >> On Thu, May 18, 2017 at 9:10 AM, Laura Vargas >> wrote: >> >>> >>> Hi Jatin welcome to Sugar Labs Community! >>> >>> Hi Aleksey, >>> >>> I hope to find time to be able to follow Jatin's project proposed time >>> line. I hope you can find some time too. See pdf attached for project's >>> details. >>> >>> Regards and blessings to all the team, >>> >>> >>> Laura Victoria >>> >>> >>> >>> >>> -- Forwarded message -- >>> From: Tony Anderson >>> Date: 2017-05-17 18:57 GMT-05:00 >>> Subject: Re: [Sugar-devel] New ASLO Project Definition >>> To: Laura Vargas >>> >>> >>> Hi, Laura >>> >>> Done. >>> >>> Tony >>> >>> >>> On 05/18/2017 12:56 AM, Laura Vargas wrote: >>> >>> Samuel and new ASLO team, >>> >>> Can you please attach the pdf with the project description? >>> >>> In my opinion, as ASLO is such a powerful resource used today by active >>> deployments, a successful successor will provide at least the same services. >>> >>> Regards >>> >>> Laura V. >>> * I SomosAZUCAR.Org* >>> >>> “Solo la tecnología libre nos hará libres.” >>> ~ Laura Victoria >>> >>> Happy Learning! >>> #LearningByDoing >>> #Projects4good >>> #IDesignATSugarLabs >>> #WeCanDoBetter >>> >>> >>> ___ >>> Sugar-devel mailing >>> listSugar-devel@lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel >>> >>> >>> >>> >> > ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] New ASLO Project Definition
Hi all, These are my notes in order to augment current proposal: https://goo.gl/VEIzCr You can add comments/suggestions to the document. Best regards, Sam C. On Thu, May 18, 2017 at 3:37 AM, Jatin Dhankharwrote: > Hi, > Thank you Laura for attaching the proposal. > I will be glad if you can point me in the right direction regarding my > GSOC project, suggest flaws and how it can be improved. If anyone has any > questions or speculations, feel free to ping me. I am also writing weekly > summary of GSOC here https://jatindhankhar.in/posts/. > If something is missing or incorrect, let me know. > > Thanks, > Jatin Dhakhar > > On Thu, May 18, 2017 at 9:10 AM, Laura Vargas > wrote: > >> >> Hi Jatin welcome to Sugar Labs Community! >> >> Hi Aleksey, >> >> I hope to find time to be able to follow Jatin's project proposed time >> line. I hope you can find some time too. See pdf attached for project's >> details. >> >> Regards and blessings to all the team, >> >> >> Laura Victoria >> >> >> >> >> -- Forwarded message -- >> From: Tony Anderson >> Date: 2017-05-17 18:57 GMT-05:00 >> Subject: Re: [Sugar-devel] New ASLO Project Definition >> To: Laura Vargas >> >> >> Hi, Laura >> >> Done. >> >> Tony >> >> >> On 05/18/2017 12:56 AM, Laura Vargas wrote: >> >> Samuel and new ASLO team, >> >> Can you please attach the pdf with the project description? >> >> In my opinion, as ASLO is such a powerful resource used today by active >> deployments, a successful successor will provide at least the same services. >> >> Regards >> >> Laura V. >> * I SomosAZUCAR.Org* >> >> “Solo la tecnología libre nos hará libres.” >> ~ Laura Victoria >> >> Happy Learning! >> #LearningByDoing >> #Projects4good >> #IDesignATSugarLabs >> #WeCanDoBetter >> >> >> ___ >> Sugar-devel mailing >> listSugar-devel@lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel >> >> >> >> > ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] New ASLO Project Definition
Hi, Thank you Laura for attaching the proposal. I will be glad if you can point me in the right direction regarding my GSOC project, suggest flaws and how it can be improved. If anyone has any questions or speculations, feel free to ping me. I am also writing weekly summary of GSOC here https://jatindhankhar.in/posts/. If something is missing or incorrect, let me know. Thanks, Jatin Dhakhar On Thu, May 18, 2017 at 9:10 AM, Laura Vargaswrote: > > Hi Jatin welcome to Sugar Labs Community! > > Hi Aleksey, > > I hope to find time to be able to follow Jatin's project proposed time > line. I hope you can find some time too. See pdf attached for project's > details. > > Regards and blessings to all the team, > > > Laura Victoria > > > > > -- Forwarded message -- > From: Tony Anderson > Date: 2017-05-17 18:57 GMT-05:00 > Subject: Re: [Sugar-devel] New ASLO Project Definition > To: Laura Vargas > > > Hi, Laura > > Done. > > Tony > > > On 05/18/2017 12:56 AM, Laura Vargas wrote: > > Samuel and new ASLO team, > > Can you please attach the pdf with the project description? > > In my opinion, as ASLO is such a powerful resource used today by active > deployments, a successful successor will provide at least the same services. > > Regards > > Laura V. > * I SomosAZUCAR.Org* > > “Solo la tecnología libre nos hará libres.” > ~ Laura Victoria > > Happy Learning! > #LearningByDoing > #Projects4good > #IDesignATSugarLabs > #WeCanDoBetter > > > ___ > Sugar-devel mailing > listSugar-devel@lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel > > > > ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep