Re: [Sugar-devel] Presentation
Welcome Gabriel! Gonzalo On Thu, Mar 20, 2014 at 5:14 PM, Gabriel Hernán Perez glpp2014.g...@gmail.com wrote: Hello everyone, My name is Gabriel and I am a mathematics student from Buenos Aires, Argentina. I have some experience with Smalltalk and Python and I'm looking forward to keep working on my skills. That's why I want to participate on GSOC this summer through this community :) I discovered Sugar Labs through Ricardo Moran, a coworker (who I think introduced himself earlier in this list). I became interested because of my previous contact with Etoys, which initially helped me to understand different OO concepts. During this GSOC I'd like to work on a touch-capable interface for Etoys, given how useful and intuitive I found it when I first started learning about computer sciences and the current popularity of touch devices (and how Sugar seems to wish to incorporate this technology into future platforms). Here's a link to my application's wiki page (still working on it): http://wiki.sugarlabs.org/go/Summer_of_Code/2014/Etoys_Touch_UI That being said, I hope to hear from you all soon! Regards, Gabriel. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] shipped languages/locales
I think was done to preserve space. Not sure if that is a concern now. Gonzalo On Sun, Mar 9, 2014 at 8:43 PM, me m...@jvonau.ca wrote: Hi All: I'm wondering if there is any reason why there are po files generated for the source in git, these are included as .mo files in the src rpm, but not shipped in the released rpms. Compare the list in git[1] and what becomes installed in the resulting rpm through ALL_LINGUAS=[2]. Is there any reason for this? Would it be worthwhile to ship all available translations? Jerry 1. https://github.com/sugarlabs/sugar/tree/master/po 2. https://github.com/sugarlabs/sugar/blob/master/configure.ac ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] New method for Activity class to send notifications
Hello Everyone, We recently landed a messages notifications feature, based on Gary's designs [1]. One of our GCI 2013 hackers, Sam Parkinson, is has sent the bits to enable activities to send notifications too, as in Gary's design. His work is almost done [2,3,4], but it introduces a new method to the base Activity class, therefore I wanted your opinions regarding the name of this method, the current options are [4]: * send_notification * add_notification * shell_notify * sugar_notify Thanks for your time! tch. Refs: 1. http://wiki.sugarlabs.org/go/Design_Team/Proposals/Notifications 2. https://github.com/sugarlabs/sugar/pull/301 3. https://github.com/sugarlabs/sugar/pull/300 4. https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/114 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New method for Activity class to send notifications
I vote for add_notification Gonzalo On Wed, Mar 26, 2014 at 9:40 AM, Martin Abente martin.abente.lah...@gmail.com wrote: Hello Everyone, We recently landed a messages notifications feature, based on Gary's designs [1]. One of our GCI 2013 hackers, Sam Parkinson, is has sent the bits to enable activities to send notifications too, as in Gary's design. His work is almost done [2,3,4], but it introduces a new method to the base Activity class, therefore I wanted your opinions regarding the name of this method, the current options are [4]: * send_notification * add_notification * shell_notify * sugar_notify Thanks for your time! tch. Refs: 1. http://wiki.sugarlabs.org/go/Design_Team/Proposals/Notifications 2. https://github.com/sugarlabs/sugar/pull/301 3. https://github.com/sugarlabs/sugar/pull/300 4. https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/114 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] shipped languages/locales
Just wondering how AU is reacting without having the correct spelling for 'favourites', 'neighbourhood' that comes with en_BR. This is a regression from DX4 that included such support. It would be better would really support en_AU thou. just my thoughts, Jerry On March 26, 2014 at 6:59 AM Gonzalo Odiard godi...@sugarlabs.org wrote: I think was done to preserve space. Not sure if that is a concern now. Gonzalo On Sun, Mar 9, 2014 at 8:43 PM, me m...@jvonau.ca wrote: Hi All: I'm wondering if there is any reason why there are po files generated for the source in git, these are included as .mo files in the src rpm, but not shipped in the released rpms. Compare the list in git[1] and what becomes installed in the resulting rpm through ALL_LINGUAS=[2]. Is there any reason for this? Would it be worthwhile to ship all available translations? Jerry 1. https://github.com/sugarlabs/sugar/tree/master/po 2. https://github.com/sugarlabs/sugar/blob/master/configure.ac ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] shipped languages/locales
Honestly, they didn't complained yet. Thanks for pointing that. Gonzalo On Wed, Mar 26, 2014 at 10:33 AM, Jerry Vonau m...@jvonau.ca wrote: Just wondering how AU is reacting without having the correct spelling for 'favourites', 'neighbourhood' that comes with en_BR. This is a regression from DX4 that included such support. It would be better would really support en_AU thou. just my thoughts, Jerry On March 26, 2014 at 6:59 AM Gonzalo Odiard godi...@sugarlabs.org wrote: I think was done to preserve space. Not sure if that is a concern now. Gonzalo On Sun, Mar 9, 2014 at 8:43 PM, me m...@jvonau.ca wrote: Hi All: I'm wondering if there is any reason why there are po files generated for the source in git, these are included as .mo files in the src rpm, but not shipped in the released rpms. Compare the list in git[1] and what becomes installed in the resulting rpm through ALL_LINGUAS=[2]. Is there any reason for this? Would it be worthwhile to ship all available translations? Jerry 1. https://github.com/sugarlabs/sugar/tree/master/po 2. https://github.com/sugarlabs/sugar/blob/master/configure.ac ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] shipped languages/locales
I believe AU makes their own build with en_GB. cjl On Wed, Mar 26, 2014 at 9:33 AM, Jerry Vonau m...@jvonau.ca wrote: Just wondering how AU is reacting without having the correct spelling for 'favourites', 'neighbourhood' that comes with en_BR. This is a regression from DX4 that included such support. It would be better would really support en_AU thou. just my thoughts, Jerry On March 26, 2014 at 6:59 AM Gonzalo Odiard godi...@sugarlabs.org wrote: I think was done to preserve space. Not sure if that is a concern now. Gonzalo On Sun, Mar 9, 2014 at 8:43 PM, me m...@jvonau.ca wrote: Hi All: I'm wondering if there is any reason why there are po files generated for the source in git, these are included as .mo files in the src rpm, but not shipped in the released rpms. Compare the list in git[1] and what becomes installed in the resulting rpm through ALL_LINGUAS=[2]. Is there any reason for this? Would it be worthwhile to ship all available translations? Jerry 1. https://github.com/sugarlabs/sugar/tree/master/po 2. https://github.com/sugarlabs/sugar/blob/master/configure.ac ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] shipped languages/locales
http://bugs.sugarlabs.org/ticket/4743 Jerry On March 26, 2014 at 8:48 AM Gonzalo Odiard godi...@sugarlabs.org wrote: Honestly, they didn't complained yet. Thanks for pointing that. Gonzalo On Wed, Mar 26, 2014 at 10:33 AM, Jerry Vonau m...@jvonau.ca wrote: Just wondering how AU is reacting without having the correct spelling for 'favourites', 'neighbourhood' that comes with en_BR. This is a regression from DX4 that included such support. It would be better would really support en_AU thou. just my thoughts, Jerry On March 26, 2014 at 6:59 AM Gonzalo Odiard godi...@sugarlabs.org wrote: I think was done to preserve space. Not sure if that is a concern now. Gonzalo On Sun, Mar 9, 2014 at 8:43 PM, me m...@jvonau.ca wrote: Hi All: I'm wondering if there is any reason why there are po files generated for the source in git, these are included as .mo files in the src rpm, but not shipped in the released rpms. Compare the list in git[1] and what becomes installed in the resulting rpm through ALL_LINGUAS=[2]. Is there any reason for this? Would it be worthwhile to ship all available translations? Jerry 1. https://github.com/sugarlabs/sugar/tree/master/po 2. https://github.com/sugarlabs/sugar/blob/master/configure.ac ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] shipped languages/locales
We included en_AU, but not en_GB. Will be in the next image. Gonzalo On Wed, Mar 26, 2014 at 10:59 AM, Chris Leonard cjlhomeaddr...@gmail.comwrote: I believe AU makes their own build with en_GB. cjl On Wed, Mar 26, 2014 at 9:33 AM, Jerry Vonau m...@jvonau.ca wrote: Just wondering how AU is reacting without having the correct spelling for 'favourites', 'neighbourhood' that comes with en_BR. This is a regression from DX4 that included such support. It would be better would really support en_AU thou. just my thoughts, Jerry On March 26, 2014 at 6:59 AM Gonzalo Odiard godi...@sugarlabs.org wrote: I think was done to preserve space. Not sure if that is a concern now. Gonzalo On Sun, Mar 9, 2014 at 8:43 PM, me m...@jvonau.ca wrote: Hi All: I'm wondering if there is any reason why there are po files generated for the source in git, these are included as .mo files in the src rpm, but not shipped in the released rpms. Compare the list in git[1] and what becomes installed in the resulting rpm through ALL_LINGUAS=[2]. Is there any reason for this? Would it be worthwhile to ship all available translations? Jerry 1. https://github.com/sugarlabs/sugar/tree/master/po 2. https://github.com/sugarlabs/sugar/blob/master/configure.ac ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] shipped languages/locales
They did when DX4 was used, not now. Jerry On March 26, 2014 at 8:59 AM Chris Leonard cjlhomeaddr...@gmail.com wrote: I believe AU makes their own build with en_GB. cjl On Wed, Mar 26, 2014 at 9:33 AM, Jerry Vonau m...@jvonau.ca wrote: Just wondering how AU is reacting without having the correct spelling for 'favourites', 'neighbourhood' that comes with en_BR. This is a regression from DX4 that included such support. It would be better would really support en_AU thou. just my thoughts, Jerry On March 26, 2014 at 6:59 AM Gonzalo Odiard godi...@sugarlabs.org wrote: I think was done to preserve space. Not sure if that is a concern now. Gonzalo On Sun, Mar 9, 2014 at 8:43 PM, me m...@jvonau.ca wrote: Hi All: I'm wondering if there is any reason why there are po files generated for the source in git, these are included as .mo files in the src rpm, but not shipped in the released rpms. Compare the list in git[1] and what becomes installed in the resulting rpm through ALL_LINGUAS=[2]. Is there any reason for this? Would it be worthwhile to ship all available translations? Jerry 1. https://github.com/sugarlabs/sugar/tree/master/po 2. https://github.com/sugarlabs/sugar/blob/master/configure.ac ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New method for Activity class to send notifications
Hi Martin, What about using this: https://developer.gnome.org/notification-spec/ ? I really think we should be moving towards FreeDesktop standards instead of rolling our own. Currently it would look like this, or you can add some syntax sugar to it: #!/usr/bin/python from gi.repository import Notify Notify.init (Hello world) Hello=Notify.Notification.new (Hello world,This is an example notification.,dialog-information) Hello.show () El mié, 26 de mar 2014 a las 7:40 AM, Martin Abente martin.abente.lah...@gmail.com escribió: Hello Everyone, We recently landed a messages notifications feature, based on Gary's designs [1]. One of our GCI 2013 hackers, Sam Parkinson, is has sent the bits to enable activities to send notifications too, as in Gary's design. His work is almost done [2,3,4], but it introduces a new method to the base Activity class, therefore I wanted your opinions regarding the name of this method, the current options are [4]: * send_notification * add_notification * shell_notify * sugar_notify Thanks for your time! tch. Refs: 1. http://wiki.sugarlabs.org/go/Design_Team/Proposals/Notifications 2. https://github.com/sugarlabs/sugar/pull/301 3. https://github.com/sugarlabs/sugar/pull/300 4. https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/114 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New method for Activity class to send notifications
Hello Sebastian, The notification back-end is already a subset of freedesktop notification definition. That is something we had in Sugar since a long time. We just added some other missing parts (displaying subject and body). But, for the front-end, If you look at Gary's design, you will see that is not the typical independent bubble UI component, as it groups notifications according to some context (ie., when is an activity). So, the motivation behind this method is (as you also suggest) to add some sugar syntax to facilitate its usage for activity developers. Having explained that, any recommendation for the name? :) Saludos! tch. On Wed, Mar 26, 2014 at 10:20 AM, Sebastian Silva sebast...@fuentelibre.org wrote: Hi Martin, What about using this: https://developer.gnome.org/notification-spec/ ? I really think we should be moving towards FreeDesktop standards instead of rolling our own. Currently it would look like this, or you can add some syntax sugar to it: #!/usr/bin/python from gi.repository import Notify Notify.init (Hello world) Hello=Notify.Notification.new (Hello world,This is an example notification.,dialog-information) Hello.show () El mié, 26 de mar 2014 a las 7:40 AM, Martin Abente martin.abente.lah...@gmail.com escribió: Hello Everyone, We recently landed a messages notifications feature, based on Gary's designs [1]. One of our GCI 2013 hackers, Sam Parkinson, is has sent the bits to enable activities to send notifications too, as in Gary's design. His work is almost done [2,3,4], but it introduces a new method to the base Activity class, therefore I wanted your opinions regarding the name of this method, the current options are [4]: * send_notification * add_notification * shell_notify * sugar_notify Thanks for your time! tch. Refs: 1. http://wiki.sugarlabs.org/go/Design_Team/Proposals/Notifications 2. https://github.com/sugarlabs/sugar/pull/301 3. https://github.com/sugarlabs/sugar/pull/300 4. https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/114 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] shipped languages/locales
That is strange, I don't see en_AU's translation file when extracting the files from the released rpm[1]. The src[2] rpm's tar file only lists en_GB and en_USA, but those are not in the released rpm and not en_AU at all. Jerry 1. http://harvest.one-education.org/public/au1b-updates/RPMS/sugar-0.100.1-10.olpcau.noarch.rpm 2. http://harvest.one-education.org/public/au1b-updates/SRPMS/sugar-0.100.1-10.olpcau.src.rpm On March 26, 2014 at 9:07 AM Gonzalo Odiard godi...@sugarlabs.org wrote: We included en_AU, but not en_GB. Will be in the next image. Gonzalo On Wed, Mar 26, 2014 at 10:59 AM, Chris Leonard cjlhomeaddr...@gmail.comwrote: I believe AU makes their own build with en_GB. cjl On Wed, Mar 26, 2014 at 9:33 AM, Jerry Vonau m...@jvonau.ca wrote: Just wondering how AU is reacting without having the correct spelling for 'favourites', 'neighbourhood' that comes with en_BR. This is a regression from DX4 that included such support. It would be better would really support en_AU thou. just my thoughts, Jerry On March 26, 2014 at 6:59 AM Gonzalo Odiard godi...@sugarlabs.org wrote: I think was done to preserve space. Not sure if that is a concern now. Gonzalo On Sun, Mar 9, 2014 at 8:43 PM, me m...@jvonau.ca wrote: Hi All: I'm wondering if there is any reason why there are po files generated for the source in git, these are included as .mo files in the src rpm, but not shipped in the released rpms. Compare the list in git[1] and what becomes installed in the resulting rpm through ALL_LINGUAS=[2]. Is there any reason for this? Would it be worthwhile to ship all available translations? Jerry 1. https://github.com/sugarlabs/sugar/tree/master/po 2. https://github.com/sugarlabs/sugar/blob/master/configure.ac ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] shipped languages/locales
There are not en_AU in http://translate.sugarlabs.org/ neither. Maybe was just en_GB? Gonzalo On Wed, Mar 26, 2014 at 1:10 PM, Jerry Vonau m...@jvonau.ca wrote: That is strange, I don't see en_AU's translation file when extracting the files from the released rpm[1]. The src[2] rpm's tar file only lists en_GB and en_USA, but those are not in the released rpm and not en_AU at all. Jerry 1. http://harvest.one-education.org/public/au1b-updates/RPMS/sugar-0.100.1-10.olpcau.noarch.rpm 2. http://harvest.one-education.org/public/au1b-updates/SRPMS/sugar-0.100.1-10.olpcau.src.rpm On March 26, 2014 at 9:07 AM Gonzalo Odiard godi...@sugarlabs.org wrote: We included en_AU, but not en_GB. Will be in the next image. Gonzalo On Wed, Mar 26, 2014 at 10:59 AM, Chris Leonard cjlhomeaddr...@gmail.comwrote: I believe AU makes their own build with en_GB. cjl On Wed, Mar 26, 2014 at 9:33 AM, Jerry Vonau m...@jvonau.ca wrote: Just wondering how AU is reacting without having the correct spelling for 'favourites', 'neighbourhood' that comes with en_BR. This is a regression from DX4 that included such support. It would be better would really support en_AU thou. just my thoughts, Jerry On March 26, 2014 at 6:59 AM Gonzalo Odiard godi...@sugarlabs.org wrote: I think was done to preserve space. Not sure if that is a concern now. Gonzalo On Sun, Mar 9, 2014 at 8:43 PM, me m...@jvonau.ca wrote: Hi All: I'm wondering if there is any reason why there are po files generated for the source in git, these are included as .mo files in the src rpm, but not shipped in the released rpms. Compare the list in git[1] and what becomes installed in the resulting rpm through ALL_LINGUAS=[2]. Is there any reason for this? Would it be worthwhile to ship all available translations? Jerry 1. https://github.com/sugarlabs/sugar/tree/master/po 2. https://github.com/sugarlabs/sugar/blob/master/configure.ac ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] shipped languages/locales
On Wed, Mar 26, 2014 at 7:59 AM, Gonzalo Odiard godi...@sugarlabs.orgwrote: I think was done to preserve space. Not sure if that is a concern now. Yep. It was definitely a concern for XO-1 and for XO-1.5 images for 2GB machines. m -- martin.langh...@gmail.com - ask interesting questions - don't get distracted with shiny stuff - working code first ~ http://docs.moodle.org/en/User:Martin_Langhoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] shipped languages/locales
We do not have an en_AU language project in Pootle, so that does not surprise me. On Wed, Mar 26, 2014 at 12:10 PM, Jerry Vonau m...@jvonau.ca wrote: That is strange, I don't see en_AU's translation file when extracting the files from the released rpm[1]. The src[2] rpm's tar file only lists en_GB and en_USA, but those are not in the released rpm and not en_AU at all. Jerry 1. http://harvest.one-education.org/public/au1b-updates/RPMS/sugar-0.100.1-10.olpcau.noarch.rpm 2. http://harvest.one-education.org/public/au1b-updates/SRPMS/sugar-0.100.1-10.olpcau.src.rpm On March 26, 2014 at 9:07 AM Gonzalo Odiard godi...@sugarlabs.org wrote: We included en_AU, but not en_GB. Will be in the next image. Gonzalo On Wed, Mar 26, 2014 at 10:59 AM, Chris Leonard cjlhomeaddr...@gmail.comwrote: I believe AU makes their own build with en_GB. cjl On Wed, Mar 26, 2014 at 9:33 AM, Jerry Vonau m...@jvonau.ca wrote: Just wondering how AU is reacting without having the correct spelling for 'favourites', 'neighbourhood' that comes with en_BR. This is a regression from DX4 that included such support. It would be better would really support en_AU thou. just my thoughts, Jerry On March 26, 2014 at 6:59 AM Gonzalo Odiard godi...@sugarlabs.org wrote: I think was done to preserve space. Not sure if that is a concern now. Gonzalo On Sun, Mar 9, 2014 at 8:43 PM, me m...@jvonau.ca wrote: Hi All: I'm wondering if there is any reason why there are po files generated for the source in git, these are included as .mo files in the src rpm, but not shipped in the released rpms. Compare the list in git[1] and what becomes installed in the resulting rpm through ALL_LINGUAS=[2]. Is there any reason for this? Would it be worthwhile to ship all available translations? Jerry 1. https://github.com/sugarlabs/sugar/tree/master/po 2. https://github.com/sugarlabs/sugar/blob/master/configure.ac ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] shipped languages/locales
I know there is no translations for en_AU in Pootle therefore not in sugar, but en_GB was used in the past as a substitute for this shortcoming. There are languages in Pootle that form the source tar file that becomes part of the source rpm, however the resulting installable rpm doesn't ship all the languages available from the source rpm. This thread started with the question should all the available translations from Pootle be shipped in the rpm, and that question still stands. Jerry On March 26, 2014 at 11:53 AM Chris Leonard cjlhomeaddr...@gmail.com wrote: We do not have an en_AU language project in Pootle, so that does not surprise me. On Wed, Mar 26, 2014 at 12:10 PM, Jerry Vonau m...@jvonau.ca wrote: That is strange, I don't see en_AU's translation file when extracting the files from the released rpm[1]. The src[2] rpm's tar file only lists en_GB and en_USA, but those are not in the released rpm and not en_AU at all. Jerry 1. http://harvest.one-education.org/public/au1b-updates/RPMS/sugar-0.100.1-10.olpcau.noarch.rpm 2. http://harvest.one-education.org/public/au1b-updates/SRPMS/sugar-0.100.1-10.olpcau.src.rpm On March 26, 2014 at 9:07 AM Gonzalo Odiard godi...@sugarlabs.org wrote: We included en_AU, but not en_GB. Will be in the next image. Gonzalo On Wed, Mar 26, 2014 at 10:59 AM, Chris Leonard cjlhomeaddr...@gmail.comwrote: I believe AU makes their own build with en_GB. cjl On Wed, Mar 26, 2014 at 9:33 AM, Jerry Vonau m...@jvonau.ca wrote: Just wondering how AU is reacting without having the correct spelling for 'favourites', 'neighbourhood' that comes with en_BR. This is a regression from DX4 that included such support. It would be better would really support en_AU thou. just my thoughts, Jerry On March 26, 2014 at 6:59 AM Gonzalo Odiard godi...@sugarlabs.org wrote: I think was done to preserve space. Not sure if that is a concern now. Gonzalo On Sun, Mar 9, 2014 at 8:43 PM, me m...@jvonau.ca wrote: Hi All: I'm wondering if there is any reason why there are po files generated for the source in git, these are included as .mo files in the src rpm, but not shipped in the released rpms. Compare the list in git[1] and what becomes installed in the resulting rpm through ALL_LINGUAS=[2]. Is there any reason for this? Would it be worthwhile to ship all available translations? Jerry 1. https://github.com/sugarlabs/sugar/tree/master/po 2. https://github.com/sugarlabs/sugar/blob/master/configure.ac ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New method for Activity class to send notifications
Sorry I hadn't read the proposal in detail. So if I understand correctly, if a regular X11 application emits a gi.repository.Notification, it will display correctly in Sugar? That's great, kudos on the work. Sebastian El mié, 26 de mar 2014 a las 10:21 AM, Martin Abente martin.abente.lah...@gmail.com escribió: Hello Sebastian, The notification back-end is already a subset of freedesktop notification definition. That is something we had in Sugar since a long time. We just added some other missing parts (displaying subject and body). But, for the front-end, If you look at Gary's design, you will see that is not the typical independent bubble UI component, as it groups notifications according to some context (ie., when is an activity). So, the motivation behind this method is (as you also suggest) to add some sugar syntax to facilitate its usage for activity developers. Having explained that, any recommendation for the name? :) Saludos! tch. On Wed, Mar 26, 2014 at 10:20 AM, Sebastian Silva sebast...@fuentelibre.org wrote: Hi Martin, What about using this: https://developer.gnome.org/notification-spec/ ? I really think we should be moving towards FreeDesktop standards instead of rolling our own. Currently it would look like this, or you can add some syntax sugar to it: #!/usr/bin/python from gi.repository import Notify Notify.init (Hello world) Hello=Notify.Notification.new (Hello world,This is an example notification.,dialog-information) Hello.show () El mié, 26 de mar 2014 a las 7:40 AM, Martin Abente martin.abente.lah...@gmail.com escribió: Hello Everyone, We recently landed a messages notifications feature, based on Gary's designs [1]. One of our GCI 2013 hackers, Sam Parkinson, is has sent the bits to enable activities to send notifications too, as in Gary's design. His work is almost done [2,3,4], but it introduces a new method to the base Activity class, therefore I wanted your opinions regarding the name of this method, the current options are [4]: * send_notification * add_notification * shell_notify * sugar_notify Thanks for your time! tch. Refs: 1. http://wiki.sugarlabs.org/go/Design_Team/Proposals/Notifications 2. https://github.com/sugarlabs/sugar/pull/301 3. https://github.com/sugarlabs/sugar/pull/300 4. https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/114 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] shipped languages/locales
Looks like we need a file po/LINGUAS Anybody have a idea about why we don't have one? Gonzalo On Wed, Mar 26, 2014 at 3:27 PM, Gonzalo Odiard godi...@sugarlabs.orgwrote: Maybe the reason is we don't have en_GB in the variable ALL_LINGUAS in the Makefile.in in sugar/po directory. In my system: * we have a file en_GB.po sugar-build/sugar/po/ * the file is not copied in sugar-build/build/out/install/share/locale/en_GB/LC_MESSAGES not sure how Makefile.in is created, here Makefile.in.in is a link to /usr/share/intltool/Makefile.in.in Gonzalo On Wed, Mar 26, 2014 at 2:17 PM, Jerry Vonau m...@jvonau.ca wrote: I know there is no translations for en_AU in Pootle therefore not in sugar, but en_GB was used in the past as a substitute for this shortcoming. There are languages in Pootle that form the source tar file that becomes part of the source rpm, however the resulting installable rpm doesn't ship all the languages available from the source rpm. This thread started with the question should all the available translations from Pootle be shipped in the rpm, and that question still stands. Jerry On March 26, 2014 at 11:53 AM Chris Leonard cjlhomeaddr...@gmail.com wrote: We do not have an en_AU language project in Pootle, so that does not surprise me. On Wed, Mar 26, 2014 at 12:10 PM, Jerry Vonau m...@jvonau.ca wrote: That is strange, I don't see en_AU's translation file when extracting the files from the released rpm[1]. The src[2] rpm's tar file only lists en_GB and en_USA, but those are not in the released rpm and not en_AU at all. Jerry 1. http://harvest.one-education.org/public/au1b-updates/RPMS/sugar-0.100.1-10.olpcau.noarch.rpm 2. http://harvest.one-education.org/public/au1b-updates/SRPMS/sugar-0.100.1-10.olpcau.src.rpm On March 26, 2014 at 9:07 AM Gonzalo Odiard godi...@sugarlabs.org wrote: We included en_AU, but not en_GB. Will be in the next image. Gonzalo On Wed, Mar 26, 2014 at 10:59 AM, Chris Leonard cjlhomeaddr...@gmail.comwrote: I believe AU makes their own build with en_GB. cjl On Wed, Mar 26, 2014 at 9:33 AM, Jerry Vonau m...@jvonau.ca wrote: Just wondering how AU is reacting without having the correct spelling for 'favourites', 'neighbourhood' that comes with en_BR. This is a regression from DX4 that included such support. It would be better would really support en_AU thou. just my thoughts, Jerry On March 26, 2014 at 6:59 AM Gonzalo Odiard godi...@sugarlabs.org wrote: I think was done to preserve space. Not sure if that is a concern now. Gonzalo On Sun, Mar 9, 2014 at 8:43 PM, me m...@jvonau.ca wrote: Hi All: I'm wondering if there is any reason why there are po files generated for the source in git, these are included as .mo files in the src rpm, but not shipped in the released rpms. Compare the list in git[1] and what becomes installed in the resulting rpm through ALL_LINGUAS=[2]. Is there any reason for this? Would it be worthwhile to ship all available translations? Jerry 1. https://github.com/sugarlabs/sugar/tree/master/po 2. https://github.com/sugarlabs/sugar/blob/master/configure.ac ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] shipped languages/locales
Maybe the reason is we don't have en_GB in the variable ALL_LINGUAS in the Makefile.in in sugar/po directory. In my system: * we have a file en_GB.po sugar-build/sugar/po/ * the file is not copied in sugar-build/build/out/install/share/locale/en_GB/LC_MESSAGES not sure how Makefile.in is created, here Makefile.in.in is a link to /usr/share/intltool/Makefile.in.in Gonzalo On Wed, Mar 26, 2014 at 2:17 PM, Jerry Vonau m...@jvonau.ca wrote: I know there is no translations for en_AU in Pootle therefore not in sugar, but en_GB was used in the past as a substitute for this shortcoming. There are languages in Pootle that form the source tar file that becomes part of the source rpm, however the resulting installable rpm doesn't ship all the languages available from the source rpm. This thread started with the question should all the available translations from Pootle be shipped in the rpm, and that question still stands. Jerry On March 26, 2014 at 11:53 AM Chris Leonard cjlhomeaddr...@gmail.com wrote: We do not have an en_AU language project in Pootle, so that does not surprise me. On Wed, Mar 26, 2014 at 12:10 PM, Jerry Vonau m...@jvonau.ca wrote: That is strange, I don't see en_AU's translation file when extracting the files from the released rpm[1]. The src[2] rpm's tar file only lists en_GB and en_USA, but those are not in the released rpm and not en_AU at all. Jerry 1. http://harvest.one-education.org/public/au1b-updates/RPMS/sugar-0.100.1-10.olpcau.noarch.rpm 2. http://harvest.one-education.org/public/au1b-updates/SRPMS/sugar-0.100.1-10.olpcau.src.rpm On March 26, 2014 at 9:07 AM Gonzalo Odiard godi...@sugarlabs.org wrote: We included en_AU, but not en_GB. Will be in the next image. Gonzalo On Wed, Mar 26, 2014 at 10:59 AM, Chris Leonard cjlhomeaddr...@gmail.comwrote: I believe AU makes their own build with en_GB. cjl On Wed, Mar 26, 2014 at 9:33 AM, Jerry Vonau m...@jvonau.ca wrote: Just wondering how AU is reacting without having the correct spelling for 'favourites', 'neighbourhood' that comes with en_BR. This is a regression from DX4 that included such support. It would be better would really support en_AU thou. just my thoughts, Jerry On March 26, 2014 at 6:59 AM Gonzalo Odiard godi...@sugarlabs.org wrote: I think was done to preserve space. Not sure if that is a concern now. Gonzalo On Sun, Mar 9, 2014 at 8:43 PM, me m...@jvonau.ca wrote: Hi All: I'm wondering if there is any reason why there are po files generated for the source in git, these are included as .mo files in the src rpm, but not shipped in the released rpms. Compare the list in git[1] and what becomes installed in the resulting rpm through ALL_LINGUAS=[2]. Is there any reason for this? Would it be worthwhile to ship all available translations? Jerry 1. https://github.com/sugarlabs/sugar/tree/master/po 2. https://github.com/sugarlabs/sugar/blob/master/configure.ac ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [Design] Develop activity
Hello Designers, I just ran the Develop activity the first time which opens multiple files. Something looked strange to me there about the tabs and their colors. As Gonzalo told me in IRC that we need to be consistent with the Browse activity regarding tabs and colors, I agree. But I had a bad user experience when I opened 2-3 files there, it took several seconds and several clicks to get to know which file was I viewing out of these 3. I mean, the tab which is open has a black color same as Browse activity( of tab name / file name) and those next to it are grey. As the other tabs remain grey and also the color behind an image in an image file is grey, looks grey as a whole making me feel that grey is highlighted and that grey file is opened. See here: http://202.164.53.122/~kamaljeet/sugar.png Here, it seems like the first file is open but actually it is the second one. So there is some problem with grabbing user's attention to the opened file. Although grey seems more eye catching and highlighted than black but IDK if it can be changed in Browse activity as well. IMO, either the opened file must be highlighted grey(I prefer this) or the color behind opened image should be changed or a third thing that we can do is changing the position of image(Text can be above and the image below). I just want you to look into the matter and take suitable action regarding good user experience. Thank you -- Kamaljeet Kaur kamalkaur188.wordpress.com ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New method for Activity class to send notifications
Hi, It is compatible with the dbus interface thing. But notifications with an app name of something like Chat activity will get a new icon in the frame. The function in the toolkit just sends a notification where the name is the activities id, which shows it under the activity button. Sam On Mar 27, 2014 4:21 AM, Sebastian Silva sebast...@fuentelibre.org wrote: Sorry I hadn't read the proposal in detail. So if I understand correctly, if a regular X11 application emits a gi.repository.Notification, it will display correctly in Sugar? That's great, kudos on the work. Sebastian El mié, 26 de mar 2014 a las 10:21 AM, Martin Abente martin.abente.lah...@gmail.com escribió: Hello Sebastian, The notification back-end is already a subset of freedesktop notification definition. That is something we had in Sugar since a long time. We just added some other missing parts (displaying subject and body). But, for the front-end, If you look at Gary's design, you will see that is not the typical independent bubble UI component, as it groups notifications according to some context (ie., when is an activity). So, the motivation behind this method is (as you also suggest) to add some sugar syntax to facilitate its usage for activity developers. Having explained that, any recommendation for the name? :) Saludos! tch. On Wed, Mar 26, 2014 at 10:20 AM, Sebastian Silva sebast...@fuentelibre.org wrote: Hi Martin, What about using this: https://developer.gnome.org/notification-spec/ ? I really think we should be moving towards FreeDesktop standards instead of rolling our own. Currently it would look like this, or you can add some syntax sugar to it: #!/usr/bin/python from gi.repository import Notify Notify.init (Hello world) Hello=Notify.Notification.new (Hello world,This is an example notification.,dialog-information) Hello.show () El mié, 26 de mar 2014 a las 7:40 AM, Martin Abente martin.abente.lah...@gmail.com escribió: Hello Everyone, We recently landed a messages notifications feature, based on Gary's designs [1]. One of our GCI 2013 hackers, Sam Parkinson, is has sent the bits to enable activities to send notifications too, as in Gary's design. His work is almost done [2,3,4], but it introduces a new method to the base Activity class, therefore I wanted your opinions regarding the name of this method, the current options are [4]: * send_notification * add_notification * shell_notify * sugar_notify Thanks for your time! tch. Refs: 1. http://wiki.sugarlabs.org/go/Design_Team/Proposals/Notifications 2. https://github.com/sugarlabs/sugar/pull/301 3. https://github.com/sugarlabs/sugar/pull/300 4. https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/114 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New method for Activity class to send notifications
On Wed, Mar 26, 2014 at 09:40:41AM -0300, Martin Abente wrote: His work is almost done [2,3,4], but it introduces a new method to the base Activity class, therefore I wanted your opinions regarding the name of this method, the current options are [4]: * send_notification * add_notification * shell_notify * sugar_notify shell_ and sugar_ prefixes are superfluous given that the base Activity class is already a part of Sugar, and the Shell isn't the eventual target of the notification; the user is. _notify and _notification are ambiguous, because they don't say what is being notified; the system, the class instance, or the user. add_ prefix exposes an implementation detail; that notifications are a list. This exposure is unnecessary. Of the ones you listed, send_notification fits best. Of the ones you didn't list, notify_user would be best. sugar_shell_add_notification_and_send_to_user would be the worst. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New method for Activity class to send notifications
sugar_shell_add_notification_and_send_to_user would be the worst. Maybe is a good name for a Java implementation :) -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New method for Activity class to send notifications
2014-03-26 18:12 GMT-03:00 James Cameron qu...@laptop.org: On Wed, Mar 26, 2014 at 09:40:41AM -0300, Martin Abente wrote: His work is almost done [2,3,4], but it introduces a new method to the base Activity class, therefore I wanted your opinions regarding the name of this method, the current options are [4]: * send_notification * add_notification * shell_notify * sugar_notify shell_ and sugar_ prefixes are superfluous given that the base Activity class is already a part of Sugar, and the Shell isn't the eventual target of the notification; the user is. _notify and _notification are ambiguous, because they don't say what is being notified; the system, the class instance, or the user. add_ prefix exposes an implementation detail; that notifications are a list. This exposure is unnecessary. Of the ones you listed, send_notification fits best. I agree. Thanks for the detailed comments on each proposal. Of the ones you didn't list, notify_user would be best. sugar_shell_add_notification_and_send_to_user would be the worst. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New method for Activity class to send notifications
notify_user sounds good to me :) On Wed, Mar 26, 2014 at 5:36 PM, Manuel Quiñones ma...@laptop.org wrote: 2014-03-26 18:12 GMT-03:00 James Cameron qu...@laptop.org: On Wed, Mar 26, 2014 at 09:40:41AM -0300, Martin Abente wrote: His work is almost done [2,3,4], but it introduces a new method to the base Activity class, therefore I wanted your opinions regarding the name of this method, the current options are [4]: * send_notification * add_notification * shell_notify * sugar_notify shell_ and sugar_ prefixes are superfluous given that the base Activity class is already a part of Sugar, and the Shell isn't the eventual target of the notification; the user is. _notify and _notification are ambiguous, because they don't say what is being notified; the system, the class instance, or the user. add_ prefix exposes an implementation detail; that notifications are a list. This exposure is unnecessary. Of the ones you listed, send_notification fits best. I agree. Thanks for the detailed comments on each proposal. Of the ones you didn't list, notify_user would be best. sugar_shell_add_notification_and_send_to_user would be the worst. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New method for Activity class to send notifications
2014-03-26 19:23 GMT-03:00 Martin Abente martin.abente.lah...@gmail.com: notify_user sounds good to me :) Same to me, notify_user fits best. I meant to add my comment below that one, sorry. On Wed, Mar 26, 2014 at 5:36 PM, Manuel Quiñones ma...@laptop.org wrote: 2014-03-26 18:12 GMT-03:00 James Cameron qu...@laptop.org: On Wed, Mar 26, 2014 at 09:40:41AM -0300, Martin Abente wrote: His work is almost done [2,3,4], but it introduces a new method to the base Activity class, therefore I wanted your opinions regarding the name of this method, the current options are [4]: * send_notification * add_notification * shell_notify * sugar_notify shell_ and sugar_ prefixes are superfluous given that the base Activity class is already a part of Sugar, and the Shell isn't the eventual target of the notification; the user is. _notify and _notification are ambiguous, because they don't say what is being notified; the system, the class instance, or the user. add_ prefix exposes an implementation detail; that notifications are a list. This exposure is unnecessary. Of the ones you listed, send_notification fits best. I agree. Thanks for the detailed comments on each proposal. Of the ones you didn't list, notify_user would be best. sugar_shell_add_notification_and_send_to_user would be the worst. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New method for Activity class to send notifications
On Wed, Mar 26, 2014 at 6:43 PM, Manuel Quiñones ma...@laptop.org wrote: 2014-03-26 19:23 GMT-03:00 Martin Abente martin.abente.lah...@gmail.com: notify_user sounds good to me :) +1 Same to me, notify_user fits best. I meant to add my comment below that one, sorry. On Wed, Mar 26, 2014 at 5:36 PM, Manuel Quiñones ma...@laptop.org wrote: 2014-03-26 18:12 GMT-03:00 James Cameron qu...@laptop.org: On Wed, Mar 26, 2014 at 09:40:41AM -0300, Martin Abente wrote: His work is almost done [2,3,4], but it introduces a new method to the base Activity class, therefore I wanted your opinions regarding the name of this method, the current options are [4]: * send_notification * add_notification * shell_notify * sugar_notify shell_ and sugar_ prefixes are superfluous given that the base Activity class is already a part of Sugar, and the Shell isn't the eventual target of the notification; the user is. _notify and _notification are ambiguous, because they don't say what is being notified; the system, the class instance, or the user. add_ prefix exposes an implementation detail; that notifications are a list. This exposure is unnecessary. Of the ones you listed, send_notification fits best. I agree. Thanks for the detailed comments on each proposal. Of the ones you didn't list, notify_user would be best. sugar_shell_add_notification_and_send_to_user would be the worst. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] shipped languages/locales
The hint was given in the initial email, alter ALL_LINGUAS= in /configure.ac Jerry On March 26, 2014 at 1:27 PM Gonzalo Odiard godi...@sugarlabs.org wrote: Maybe the reason is we don't have en_GB in the variable ALL_LINGUAS in the Makefile.in in sugar/po directory. In my system: * we have a file en_GB.po sugar-build/sugar/po/ * the file is not copied in sugar-build/build/out/install/share/locale/en_GB/LC_MESSAGES not sure how Makefile.in is created, here Makefile.in.in is a link to /usr/share/intltool/Makefile.in.in Gonzalo On Wed, Mar 26, 2014 at 2:17 PM, Jerry Vonau m...@jvonau.ca wrote: I know there is no translations for en_AU in Pootle therefore not in sugar, but en_GB was used in the past as a substitute for this shortcoming. There are languages in Pootle that form the source tar file that becomes part of the source rpm, however the resulting installable rpm doesn't ship all the languages available from the source rpm. This thread started with the question should all the available translations from Pootle be shipped in the rpm, and that question still stands. Jerry On March 26, 2014 at 11:53 AM Chris Leonard cjlhomeaddr...@gmail.com wrote: We do not have an en_AU language project in Pootle, so that does not surprise me. On Wed, Mar 26, 2014 at 12:10 PM, Jerry Vonau m...@jvonau.ca wrote: That is strange, I don't see en_AU's translation file when extracting the files from the released rpm[1]. The src[2] rpm's tar file only lists en_GB and en_USA, but those are not in the released rpm and not en_AU at all. Jerry 1. http://harvest.one-education.org/public/au1b-updates/RPMS/sugar-0.100.1-10.olpcau.noarch.rpm 2. http://harvest.one-education.org/public/au1b-updates/SRPMS/sugar-0.100.1-10.olpcau.src.rpm On March 26, 2014 at 9:07 AM Gonzalo Odiard godi...@sugarlabs.org wrote: We included en_AU, but not en_GB. Will be in the next image. Gonzalo On Wed, Mar 26, 2014 at 10:59 AM, Chris Leonard cjlhomeaddr...@gmail.comwrote: I believe AU makes their own build with en_GB. cjl On Wed, Mar 26, 2014 at 9:33 AM, Jerry Vonau m...@jvonau.ca wrote: Just wondering how AU is reacting without having the correct spelling for 'favourites', 'neighbourhood' that comes with en_BR. This is a regression from DX4 that included such support. It would be better would really support en_AU thou. just my thoughts, Jerry On March 26, 2014 at 6:59 AM Gonzalo Odiard godi...@sugarlabs.org wrote: I think was done to preserve space. Not sure if that is a concern now. Gonzalo On Sun, Mar 9, 2014 at 8:43 PM, me m...@jvonau.ca wrote: Hi All: I'm wondering if there is any reason why there are po files generated for the source in git, these are included as .mo files in the src rpm, but not shipped in the released rpms. Compare the list in git[1] and what becomes installed in the resulting rpm through ALL_LINGUAS=[2]. Is there any reason for this? Would it be worthwhile to ship all available translations? Jerry 1. https://github.com/sugarlabs/sugar/tree/master/po 2. https://github.com/sugarlabs/sugar/blob/master/configure.ac ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] shipped languages/locales
Yes, but is not a problem in the rpm, but in the sources repository. Gonzalo On Wed, Mar 26, 2014 at 8:15 PM, Jerry Vonau m...@jvonau.ca wrote: The hint was given in the initial email, alter ALL_LINGUAS= in /configure.ac Jerry On March 26, 2014 at 1:27 PM Gonzalo Odiard godi...@sugarlabs.org wrote: Maybe the reason is we don't have en_GB in the variable ALL_LINGUAS in the Makefile.in in sugar/po directory. In my system: * we have a file en_GB.po sugar-build/sugar/po/ * the file is not copied in sugar-build/build/out/install/share/locale/en_GB/LC_MESSAGES not sure how Makefile.in is created, here Makefile.in.in is a link to /usr/share/intltool/Makefile.in.in Gonzalo On Wed, Mar 26, 2014 at 2:17 PM, Jerry Vonau m...@jvonau.ca wrote: I know there is no translations for en_AU in Pootle therefore not in sugar, but en_GB was used in the past as a substitute for this shortcoming. There are languages in Pootle that form the source tar file that becomes part of the source rpm, however the resulting installable rpm doesn't ship all the languages available from the source rpm. This thread started with the question should all the available translations from Pootle be shipped in the rpm, and that question still stands. Jerry On March 26, 2014 at 11:53 AM Chris Leonard cjlhomeaddr...@gmail.com wrote: We do not have an en_AU language project in Pootle, so that does not surprise me. On Wed, Mar 26, 2014 at 12:10 PM, Jerry Vonau m...@jvonau.ca wrote: That is strange, I don't see en_AU's translation file when extracting the files from the released rpm[1]. The src[2] rpm's tar file only lists en_GB and en_USA, but those are not in the released rpm and not en_AU at all. Jerry 1. http://harvest.one-education.org/public/au1b-updates/RPMS/sugar-0.100.1-10.olpcau.noarch.rpm 2. http://harvest.one-education.org/public/au1b-updates/SRPMS/sugar-0.100.1-10.olpcau.src.rpm On March 26, 2014 at 9:07 AM Gonzalo Odiard godi...@sugarlabs.org wrote: We included en_AU, but not en_GB. Will be in the next image. Gonzalo On Wed, Mar 26, 2014 at 10:59 AM, Chris Leonard cjlhomeaddr...@gmail.comwrote: I believe AU makes their own build with en_GB. cjl On Wed, Mar 26, 2014 at 9:33 AM, Jerry Vonau m...@jvonau.ca wrote: Just wondering how AU is reacting without having the correct spelling for 'favourites', 'neighbourhood' that comes with en_BR. This is a regression from DX4 that included such support. It would be better would really support en_AU thou. just my thoughts, Jerry On March 26, 2014 at 6:59 AM Gonzalo Odiard godi...@sugarlabs.org wrote: I think was done to preserve space. Not sure if that is a concern now. Gonzalo On Sun, Mar 9, 2014 at 8:43 PM, me m...@jvonau.ca wrote: Hi All: I'm wondering if there is any reason why there are po files generated for the source in git, these are included as .mo files in the src rpm, but not shipped in the released rpms. Compare the list in git[1] and what becomes installed in the resulting rpm through ALL_LINGUAS=[2]. Is there any reason for this? Would it be worthwhile to ship all available translations? Jerry 1. https://github.com/sugarlabs/sugar/tree/master/po 2. https://github.com/sugarlabs/sugar/blob/master/configure.ac ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org
[Sugar-devel] Develop activity
Hi Could someone with the permissions please make the ASLO page for Develop http://activities.sugarlabs.org/en-US/sugar/addon/4058 have a home page link to http://wiki.sugarlabs.org/go/Activities/Develop Thanks Tony ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Develop activity
Ready! Please test. Regards! Alan Date: Thu, 27 Mar 2014 15:21:39 +1100 From: fors...@ozonline.com.au To: sugar-devel@lists.sugarlabs.org Subject: [Sugar-devel] Develop activity Hi Could someone with the permissions please make the ASLO page for Develop http://activities.sugarlabs.org/en-US/sugar/addon/4058 have a home page link to http://wiki.sugarlabs.org/go/Activities/Develop Thanks Tony ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Develop activity
The home page link works for me. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
