Re: [Sugar-devel] TamTamMini
David, I can't understand you. You talk a lot about how much you want participate, but then start attacking me. And now, you say: Hmmm. Flavio and others have been trying to send patches for years. They have been ignored so they fork. Look at the history of TamTam uploads: http://activities.sugarlabs.org/en-US/sugar/addons/versions/4061 I have uploaded the last version, previously alsroot and dirakx, (both employees of AC) were responsible of TamTam. In fact, I collaborated with both in the past, without problem. Then, do not try rewrite history, and don't try make me the bad maintainer, who only want to do his way. Gonzalo On Mon, Nov 18, 2013 at 10:52 PM, David Farning dfarn...@activitycentral.com wrote: On Mon, Nov 18, 2013 at 4:27 PM, Daniel Narvaez dwnarv...@gmail.com wrote: David, if you want to make a fair comparison, you need to take in account what was submitted! Hmmm. Flavio and others have been trying to send patches for years. They have been ignored so they fork. At which point upstream complains about how destructive it is when down streams fork. He took a play out of Lionel's book and submitted a completed product to the list for review and analysis of what it takes to maintain a set of activities for a large deployment. Try to submit six copies of the same codebase (instead of a patch) to any other free software project on heart. I bet our reaction will compare *very* favourably in friendliness. Seriously, stop thinking you are being treaten unfairly. You are not. This is about open source best practices. The goal is to highlight the difference a maintainer's attitude has on the tone of a discussion. We appreciate ActivityCentral effort to work upstream, just keep it up and give us a chance. Thank you. We will. In addition, I will continue to identify behaviors and practices which are detrimental to the project and the ecosystem. On 18 November 2013 23:07, David Farning dfarn...@activitycentral.com wrote: Did anyone else notice a difference in how this Activity and Pippy were handled? With pippy the maintainers quickly responded with Cool someone else wants to add value to the project. Here are my notes. Good luck. With TamTam the maintainer responded with My way or the highway. On Mon, Nov 18, 2013 at 7:39 AM, Daniel Narvaez dwnarv...@gmail.com wrote: Also note that we don't necessarily need to fix the code ourselves, good profiling data is often acted on by lower level libraries maintainers. The default strategy is to pretend it's higher level code fault of course, but issues can't be denied or ignored when proven by numbers and test cases :P On Monday, 18 November 2013, Daniel Narvaez wrote: And we can tackle lower level stuff... It's free and open code too! :) On Monday, 18 November 2013, Gonzalo Odiard wrote: There are some ow level stuff, but we can solve some problems in the activities too. You can see the other thread I started about performance. Also, dsd solved some of the problems related with the dynamic bindings. Gonzalo On Mon, Nov 18, 2013 at 9:52 AM, Sebastian Silva sebast...@fuentelibre.org wrote: El 17/11/13 12:58, Gonzalo Odiard escribió: I hope we can solve the performance problems then you don't need use a old Sugar version, to avoid all these problems. Well, I don't think it's likely you or me will be able to fix this one. It's lower level than Python and it looks to be by design of the lower level libraries. Note this mainly affects the XO1 which is already considered End Of Life. I think efforts are much more productive in trying to make the GNU+Sugar user experience excellent on Classmates and other netbooks. BTW, we are not the only ones affected. The entire LXDE desktop environment has decided to forego migrating to GTK3 and instead decided to port everything to QT. Here's a quote from the initial release of the QT file manager PCManFM [1]: I, however, need to admit that working with Qt/C++ is much more pleasant and productive than messing with C/GObject/GTK+. Since GTK+ 3 breaks backward compatibility a lot and it becomes more memory hungry and slower, I don’t see much advantage of GTK+ now. GTK+ 2 is lighter, but it’s no longer true for GTK+ 3. Ironically, fixing all of the broken compatibility is even harder than porting to Qt in some cases (PCManFM IMO is one of them). So If someone is starting a whole new project and is thinking about what GUI toolkit to use, personally I might recommend Qt if you’re not targeting Gnome 3. [1] http://blog.lxde.org/?p=990 -- Daniel Narvaez -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org
Re: [Sugar-devel] TamTamMini
Flavio, Ok, is not a patch, is a entire repository. Sadly, for me is impossible get from there what are the changes needed to make TamTam work in every hardware, or what changes are useful upstream. Is bad, because you worked a lot, and that is the only I wanted to say. Is nothing personal, just check how small are the patches I have sent this week, and how were reviewed in github. Gonzalo On Mon, Nov 18, 2013 at 8:02 PM, Flavio Danesse fdane...@activitycentral.com wrote: Sorry to put me back, but to bring a little clarity on TamTam: Do not say that the patch is huge because I never send a patch for this just to avoid giving this discussion which does not yield as well. If you look at my first mail on the subject I told him what I had done and posted where it was in case anyone wanted to look at, but never sent any patch. So, please do not complain about a patch that does not exist. I also said that because I never had previous patches approved on the same modifications to the application, which in each new version I had to return them. But anyway, my intention was to improve the application, not provoke discussions. I believe Nothing more TamTam theme, let the official repository as it is now and the end of the topic. 2013/11/18 Daniel Narvaez dwnarv...@gmail.com David, if you want to make a fair comparison, you need to take in account what was submitted! Try to submit six copies of the same codebase (instead of a patch) to any other free software project on heart. I bet our reaction will compare *very* favourably in friendliness. Seriously, stop thinking you are being treaten unfairly. You are not. We appreciate ActivityCentral effort to work upstream, just keep it up and give us a chance. On 18 November 2013 23:07, David Farning dfarn...@activitycentral.comwrote: Did anyone else notice a difference in how this Activity and Pippy were handled? With pippy the maintainers quickly responded with Cool someone else wants to add value to the project. Here are my notes. Good luck. With TamTam the maintainer responded with My way or the highway. On Mon, Nov 18, 2013 at 7:39 AM, Daniel Narvaez dwnarv...@gmail.com wrote: Also note that we don't necessarily need to fix the code ourselves, good profiling data is often acted on by lower level libraries maintainers. The default strategy is to pretend it's higher level code fault of course, but issues can't be denied or ignored when proven by numbers and test cases :P On Monday, 18 November 2013, Daniel Narvaez wrote: And we can tackle lower level stuff... It's free and open code too! :) On Monday, 18 November 2013, Gonzalo Odiard wrote: There are some ow level stuff, but we can solve some problems in the activities too. You can see the other thread I started about performance. Also, dsd solved some of the problems related with the dynamic bindings. Gonzalo On Mon, Nov 18, 2013 at 9:52 AM, Sebastian Silva sebast...@fuentelibre.org wrote: El 17/11/13 12:58, Gonzalo Odiard escribió: I hope we can solve the performance problems then you don't need use a old Sugar version, to avoid all these problems. Well, I don't think it's likely you or me will be able to fix this one. It's lower level than Python and it looks to be by design of the lower level libraries. Note this mainly affects the XO1 which is already considered End Of Life. I think efforts are much more productive in trying to make the GNU+Sugar user experience excellent on Classmates and other netbooks. BTW, we are not the only ones affected. The entire LXDE desktop environment has decided to forego migrating to GTK3 and instead decided to port everything to QT. Here's a quote from the initial release of the QT file manager PCManFM [1]: I, however, need to admit that working with Qt/C++ is much more pleasant and productive than messing with C/GObject/GTK+. Since GTK+ 3 breaks backward compatibility a lot and it becomes more memory hungry and slower, I don’t see much advantage of GTK+ now. GTK+ 2 is lighter, but it’s no longer true for GTK+ 3. Ironically, fixing all of the broken compatibility is even harder than porting to Qt in some cases (PCManFM IMO is one of them). So If someone is starting a whole new project and is thinking about what GUI toolkit to use, personally I might recommend Qt if you’re not targeting Gnome 3. [1] http://blog.lxde.org/?p=990 -- Daniel Narvaez -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- David Farning Activity Central: http://www.activitycentral.com -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
Sebastian, You are a editor in ASLO, can you upload the xo bundles if we coordinate the version numbers? Gonzalo On Sun, Nov 17, 2013 at 4:03 PM, Sebastian Silva sebast...@fuentelibre.orgwrote: El 17/11/13 13:20, Gonzalo Odiard escribió: Sebastian said he don't want make changes in the activities, only want add translation files, and package them in a xo file. Actually I was very specific in stating what I needed was to have updated .xo bundles in ASLO. Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
Date: Mon, 18 Nov 2013 06:56:25 -0500 From: sebast...@fuentelibre.org To: dwnarv...@gmail.com CC: fdane...@activitycentral.com; gonz...@laptop.org; cjlhomeaddr...@gmail.com; sugar-devel@lists.sugarlabs.org Subject: Re: [Sugar-devel] TamTamMini El 17/11/13 14:27, Daniel Narvaez escribió: I don't know how ASLO works... Is it possible to have multiple maintainers for each activity? Actually yes it's possible, but they are all labeled authors. One of these authors would have to add me. I can add you as author in any activity.The above list is that you need?? Looking over again, it was actually only 8 activities I had to fork in order to merge Quechua and Aymara translations: Chart Implode Jukebox Paint Read Terminal Write JigsawPuzzle Labyrinth ___ 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] TamTamMini
Alan, Should be good have a confirmation of the maintainers I can add Sebastian if we agree in the version numbers in the activities I maintain: Jukebox Paint Read Write Gonzalo On Mon, Nov 18, 2013 at 9:04 AM, Alan Jhonn Aguiar Schwyn alan...@hotmail.com wrote: Date: Mon, 18 Nov 2013 06:56:25 -0500 From: sebast...@fuentelibre.org To: dwnarv...@gmail.com CC: fdane...@activitycentral.com; gonz...@laptop.org; cjlhomeaddr...@gmail.com; sugar-devel@lists.sugarlabs.org Subject: Re: [Sugar-devel] TamTamMini El 17/11/13 14:27, Daniel Narvaez escribió: I don't know how ASLO works... Is it possible to have multiple maintainers for each activity? Actually yes it's possible, but they are all labeled authors. One of these authors would have to add me. I can add you as author in any activity. The above list is that you need?? Looking over again, it was actually only 8 activities I had to fork in order to merge Quechua and Aymara translations: Chart Implode Jukebox Paint Read Terminal Write JigsawPuzzle Labyrinth ___ 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] TamTamMini
El 18/11/13 06:02, Gonzalo Odiard escribió: Sebastian, You are a editor in ASLO, can you upload the xo bundles if we coordinate the version numbers? Gonzalo Gonzalo, Editors in ASLO only get to approve. It won't let us upload new bundles. Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
El 17/11/13 12:58, Gonzalo Odiard escribió: I hope we can solve the performance problems then you don't need use a old Sugar version, to avoid all these problems. Well, I don't think it's likely you or me will be able to fix this one. It's lower level than Python and it looks to be by design of the lower level libraries. Note this mainly affects the XO1 which is already considered End Of Life. I think efforts are much more productive in trying to make the GNU+Sugar user experience excellent on Classmates and other netbooks. BTW, we are not the only ones affected. The entire LXDE desktop environment has decided to forego migrating to GTK3 and instead decided to port everything to QT. Here's a quote from the initial release of the QT file manager PCManFM [1]: /I, however, need to admit that working with Qt/C++ is much more pleasant and productive than messing with C/GObject/GTK+.// //Since GTK+ 3 breaks backward compatibility a lot and it becomes more memory hungry and slower, I don't see much advantage of GTK+ now. GTK+ 2 is lighter, but it's no longer true for GTK+ 3. Ironically, fixing all of the broken compatibility is even harder than porting to Qt in some cases (PCManFM IMO is one of them).// //So If someone is starting a whole new project and is thinking about what GUI toolkit to use, personally I might recommend Qt if you're not targeting Gnome 3.// [1] /http://blog.lxde.org/?p=990 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
Ok. Can tell me what versions are you using right now of these activities? Jukebox Paint Read Write Gonzalo On Mon, Nov 18, 2013 at 9:46 AM, Sebastian Silva sebast...@fuentelibre.orgwrote: El 18/11/13 06:02, Gonzalo Odiard escribió: Sebastian, You are a editor in ASLO, can you upload the xo bundles if we coordinate the version numbers? Gonzalo Gonzalo, Editors in ASLO only get to approve. It won't let us upload new bundles. Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
Obviously it would not be ideal solution to be listed as author when all I did was merge .po files. But then again, author field in ASLO is not accurate at all, most of the time. You can find my bundles at: http://people.sugarlabs.org/icarito/activities/ Regards, Sebastian El 18/11/13 07:08, Gonzalo Odiard escribió: Alan, Should be good have a confirmation of the maintainers I can add Sebastian if we agree in the version numbers in the activities I maintain: Jukebox Paint Read Write Gonzalo On Mon, Nov 18, 2013 at 9:04 AM, Alan Jhonn Aguiar Schwyn alan...@hotmail.com mailto:alan...@hotmail.com wrote: (...) I can add you as author in any activity. The above list is that you need?? Looking over again, it was actually only 8 activities I had to fork in order to merge Quechua and Aymara translations: Chart Implode Jukebox Paint Read Terminal Write JigsawPuzzle Labyrinth ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org mailto: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] TamTamMini
There are some ow level stuff, but we can solve some problems in the activities too. You can see the other thread I started about performance. Also, dsd solved some of the problems related with the dynamic bindings. Gonzalo On Mon, Nov 18, 2013 at 9:52 AM, Sebastian Silva sebast...@fuentelibre.orgwrote: El 17/11/13 12:58, Gonzalo Odiard escribió: I hope we can solve the performance problems then you don't need use a old Sugar version, to avoid all these problems. Well, I don't think it's likely you or me will be able to fix this one. It's lower level than Python and it looks to be by design of the lower level libraries. Note this mainly affects the XO1 which is already considered End Of Life. I think efforts are much more productive in trying to make the GNU+Sugar user experience excellent on Classmates and other netbooks. BTW, we are not the only ones affected. The entire LXDE desktop environment has decided to forego migrating to GTK3 and instead decided to port everything to QT. Here's a quote from the initial release of the QT file manager PCManFM [1]: *I, however, need to admit that working with Qt/C++ is much more pleasant and productive than messing with C/GObject/GTK+.* *Since GTK+ 3 breaks backward compatibility a lot and it becomes more memory hungry and slower, I don’t see much advantage of GTK+ now. GTK+ 2 is lighter, but it’s no longer true for GTK+ 3. Ironically, fixing all of the broken compatibility is even harder than porting to Qt in some cases (PCManFM IMO is one of them).* *So If someone is starting a whole new project and is thinking about what GUI toolkit to use, personally I might recommend Qt if you’re not targeting Gnome 3.* * [1] *http://blog.lxde.org/?p=990 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
And we can tackle lower level stuff... It's free and open code too! :)
On Monday, 18 November 2013, Gonzalo Odiard wrote:
There are some ow level stuff, but we can solve some problems in the
activities too.
You can see the other thread I started about performance.
Also, dsd solved some of the problems related with the dynamic bindings.
Gonzalo
On Mon, Nov 18, 2013 at 9:52 AM, Sebastian Silva
sebast...@fuentelibre.org javascript:_e({}, 'cvml',
'sebast...@fuentelibre.org'); wrote:
El 17/11/13 12:58, Gonzalo Odiard escribió:
I hope we can solve the performance problems then you don't need use a
old Sugar version,
to avoid all these problems.
Well, I don't think it's likely you or me will be able to fix this one.
It's lower level than Python
and it looks to be by design of the lower level libraries.
Note this mainly affects the XO1 which is already considered End Of Life.
I think efforts are
much more productive in trying to make the GNU+Sugar user experience
excellent on
Classmates and other netbooks.
BTW, we are not the only ones affected. The entire LXDE desktop
environment has decided
to forego migrating to GTK3 and instead decided to port everything to QT.
Here's a quote from the initial release of the QT file manager PCManFM
[1]:
*I, however, need to admit that working with Qt/C++ is much more
pleasant and productive than messing with C/GObject/GTK+.*
*Since GTK+ 3 breaks backward compatibility a lot and it becomes more
memory hungry and slower, I don’t see much advantage of GTK+ now. GTK+ 2 is
lighter, but it’s no longer true for GTK+ 3. Ironically, fixing all of the
broken compatibility is even harder than porting to Qt in some cases
(PCManFM IMO is one of them).*
*So If someone is starting a whole new project and is thinking about what
GUI toolkit to use, personally I might recommend Qt if you’re not targeting
Gnome 3.*
* [1] *http://blog.lxde.org/?p=990
--
Daniel Narvaez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
Also note that we don't necessarily need to fix the code ourselves, good profiling data is often acted on by lower level libraries maintainers. The default strategy is to pretend it's higher level code fault of course, but issues can't be denied or ignored when proven by numbers and test cases :P On Monday, 18 November 2013, Daniel Narvaez wrote: And we can tackle lower level stuff... It's free and open code too! :) On Monday, 18 November 2013, Gonzalo Odiard wrote: There are some ow level stuff, but we can solve some problems in the activities too. You can see the other thread I started about performance. Also, dsd solved some of the problems related with the dynamic bindings. Gonzalo On Mon, Nov 18, 2013 at 9:52 AM, Sebastian Silva sebast...@fuentelibre.org wrote: El 17/11/13 12:58, Gonzalo Odiard escribió: I hope we can solve the performance problems then you don't need use a old Sugar version, to avoid all these problems. Well, I don't think it's likely you or me will be able to fix this one. It's lower level than Python and it looks to be by design of the lower level libraries. Note this mainly affects the XO1 which is already considered End Of Life. I think efforts are much more productive in trying to make the GNU+Sugar user experience excellent on Classmates and other netbooks. BTW, we are not the only ones affected. The entire LXDE desktop environment has decided to forego migrating to GTK3 and instead decided to port everything to QT. Here's a quote from the initial release of the QT file manager PCManFM [1]: *I, however, need to admit that working with Qt/C++ is much more pleasant and productive than messing with C/GObject/GTK+.* *Since GTK+ 3 breaks backward compatibility a lot and it becomes more memory hungry and slower, I don’t see much advantage of GTK+ now. GTK+ 2 is lighter, but it’s no longer true for GTK+ 3. Ironically, fixing all of the broken compatibility is even harder than porting to Qt in some cases (PCManFM IMO is one of them).* *So If someone is starting a whole new project and is thinking about what GUI toolkit to use, personally I might recommend Qt if you’re not targeting Gnome 3.* * [1] *http://blog.lxde.org/?p=990 -- Daniel Narvaez -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
Did anyone else notice a difference in how this Activity and Pippy were handled? With pippy the maintainers quickly responded with Cool someone else wants to add value to the project. Here are my notes. Good luck. With TamTam the maintainer responded with My way or the highway. On Mon, Nov 18, 2013 at 7:39 AM, Daniel Narvaez dwnarv...@gmail.com wrote: Also note that we don't necessarily need to fix the code ourselves, good profiling data is often acted on by lower level libraries maintainers. The default strategy is to pretend it's higher level code fault of course, but issues can't be denied or ignored when proven by numbers and test cases :P On Monday, 18 November 2013, Daniel Narvaez wrote: And we can tackle lower level stuff... It's free and open code too! :) On Monday, 18 November 2013, Gonzalo Odiard wrote: There are some ow level stuff, but we can solve some problems in the activities too. You can see the other thread I started about performance. Also, dsd solved some of the problems related with the dynamic bindings. Gonzalo On Mon, Nov 18, 2013 at 9:52 AM, Sebastian Silva sebast...@fuentelibre.org wrote: El 17/11/13 12:58, Gonzalo Odiard escribió: I hope we can solve the performance problems then you don't need use a old Sugar version, to avoid all these problems. Well, I don't think it's likely you or me will be able to fix this one. It's lower level than Python and it looks to be by design of the lower level libraries. Note this mainly affects the XO1 which is already considered End Of Life. I think efforts are much more productive in trying to make the GNU+Sugar user experience excellent on Classmates and other netbooks. BTW, we are not the only ones affected. The entire LXDE desktop environment has decided to forego migrating to GTK3 and instead decided to port everything to QT. Here's a quote from the initial release of the QT file manager PCManFM [1]: I, however, need to admit that working with Qt/C++ is much more pleasant and productive than messing with C/GObject/GTK+. Since GTK+ 3 breaks backward compatibility a lot and it becomes more memory hungry and slower, I don’t see much advantage of GTK+ now. GTK+ 2 is lighter, but it’s no longer true for GTK+ 3. Ironically, fixing all of the broken compatibility is even harder than porting to Qt in some cases (PCManFM IMO is one of them). So If someone is starting a whole new project and is thinking about what GUI toolkit to use, personally I might recommend Qt if you’re not targeting Gnome 3. [1] http://blog.lxde.org/?p=990 -- Daniel Narvaez -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- David Farning Activity Central: http://www.activitycentral.com ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
On Mon, Nov 18, 2013 at 5:07 PM, David Farning dfarn...@activitycentral.com wrote: Did anyone else notice a difference in how this Activity and Pippy were handled? With pippy the maintainers quickly responded with Cool someone else wants to add value to the project. Here are my notes. Good luck. With TamTam the maintainer responded with My way or the highway. On Mon, Nov 18, 2013 at 7:39 AM, Daniel Narvaez dwnarv...@gmail.com wrote: Also note that we don't necessarily need to fix the code ourselves, good profiling data is often acted on by lower level libraries maintainers. The default strategy is to pretend it's higher level code fault of course, but issues can't be denied or ignored when proven by numbers and test cases :P On Monday, 18 November 2013, Daniel Narvaez wrote: And we can tackle lower level stuff... It's free and open code too! :) On Monday, 18 November 2013, Gonzalo Odiard wrote: There are some ow level stuff, but we can solve some problems in the activities too. You can see the other thread I started about performance. Also, dsd solved some of the problems related with the dynamic bindings. Gonzalo On Mon, Nov 18, 2013 at 9:52 AM, Sebastian Silva sebast...@fuentelibre.org wrote: El 17/11/13 12:58, Gonzalo Odiard escribió: I hope we can solve the performance problems then you don't need use a old Sugar version, to avoid all these problems. Well, I don't think it's likely you or me will be able to fix this one. It's lower level than Python and it looks to be by design of the lower level libraries. Note this mainly affects the XO1 which is already considered End Of Life. I think efforts are much more productive in trying to make the GNU+Sugar user experience excellent on Classmates and other netbooks. BTW, we are not the only ones affected. The entire LXDE desktop environment has decided to forego migrating to GTK3 and instead decided to port everything to QT. Here's a quote from the initial release of the QT file manager PCManFM [1]: I, however, need to admit that working with Qt/C++ is much more pleasant and productive than messing with C/GObject/GTK+. Since GTK+ 3 breaks backward compatibility a lot and it becomes more memory hungry and slower, I don’t see much advantage of GTK+ now. GTK+ 2 is lighter, but it’s no longer true for GTK+ 3. Ironically, fixing all of the broken compatibility is even harder than porting to Qt in some cases (PCManFM IMO is one of them). So If someone is starting a whole new project and is thinking about what GUI toolkit to use, personally I might recommend Qt if you’re not targeting Gnome 3. [1] http://blog.lxde.org/?p=990 -- Daniel Narvaez -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- David Farning Activity Central: http://www.activitycentral.com ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel With all due respect David, that is not a fair description of what happened and you are also comparing apples and oranges. In the case of TamTam, there is an active maintainer and the patch was huge. In the case of Pippy, there is no active maintainer and the patch was literally 2 characters. The difference of opinion on TamTam is technical, not personal. Let's try to keep it that way by not inflaming the situation. regards. -walter -- 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] TamTamMini
David, if you want to make a fair comparison, you need to take in account what was submitted! Try to submit six copies of the same codebase (instead of a patch) to any other free software project on heart. I bet our reaction will compare *very* favourably in friendliness. Seriously, stop thinking you are being treaten unfairly. You are not. We appreciate ActivityCentral effort to work upstream, just keep it up and give us a chance. On 18 November 2013 23:07, David Farning dfarn...@activitycentral.comwrote: Did anyone else notice a difference in how this Activity and Pippy were handled? With pippy the maintainers quickly responded with Cool someone else wants to add value to the project. Here are my notes. Good luck. With TamTam the maintainer responded with My way or the highway. On Mon, Nov 18, 2013 at 7:39 AM, Daniel Narvaez dwnarv...@gmail.com wrote: Also note that we don't necessarily need to fix the code ourselves, good profiling data is often acted on by lower level libraries maintainers. The default strategy is to pretend it's higher level code fault of course, but issues can't be denied or ignored when proven by numbers and test cases :P On Monday, 18 November 2013, Daniel Narvaez wrote: And we can tackle lower level stuff... It's free and open code too! :) On Monday, 18 November 2013, Gonzalo Odiard wrote: There are some ow level stuff, but we can solve some problems in the activities too. You can see the other thread I started about performance. Also, dsd solved some of the problems related with the dynamic bindings. Gonzalo On Mon, Nov 18, 2013 at 9:52 AM, Sebastian Silva sebast...@fuentelibre.org wrote: El 17/11/13 12:58, Gonzalo Odiard escribió: I hope we can solve the performance problems then you don't need use a old Sugar version, to avoid all these problems. Well, I don't think it's likely you or me will be able to fix this one. It's lower level than Python and it looks to be by design of the lower level libraries. Note this mainly affects the XO1 which is already considered End Of Life. I think efforts are much more productive in trying to make the GNU+Sugar user experience excellent on Classmates and other netbooks. BTW, we are not the only ones affected. The entire LXDE desktop environment has decided to forego migrating to GTK3 and instead decided to port everything to QT. Here's a quote from the initial release of the QT file manager PCManFM [1]: I, however, need to admit that working with Qt/C++ is much more pleasant and productive than messing with C/GObject/GTK+. Since GTK+ 3 breaks backward compatibility a lot and it becomes more memory hungry and slower, I don’t see much advantage of GTK+ now. GTK+ 2 is lighter, but it’s no longer true for GTK+ 3. Ironically, fixing all of the broken compatibility is even harder than porting to Qt in some cases (PCManFM IMO is one of them). So If someone is starting a whole new project and is thinking about what GUI toolkit to use, personally I might recommend Qt if you’re not targeting Gnome 3. [1] http://blog.lxde.org/?p=990 -- Daniel Narvaez -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- David Farning Activity Central: http://www.activitycentral.com -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
Sorry to put me back, but to bring a little clarity on TamTam: Do not say that the patch is huge because I never send a patch for this just to avoid giving this discussion which does not yield as well. If you look at my first mail on the subject I told him what I had done and posted where it was in case anyone wanted to look at, but never sent any patch. So, please do not complain about a patch that does not exist. I also said that because I never had previous patches approved on the same modifications to the application, which in each new version I had to return them. But anyway, my intention was to improve the application, not provoke discussions. I believe Nothing more TamTam theme, let the official repository as it is now and the end of the topic. 2013/11/18 Daniel Narvaez dwnarv...@gmail.com David, if you want to make a fair comparison, you need to take in account what was submitted! Try to submit six copies of the same codebase (instead of a patch) to any other free software project on heart. I bet our reaction will compare *very* favourably in friendliness. Seriously, stop thinking you are being treaten unfairly. You are not. We appreciate ActivityCentral effort to work upstream, just keep it up and give us a chance. On 18 November 2013 23:07, David Farning dfarn...@activitycentral.comwrote: Did anyone else notice a difference in how this Activity and Pippy were handled? With pippy the maintainers quickly responded with Cool someone else wants to add value to the project. Here are my notes. Good luck. With TamTam the maintainer responded with My way or the highway. On Mon, Nov 18, 2013 at 7:39 AM, Daniel Narvaez dwnarv...@gmail.com wrote: Also note that we don't necessarily need to fix the code ourselves, good profiling data is often acted on by lower level libraries maintainers. The default strategy is to pretend it's higher level code fault of course, but issues can't be denied or ignored when proven by numbers and test cases :P On Monday, 18 November 2013, Daniel Narvaez wrote: And we can tackle lower level stuff... It's free and open code too! :) On Monday, 18 November 2013, Gonzalo Odiard wrote: There are some ow level stuff, but we can solve some problems in the activities too. You can see the other thread I started about performance. Also, dsd solved some of the problems related with the dynamic bindings. Gonzalo On Mon, Nov 18, 2013 at 9:52 AM, Sebastian Silva sebast...@fuentelibre.org wrote: El 17/11/13 12:58, Gonzalo Odiard escribió: I hope we can solve the performance problems then you don't need use a old Sugar version, to avoid all these problems. Well, I don't think it's likely you or me will be able to fix this one. It's lower level than Python and it looks to be by design of the lower level libraries. Note this mainly affects the XO1 which is already considered End Of Life. I think efforts are much more productive in trying to make the GNU+Sugar user experience excellent on Classmates and other netbooks. BTW, we are not the only ones affected. The entire LXDE desktop environment has decided to forego migrating to GTK3 and instead decided to port everything to QT. Here's a quote from the initial release of the QT file manager PCManFM [1]: I, however, need to admit that working with Qt/C++ is much more pleasant and productive than messing with C/GObject/GTK+. Since GTK+ 3 breaks backward compatibility a lot and it becomes more memory hungry and slower, I don’t see much advantage of GTK+ now. GTK+ 2 is lighter, but it’s no longer true for GTK+ 3. Ironically, fixing all of the broken compatibility is even harder than porting to Qt in some cases (PCManFM IMO is one of them). So If someone is starting a whole new project and is thinking about what GUI toolkit to use, personally I might recommend Qt if you’re not targeting Gnome 3. [1] http://blog.lxde.org/?p=990 -- Daniel Narvaez -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- David Farning Activity Central: http://www.activitycentral.com -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
Hi Flavio, On 19 November 2013 00:02, Flavio Danesse fdane...@activitycentral.comwrote: Sorry to put me back, but to bring a little clarity on TamTam: Do not say that the patch is huge because I never send a patch for this just to avoid giving this discussion which does not yield as well. If you look at my first mail on the subject I told him what I had done and posted where it was in case anyone wanted to look at, but never sent any patch. So, please do not complain about a patch that does not exist. I and Walter was answering to David which comparing your contribution to the Pippy patch, implied it was of the same kind. *Your* position is very clear to me. The only part I don't understand is why you are not trying to contribute patches upstream rather than maintaining your own fork. I'm sorry to ask you again about that but really I wish your contributions made it upstream! I also said that because I never had previous patches approved on the same modifications to the application, which in each new version I had to return them. I'm not sure I'm fully understanding you here. Are you saying you tried to submit patches in the past and they was refused? Was they ignored? ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
On Mon, Nov 18, 2013 at 4:27 PM, Daniel Narvaez dwnarv...@gmail.com wrote: David, if you want to make a fair comparison, you need to take in account what was submitted! Hmmm. Flavio and others have been trying to send patches for years. They have been ignored so they fork. At which point upstream complains about how destructive it is when down streams fork. He took a play out of Lionel's book and submitted a completed product to the list for review and analysis of what it takes to maintain a set of activities for a large deployment. Try to submit six copies of the same codebase (instead of a patch) to any other free software project on heart. I bet our reaction will compare *very* favourably in friendliness. Seriously, stop thinking you are being treaten unfairly. You are not. This is about open source best practices. The goal is to highlight the difference a maintainer's attitude has on the tone of a discussion. We appreciate ActivityCentral effort to work upstream, just keep it up and give us a chance. Thank you. We will. In addition, I will continue to identify behaviors and practices which are detrimental to the project and the ecosystem. On 18 November 2013 23:07, David Farning dfarn...@activitycentral.com wrote: Did anyone else notice a difference in how this Activity and Pippy were handled? With pippy the maintainers quickly responded with Cool someone else wants to add value to the project. Here are my notes. Good luck. With TamTam the maintainer responded with My way or the highway. On Mon, Nov 18, 2013 at 7:39 AM, Daniel Narvaez dwnarv...@gmail.com wrote: Also note that we don't necessarily need to fix the code ourselves, good profiling data is often acted on by lower level libraries maintainers. The default strategy is to pretend it's higher level code fault of course, but issues can't be denied or ignored when proven by numbers and test cases :P On Monday, 18 November 2013, Daniel Narvaez wrote: And we can tackle lower level stuff... It's free and open code too! :) On Monday, 18 November 2013, Gonzalo Odiard wrote: There are some ow level stuff, but we can solve some problems in the activities too. You can see the other thread I started about performance. Also, dsd solved some of the problems related with the dynamic bindings. Gonzalo On Mon, Nov 18, 2013 at 9:52 AM, Sebastian Silva sebast...@fuentelibre.org wrote: El 17/11/13 12:58, Gonzalo Odiard escribió: I hope we can solve the performance problems then you don't need use a old Sugar version, to avoid all these problems. Well, I don't think it's likely you or me will be able to fix this one. It's lower level than Python and it looks to be by design of the lower level libraries. Note this mainly affects the XO1 which is already considered End Of Life. I think efforts are much more productive in trying to make the GNU+Sugar user experience excellent on Classmates and other netbooks. BTW, we are not the only ones affected. The entire LXDE desktop environment has decided to forego migrating to GTK3 and instead decided to port everything to QT. Here's a quote from the initial release of the QT file manager PCManFM [1]: I, however, need to admit that working with Qt/C++ is much more pleasant and productive than messing with C/GObject/GTK+. Since GTK+ 3 breaks backward compatibility a lot and it becomes more memory hungry and slower, I don’t see much advantage of GTK+ now. GTK+ 2 is lighter, but it’s no longer true for GTK+ 3. Ironically, fixing all of the broken compatibility is even harder than porting to Qt in some cases (PCManFM IMO is one of them). So If someone is starting a whole new project and is thinking about what GUI toolkit to use, personally I might recommend Qt if you’re not targeting Gnome 3. [1] http://blog.lxde.org/?p=990 -- Daniel Narvaez -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- David Farning Activity Central: http://www.activitycentral.com -- Daniel Narvaez -- David Farning Activity Central: http://www.activitycentral.com ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
On 19 November 2013 02:52, David Farning dfarn...@activitycentral.comwrote: Seriously, stop thinking you are being treaten unfairly. You are not. This is about open source best practices. The goal is to highlight the difference a maintainer's attitude has on the tone of a discussion. Try to go beyhond the tone and look at the concrete points that has been raised. They are all technically very valid. I don't like Linus-style tones, and I have not seen anything like that here, but that has peen proven to be a successfull open source practice too :) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
The trouble with tone is that it involves subjective detection, and is prone to bias and error during the process. -- 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] TamTamMini
In Flavio's defense, I'd like to restructure this conversation. Undoubtedly, he's put great effort in this work. From a deployment's point of view, it's a contribution. From Gonzalo's POV, it's a burden because Flavio hasn't taken up learning to master Git. From Localizer's POV it's a burden because, in their view, it implies double the strings. These are representatives up upstream. In my humble opinion, the situation is out of balance. We cannot dismiss contributions merely because people have not learnt all the tools. This also goes for localization team, because really, from a friendly fork's POV, doing a simple msgmerge command imports all of the necessary translations from upstream (or the other way around). In any case, the amount of user visible strings in TamTamMini is negligible. I spent the last month trying to get mantainers to respond to requests to update GTK2 branches with translations, with barely any response except Manuq and Gonzalo, and only the first actually took action on my request. Really, things could be simpler for downstream, especially Activity-wise. Sugar per se is a different matter because luckily, we have Daniel Narvaez, but who knows how long he'll put up with us. The Sugar Network's proposed workflow is that anybody can upload a bundle. It is not mandatory that everything has to be just right. I would encourage Flavio, who has already offered, to mantain a fork of TamTamMini with his changes, in git, and either create a new Activity Id and name for it or we can see about the new features in Sugar Network/ASLO that will enable non-mantainer uploads. For the case where alternative implementations of the same activity exist, by default the system will offer the one from the original author. If the activity really works better, perhaps we will even include it in Hexoquinasa, our downstream of Platform Team's Deployment Platform, built for Perú. Love for TamTam Suite really is welcome from this side of the island. Regards, Sebastian El 17/11/13 12:12, Chris Leonard escribió: On Sat, Nov 16, 2013 at 6:50 PM, Flavio Danesse fdane...@activitycentral.com wrote: On the issue of separating the application from the rest of the suite, I did because it was the only way to understand it, correct the code and port it to gtk3. The code of the suite is filled with errors and unused files. Now, this application is much easier to maintain and extend. The same applies to the translation patch, most not used by TamTamMini. The TamTam Suite was set up to use a common set of translations on purpose. Some time ago, they were all completely separate and it was a big burden on localizers to repeat the translation work multiple times. Free and open discussion between developers and localization stakeholders arrived at the current configuration. As the maintainer of Pootle, I am not excited about seeing this collaborative agreement undone and I will need some convincing on the need for splitting the suite before hosting a fork of your TamTamMini in Pootle. We need more open discussion, and less forking to move together as a community. cjl Sugar Labs Translation Team Coordinator ___ 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] TamTamMini
El 17/11/13 12:38, Sebastian Silva escribió: I spent the last month trying to get mantainers to respond to requests to update GTK2 branches with translations, with barely any response except Manuq and Gonzalo, and only the first actually took action on my request. BTW, in our latest public release ([1] v129) I had to fork 18 out of 26 included activities for this reason. [1] http://pe.sugarlabs.org/ir/Proyecto%20Piloto%20Hexoquinasa/Instalar#Descarga The Sugar Network's proposed workflow is that anybody can upload a bundle. It is not mandatory that everything has to be just right. I would encourage Flavio, who has already offered, to mantain a fork of TamTamMini with his changes, in git, and either create a new Activity Id and name for it or we can see about the new features in Sugar Network/ASLO that will enable non-mantainer uploads. For the case where alternative implementations of the same activity exist, by default the system will offer the one from the original author. Therefore it was decided to design this workflow. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
On Sun, Nov 17, 2013 at 12:38 PM, Sebastian Silva sebast...@fuentelibre.org wrote: In Flavio's defense, I'd like to restructure this conversation. Undoubtedly, he's put great effort in this work. And there are mechanisms for incorporating that work for the benefit of all. From a deployment's point of view, it's a contribution. I would think deployments would rather have contributions upstreamed so they do not incur maintenance costs long term. From Gonzalo's POV, it's a burden because Flavio hasn't taken up learning to master Git. Mastering certain elements of git are essential to contribute to a pre-existing longstanding core element of Sugar like TamTam. From Localizer's POV it's a burden because, in their view, it implies double the strings. These are representatives up upstream. Localizers are not upstream representatives, they are downstream collaborators using a common upstream infrastructure. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
Sebastian, I think you are not understanding the problem. Of course, anybody can fork and upload another activity, but that is nightmare on the long run, to maintainers and to users. Imagine how good for users will be have different versions of the activities, some running, some not, depending of different situations. You say From Gonzalo's POV, it's a burden because Flavio hasn't taken up learning to master Git. That is not the problem. The problem is invest a lot of work in one activity without even trying to communicate with the maintainer and agree in a way to solve the different problems. By example: the activity need changes to run in a Magallanes, then what is the best option? is that solution good for other activities? need be solved in the activity or in the toolkit? Is the best option maintain activities forked? If you ask me, I don't know, probably talking with Flavio, can understand better the problem/s and find a solution, but without communication, is impossible. Gonzalo On Sun, Nov 17, 2013 at 2:38 PM, Sebastian Silva sebast...@fuentelibre.orgwrote: In Flavio's defense, I'd like to restructure this conversation. Undoubtedly, he's put great effort in this work. From a deployment's point of view, it's a contribution. From Gonzalo's POV, it's a burden because Flavio hasn't taken up learning to master Git. From Localizer's POV it's a burden because, in their view, it implies double the strings. These are representatives up upstream. In my humble opinion, the situation is out of balance. We cannot dismiss contributions merely because people have not learnt all the tools. This also goes for localization team, because really, from a friendly fork's POV, doing a simple msgmerge command imports all of the necessary translations from upstream (or the other way around). In any case, the amount of user visible strings in TamTamMini is negligible. I spent the last month trying to get mantainers to respond to requests to update GTK2 branches with translations, with barely any response except Manuq and Gonzalo, and only the first actually took action on my request. Really, things could be simpler for downstream, especially Activity-wise. Sugar per se is a different matter because luckily, we have Daniel Narvaez, but who knows how long he'll put up with us. The Sugar Network's proposed workflow is that anybody can upload a bundle. It is not mandatory that everything has to be just right. I would encourage Flavio, who has already offered, to mantain a fork of TamTamMini with his changes, in git, and either create a new Activity Id and name for it or we can see about the new features in Sugar Network/ASLO that will enable non-mantainer uploads. For the case where alternative implementations of the same activity exist, by default the system will offer the one from the original author. If the activity really works better, perhaps we will even include it in Hexoquinasa, our downstream of Platform Team's Deployment Platform, built for Perú. Love for TamTam Suite really is welcome from this side of the island. Regards, Sebastian El 17/11/13 12:12, Chris Leonard escribió: On Sat, Nov 16, 2013 at 6:50 PM, Flavio Danesse fdane...@activitycentral.com wrote: On the issue of separating the application from the rest of the suite, I did because it was the only way to understand it, correct the code and port it to gtk3. The code of the suite is filled with errors and unused files. Now, this application is much easier to maintain and extend. The same applies to the translation patch, most not used by TamTamMini. The TamTam Suite was set up to use a common set of translations on purpose. Some time ago, they were all completely separate and it was a big burden on localizers to repeat the translation work multiple times. Free and open discussion between developers and localization stakeholders arrived at the current configuration. As the maintainer of Pootle, I am not excited about seeing this collaborative agreement undone and I will need some convincing on the need for splitting the suite before hosting a fork of your TamTamMini in Pootle. We need more open discussion, and less forking to move together as a community. cjl Sugar Labs Translation Team Coordinator ___ 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] TamTamMini
On Sun, Nov 17, 2013 at 2:46 PM, Sebastian Silva sebast...@fuentelibre.orgwrote: El 17/11/13 12:38, Sebastian Silva escribió: I spent the last month trying to get mantainers to respond to requests to update GTK2 branches with translations, with barely any response except Manuq and Gonzalo, and only the first actually took action on my request. I requested you clone the repositories. In your case, you only want add translations. BTW, in our latest public release ([1] v129) I had to fork 18 out of 26 included activities for this reason. I hope we can solve the performance problems then you don't need use a old Sugar version, to avoid all these problems. Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
On 17 November 2013 18:38, Sebastian Silva sebast...@fuentelibre.orgwrote: In Flavio's defense, I'd like to restructure this conversation. Undoubtedly, he's put great effort in this work. I suspect it's a great contribution, which is exactly why I'm mad it's not going upstream... In my humble opinion, the situation is out of balance. We cannot dismiss contributions merely because people have not learnt all the tools. This also goes for localization team, I don't think we are dismissing contributions at all here. The way I read the conversation is Gonzalo: As we already discussed, this is not a good way to submit contributions. You should do this and that. Flavio: Yes, I know this is not a good way, that's why I didn't post patches. On the other hand, why I don't just take maintenance of the module over? I suspect Gonzalo didn't take this too badly because he didn't write TamTam. But in most free software project this behaviour would have been seen as insulting to the maintainer. Gonzalo offered to work with Flavio to get his work submitted properly. I hope Flavio takes that offer, showing it was all just a misunderstanding. Happy to help out with that btw if needed, I know Gonzalo is busy I spent the last month trying to get mantainers to respond to requests to update GTK2 branches with translations, with barely any response except Manuq and Gonzalo, and only the first actually took action on my request. I think the two issues are very different, in this case the maintainer was super responsive. Are you willing to do the work if you are given access to the repositories? ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
On 17 November 2013 18:58, Gonzalo Odiard gonz...@laptop.org wrote: On Sun, Nov 17, 2013 at 2:46 PM, Sebastian Silva sebast...@fuentelibre.org wrote: El 17/11/13 12:38, Sebastian Silva escribió: I spent the last month trying to get mantainers to respond to requests to update GTK2 branches with translations, with barely any response except Manuq and Gonzalo, and only the first actually took action on my request. I requested you clone the repositories. In your case, you only want add translations. Why fork if Sebastian is willing to do it in the official repositories? It seems like it won't give you any extra work and possiblity be useful to other people. I probably want gtk2 to disappear even more than you. Despite that I think we should take people contributions on old branches, if they are willing to do the work. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
On Sun, Nov 17, 2013 at 3:17 PM, Daniel Narvaez dwnarv...@gmail.com wrote: On 17 November 2013 18:58, Gonzalo Odiard gonz...@laptop.org wrote: On Sun, Nov 17, 2013 at 2:46 PM, Sebastian Silva sebast...@fuentelibre.org wrote: El 17/11/13 12:38, Sebastian Silva escribió: I spent the last month trying to get mantainers to respond to requests to update GTK2 branches with translations, with barely any response except Manuq and Gonzalo, and only the first actually took action on my request. I requested you clone the repositories. In your case, you only want add translations. Why fork if Sebastian is willing to do it in the official repositories? It seems like it won't give you any extra work and possiblity be useful to other people. I probably want gtk2 to disappear even more than you. Despite that I think we should take people contributions on old branches, if they are willing to do the work. Like I see it, is not a fork. Sebastian said he don't want make changes in the activities, only want add translation files, and package them in a xo file. Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
On 17 November 2013 19:20, Gonzalo Odiard gonz...@laptop.org wrote: Like I see it, is not a fork. Sebastian said he don't want make changes in the activities, only want add translation files, and package them in a xo file. If someone needs to package gtk2 activities, how they will know they should be using Sebastian repository instead of the official one? That's why I call it a fork. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
El 17/11/13 13:12, Daniel Narvaez escribió: I spent the last month trying to get mantainers to respond to requests to update GTK2 branches with translations, with barely any response except Manuq and Gonzalo, and only the first actually took action on my request. I think the two issues are very different, in this case the maintainer was super responsive. Are you willing to do the work if you are given access to the repositories? Absolutely. My issue was not just access to the repositories but the ability to put these in ASLO. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
El 17/11/13 13:20, Gonzalo Odiard escribió: Sebastian said he don't want make changes in the activities, only want add translation files, and package them in a xo file. Actually I was very specific in stating what I needed was to have updated .xo bundles in ASLO. Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
On 17 November 2013 20:02, Sebastian Silva sebast...@fuentelibre.orgwrote: El 17/11/13 13:12, Daniel Narvaez escribió: I spent the last month trying to get mantainers to respond to requests to update GTK2 branches with translations, with barely any response except Manuq and Gonzalo, and only the first actually took action on my request. I think the two issues are very different, in this case the maintainer was super responsive. Are you willing to do the work if you are given access to the repositories? Absolutely. My issue was not just access to the repositories but the ability to put these in ASLO. I don't know how ASLO works... Is it possible to have multiple maintainers for each activity? ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
On Fri, Nov 15, 2013 at 6:02 PM, Flavio Danesse fdane...@activitycentral.com wrote: I wanted to inform maintainers TamTam : These last few days I've added a little love to TamTamMini. This is an application that has been added Ceibal instruments and small arrangements over the years, but for various reasons, changes were never implemented in the official repository, so that at the launch of each version, I was obliged back to modify the application to meet the specifications of Ceibal. To not have to continue with that methodology, I spent several days to fix, clean and improve implementation. The work done was as follows: Over the past couple of weeks, I have asked some hard questions about the future of Sugar. Lionel responded with an awesome and inspirational web activities prototype. In addition to that type of innovation, I allege that additional deployment feedback is necessary to make sure that what we offer is what deployments need. This work by Flavio exemplifies those needs. TamTamMini separated from other Suite applications, deleting files that were not used. I deleted the images were not used or those that were not necessary. Corrected, I simplified and cleaned up the code. As a result , the application occupies least 5 mb. I ported the application to gtk3 . The update process can take months and even years for large deployments. As a result critical activities must run, have a consistent look and feel, and be validated across both Gtk2 and Gtk3. I built separate versions for xo gtk2 and gtk3 1.0 , x 1.5 , x 1.75 and one for Magalães. Each version contains the corrections necessary for proper operation as both gtk gtk3 for each particular machine. Deployments often run several types of hardware. As a result activities must run, have a consistent look and feel, and be validated across each type of hardware in use by the deployment. The becomes tricky as activities bypass the API provided by Sugar and interact directly with low level libraries. All versions were tested in each of the aforementioned machines and all functioning properly. It only remains to make some very minor repairs on gtk3 versions . I wish that the maintainers of the repository with TamTam saw all this content for the purpose of seeing whether it is possible to unify into a single repository TamTamMini . The challenge becomes what to do when the work like this does not fit the priorities of the activity maintainer. Link: https://github.com/fdanesse/TamTamMini ___ Team mailing list t...@lists.activitycentral.com http://lists.activitycentral.com/listinfo/team -- David Farning Activity Central: http://www.activitycentral.com ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
On 16 November 2013 10:23, David Farning dfarn...@activitycentral.comwrote: TamTamMini separated from other Suite applications, deleting files that were not used. I deleted the images were not used or those that were not necessary. Corrected, I simplified and cleaned up the code. As a result , the application occupies least 5 mb. I ported the application to gtk3 . The update process can take months and even years for large deployments. As a result critical activities must run, have a consistent look and feel, and be validated across both Gtk2 and Gtk3. At the cost of being blamed to ignore deployment needs... I don't think supporting both toolkits like that is realistically sustainable. That said, I understand where this is coming from, it's just a really bad situation to be in. Let's try to support it as well as we can but at the same time, let's do whatever we can to move deployments to gtk3 as soon as possible. I built separate versions for xo gtk2 and gtk3 1.0 , x 1.5 , x 1.75 and one for Magalães. Each version contains the corrections necessary for proper operation as both gtk gtk3 for each particular machine. Deployments often run several types of hardware. As a result activities must run, have a consistent look and feel, and be validated across each type of hardware in use by the deployment. The becomes tricky as activities bypass the API provided by Sugar and interact directly with low level libraries. I'm not sure what was the issue with TamTam exactly, but I'd hope hardware related incompatibilities to be relatively rare, assuming a recent software. If not, we must fix that :) All versions were tested in each of the aforementioned machines and all functioning properly. It only remains to make some very minor repairs on gtk3 versions . I wish that the maintainers of the repository with TamTam saw all this content for the purpose of seeing whether it is possible to unify into a single repository TamTamMini . The challenge becomes what to do when the work like this does not fit the priorities of the activity maintainer. In this community, if the maintainer is too busy to deal with patches like this, I suspect he would be more than willing to accept co-maintainers. That's assuming the maintainer is at all resposive. If not, I'd say maintainership could be just taken over. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
Can you explain why you needed to create a separate activity for each type of hardware? On 16 November 2013 01:02, Flavio Danesse fdane...@activitycentral.comwrote: *I wanted to inform maintainers TamTam :* These last few days I've added a little love to TamTamMini. This is an application that has been added Ceibal instruments and small arrangements over the years, but for various reasons, changes were never implemented in the official repository, so that at the launch of each version, I was obliged back to modify the application to meet the specifications of Ceibal. To not have to continue with that methodology, I spent several days to fix, clean and improve implementation. *The work done was as follows:* - TamTamMini separated from other Suite applications, deleting files that were not used. - I deleted the images were not used or those that were not necessary. - Corrected, I simplified and cleaned up the code. As a result , the application occupies least 5 mb. - I ported the application to gtk3 . - I built separate versions for xo gtk2 and gtk3 1.0 , x 1.5 , x 1.75 and one for Magalães. Each version contains the corrections necessary for proper operation as both gtk gtk3 for each particular machine. All versions were tested in each of the aforementioned machines and all functioning properly. It only remains to make some very minor repairs on gtk3 versions . I wish that the maintainers of the repository with TamTam saw all this content for the purpose of seeing whether it is possible to unify into a single repository TamTamMini . Link: https://github.com/fdanesse/TamTamMini ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TamTamMini
Hi Flavio, I am maintaining TamTam suite right now. While I appreciate your work, you are doing it again difficult for a maintainer work with you. I have talked about this in other opportunities, then you already know it. You have decided important changes without trying to ask the opinion of the maintainer, and sent a giant change with all the work already done, then for me is only a option of take all, or nothing. There are many things I would do in a different way: * Tamtam Mini port to gtk3 was already started. Needed a lot more work, but the activity run. * Is really difficult maintain different versions for every machine. * The TamTam suite was in a single repository because by example have a big number of strings to translate, and we avoid needing multiply the translators work. * The patches yiu sent are huge. Ask to any other maintainer, and will say the same. You are putting me in a really difficult situation, this is not the way to work together. Gonzalo On Fri, Nov 15, 2013 at 9:02 PM, Flavio Danesse fdane...@activitycentral.com wrote: *I wanted to inform maintainers TamTam :* These last few days I've added a little love to TamTamMini. This is an application that has been added Ceibal instruments and small arrangements over the years, but for various reasons, changes were never implemented in the official repository, so that at the launch of each version, I was obliged back to modify the application to meet the specifications of Ceibal. To not have to continue with that methodology, I spent several days to fix, clean and improve implementation. *The work done was as follows:* - TamTamMini separated from other Suite applications, deleting files that were not used. - I deleted the images were not used or those that were not necessary. - Corrected, I simplified and cleaned up the code. As a result , the application occupies least 5 mb. - I ported the application to gtk3 . - I built separate versions for xo gtk2 and gtk3 1.0 , x 1.5 , x 1.75 and one for Magalães. Each version contains the corrections necessary for proper operation as both gtk gtk3 for each particular machine. All versions were tested in each of the aforementioned machines and all functioning properly. It only remains to make some very minor repairs on gtk3 versions . I wish that the maintainers of the repository with TamTam saw all this content for the purpose of seeing whether it is possible to unify into a single repository TamTamMini . Link: https://github.com/fdanesse/TamTamMini ___ 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] TamTamMini
I am aware of the problem, why not send any patch . But it seemed important to inform the work I did in case the application mantiners somehow wanted to use it as this is the version that is used on all machines of Ceibal after passing the Activity Central testing makes before entering the applications in distribution image dextrose . On the other hand, for me it is a problem if the changes I make do not apply in the official repository in each new version I have to re-do the same thing again, so I decided to make this particular repository as I had to repeat the work several times. On the issue of separating the application from the rest of the suite, I did because it was the only way to understand it, correct the code and port it to gtk3. The code of the suite is filled with errors and unused files. Now, this application is much easier to maintain and extend. The same applies to the translation patch, most not used by TamTamMini. On the other hand, may be easier for you if I am in charge of maintaining the application. 2013/11/16 Gonzalo Odiard gonz...@laptop.org Hi Flavio, I am maintaining TamTam suite right now. While I appreciate your work, you are doing it again difficult for a maintainer work with you. I have talked about this in other opportunities, then you already know it. You have decided important changes without trying to ask the opinion of the maintainer, and sent a giant change with all the work already done, then for me is only a option of take all, or nothing. There are many things I would do in a different way: * Tamtam Mini port to gtk3 was already started. Needed a lot more work, but the activity run. * Is really difficult maintain different versions for every machine. * The TamTam suite was in a single repository because by example have a big number of strings to translate, and we avoid needing multiply the translators work. * The patches yiu sent are huge. Ask to any other maintainer, and will say the same. You are putting me in a really difficult situation, this is not the way to work together. Gonzalo On Fri, Nov 15, 2013 at 9:02 PM, Flavio Danesse fdane...@activitycentral.com wrote: *I wanted to inform maintainers TamTam :* These last few days I've added a little love to TamTamMini. This is an application that has been added Ceibal instruments and small arrangements over the years, but for various reasons, changes were never implemented in the official repository, so that at the launch of each version, I was obliged back to modify the application to meet the specifications of Ceibal. To not have to continue with that methodology, I spent several days to fix, clean and improve implementation. *The work done was as follows:* - TamTamMini separated from other Suite applications, deleting files that were not used. - I deleted the images were not used or those that were not necessary. - Corrected, I simplified and cleaned up the code. As a result , the application occupies least 5 mb. - I ported the application to gtk3 . - I built separate versions for xo gtk2 and gtk3 1.0 , x 1.5 , x 1.75 and one for Magalães. Each version contains the corrections necessary for proper operation as both gtk gtk3 for each particular machine. All versions were tested in each of the aforementioned machines and all functioning properly. It only remains to make some very minor repairs on gtk3 versions . I wish that the maintainers of the repository with TamTam saw all this content for the purpose of seeing whether it is possible to unify into a single repository TamTamMini . Link: https://github.com/fdanesse/TamTamMini ___ 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] TamTamMini
On Sat, Nov 16, 2013 at 8:50 PM, Flavio Danesse fdane...@activitycentral.com wrote: I am aware of the problem, why not send any patch . But it seemed important to inform the work I did in case the application mantiners somehow wanted to use it as this is the version that is used on all machines of Ceibal after passing the Activity Central testing makes before entering the applications in distribution image dextrose . On the other hand, for me it is a problem if the changes I make do not apply in the official repository in each new version I have to re-do the same thing again, so I decided to make this particular repository as I had to repeat the work several times. You need understand is really difficult for me get what are the changes you are doing and why are needed, in all the changes you are doing in the repository. On the issue of separating the application from the rest of the suite, I did because it was the only way to understand it, correct the code and port it to gtk3. The code of the suite is filled with errors and unused files. Now, this application is much easier to maintain and extend. The same applies to the translation patch, most not used by TamTamMini. But this have other problems. If you want, we can talk and see what is the way to move forward, but surely is not make changes without talking before. On the other hand, may be easier for you if I am in charge of maintaining the application. This is what I am talking of all or nothing :/ Gonzalo 2013/11/16 Gonzalo Odiard gonz...@laptop.org Hi Flavio, I am maintaining TamTam suite right now. While I appreciate your work, you are doing it again difficult for a maintainer work with you. I have talked about this in other opportunities, then you already know it. You have decided important changes without trying to ask the opinion of the maintainer, and sent a giant change with all the work already done, then for me is only a option of take all, or nothing. There are many things I would do in a different way: * Tamtam Mini port to gtk3 was already started. Needed a lot more work, but the activity run. * Is really difficult maintain different versions for every machine. * The TamTam suite was in a single repository because by example have a big number of strings to translate, and we avoid needing multiply the translators work. * The patches yiu sent are huge. Ask to any other maintainer, and will say the same. You are putting me in a really difficult situation, this is not the way to work together. Gonzalo On Fri, Nov 15, 2013 at 9:02 PM, Flavio Danesse fdane...@activitycentral.com wrote: *I wanted to inform maintainers TamTam :* These last few days I've added a little love to TamTamMini. This is an application that has been added Ceibal instruments and small arrangements over the years, but for various reasons, changes were never implemented in the official repository, so that at the launch of each version, I was obliged back to modify the application to meet the specifications of Ceibal. To not have to continue with that methodology, I spent several days to fix, clean and improve implementation. *The work done was as follows:* - TamTamMini separated from other Suite applications, deleting files that were not used. - I deleted the images were not used or those that were not necessary. - Corrected, I simplified and cleaned up the code. As a result , the application occupies least 5 mb. - I ported the application to gtk3 . - I built separate versions for xo gtk2 and gtk3 1.0 , x 1.5 , x 1.75 and one for Magalães. Each version contains the corrections necessary for proper operation as both gtk gtk3 for each particular machine. All versions were tested in each of the aforementioned machines and all functioning properly. It only remains to make some very minor repairs on gtk3 versions . I wish that the maintainers of the repository with TamTam saw all this content for the purpose of seeing whether it is possible to unify into a single repository TamTamMini . Link: https://github.com/fdanesse/TamTamMini ___ 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] tamtammini-57.xo, csound and ubuntu
Hi Jonas! Not yet. Well, i reported the problems to a friend who is doing package maintainance for debian. I thought he could sort the problem and give advice for further actions. Unfortunately i didn't hear back from him. Furthermore i posted the log file in the ubuntu forums: http://ubuntuforums.org/showthread.php?t=1716997 - no reaction .. but i guess it's more a user centered plattform. Next saturday i give a presentation at a linux event. Maybe i find somebody who is interested in solving the thing. Btw: i could offer a iso image of the whole system to be booted via DVD or USB-stick. Maybe this could also be help. Sofar, thanks for replies. Andrea * Jonas Smedegaard d...@jones.dk [2011-04-02 15:33]: Hi Andrea, On Fri, Apr 01, 2011 at 11:13:41AM +0200, Andrea Mayr wrote: Two years ago i tried so hard to get it running (on debian), but failed. Did you ever try report to Debian the problems you encountered? - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private ___ 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] tamtammini-57.xo, csound and ubuntu
Hi Andrea, On Fri, Apr 01, 2011 at 11:13:41AM +0200, Andrea Mayr wrote: Two years ago i tried so hard to get it running (on debian), but failed. Did you ever try report to Debian the problems you encountered? - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] tamtammini-57.xo, csound and ubuntu
Hello Andrea, Yes this is the correct place to ask. I have the exact same problem on my machine with Trisquel 10.04. I've looked and there isnt a bug report so I made one: http://bugs.sugarlabs.org/ticket/2744 I've put you on CC so you get news on it. Thanks for the report! El 01/04/11 04:13, Andrea Mayr escribió: Problem: TamTammini starts within sugar on ubuntu. When clicking on an instrument you hear the sound you get when clicking a button (sound is working, i.e Speak.activity is working fine), but you don't hear the instrument. Also the keyboard gives no sounds. insert_score_event(): invalid instrument number or name ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] tamtammini-57.xo, csound and ubuntu
As a Csound user (but except for Sugar, lacking Linux experience), I can
perhaps be of some help.
The problem is shown by these lines:
insert_score_event(): invalid instrument number or name
insert_score_event(): invalid instrument number or name
insert_score_event(): invalid instrument number or name
insert_score_event(): invalid instrument number or name
insert_score_event(): invalid instrument number or name
insert_score_event(): invalid instrument number or name
insert_score_event(): invalid instrument number or name
insert_score_event(): invalid instrument number or name
insert_score_event(): invalid instrument number or name
insert_score_event(): invalid instrument number or name
insert_score_event(): invalid instrument number or name
insert_score_event(): invalid instrument number or name
Clearly, the orchestra has been compiled correctly. The score is the
problem. Score events are obviously being inserted in real time as you press
keys. As each score event is initiated, it looks for its designated
instrument name or number and doesn't find it in the orchestra; so it gives
a click and cancels the event. Offhand, it looks like the activity has a
name communication problem; either that, or the necessary instruments
aren't being generated in the orchestra (although there is no indication of
that).
Other than that, there are a very large number of (gtk) deprecation warnings
indicated. Could this indicate python-related version incompatibilites?
Others with more expertise than I should address this possibility.
Art Hunkins
- Original Message -
From: Andrea Mayr andrea.m...@netbridge.at
To: sugar-devel@lists.sugarlabs.org
Sent: Friday, April 01, 2011 5:13 AM
Subject: [Sugar-devel] tamtammini-57.xo, csound and ubuntu
Hi!
I am putting together an Ubuntu based Live-System for Kids from 6
to 12 years. I am exited that sugar is available as a package for
installation within Ubuntu now. Two years ago i tried so hard to
get it running (on debian), but failed. Most of the activities
are now running without problems after installing them with
sugar-install-bundle. But still i have a problem with TamTammini,
which is one of the essential programs for the paedagogical
approach of our setup. Maybe somebody could have a look at my
logfile. A friend tried it on a debian system and had similar
problems. Should i direct my questions to another place? I am
very thankful for advice and help.
Andrea
System is: Ubuntu 10.10.. Sugar 0.88.1, Csound version 5.12,
tamtammini-57.xo
Problem: TamTammini starts within sugar on ubuntu. When clicking
on an instrument you hear the sound you get when clicking a
button (sound is working, i.e Speak.activity is working fine),
but you don't hear the instrument. Also the keyboard gives no
sounds.
Log file:
** Message: pygobject_register_sinkfunc is deprecated
(HippoCanvasBox)
1301392836.158145 DEBUG root: Debug Level 0
1301392836.158415 DEBUG root: INFO: loaded
TAMTAM_ROOT=/home/jux/Activities/TamTamMini.activity
1301392836.214454 DEBUG root: skip
/home/jux/Activities/TamTamMini.activity/common/Util/Clooper/linux64_511_deb
blobs: /home/jux/Activities/Tam
TamMini.activity/common/Util/Clooper/linux64_511_deb/aclient.so:
falsche ELF-Klasse: ELFCLASS64
1301392836.216862 DEBUG root: skip
/home/jux/Activities/TamTamMini.activity/common/Util/Clooper/linux64_510
blobs: /home/jux/Activities/TamTamM
ini.activity/common/Util/Clooper/linux64_510/aclient.so: falsche
ELF-Klasse: ELFCLASS64
1301392836.218069 DEBUG root: skip
/home/jux/Activities/TamTamMini.activity/common/Util/Clooper/linux32_508
blobs: libcsound.so.5.1: Kann die S
hared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht
gefunden
1301392836.226332 DEBUG root: use
/home/jux/Activities/TamTamMini.activity/common/Util/Clooper/linux32_511_deb
blobs
1301392836.293436 DEBUG root: datastore.get
1301392836.298367 WARNING root: .has_key() is deprecated, use
'in'
1301392836.303999 DEBUG root: *** Act
fe6faa0ce02bb0dce54e1510cf9c965b80cde2b4, mesh instance None,
scope private
1301392836.326327 DEBUG root: PaletteWindow.popdown immediate
True
1301392836.335281 DEBUG root: PaletteWindow.popdown immediate
True
1301392836.340254 WARNING root: No gtk.AccelGroup in the top
level window.
1301392836.344155 WARNING root: No gtk.AccelGroup in the top
level window.
/usr/lib/python2.6/dist-packages/sugar/graphics/window.py:290:
DeprecationWarning: use toolbar_box instead of toolbox
warnings.warn('use toolbar_box instead of toolbox',
DeprecationWarning)
Logging disabled on purpose
PortMIDI real time MIDI plugin for Csound
virtual_keyboard real time MIDI plugin for Csound
PortAudio real-time audio module for Csound
0dBFS level = 32768.0
Csound version 5.12 (double samples) Sep 15 2010
libsndfile-1.0.21
UnifiedCSD:
/home/jux/Activities/TamTamMini.activity/common/Resources/tamtamorc.csd
STARTING FILE
Creating options
Herstellen des Orchesters
Creating score
orchname: /tmp/csound-uN7ijG.orc
scorename: /tmp/csound-QRX3dJ.sco
