Yes
On Sat, Apr 5, 2014 at 1:48 AM, wrote:
> Thanks
>
> So am I right to say that currently Sugar and its Activities never
> generate notifications and the only way to generate one is to run a test
> script?
>
> Tony
>
>
>
> You have information about how to test here:
>>
>> http://wiki.sugarl
Thanks
So am I right to say that currently Sugar and its Activities never
generate notifications and the only way to generate one is to run a
test script?
Tony
You have information about how to test here:
http://wiki.sugarlabs.org/go/Features/Notification_System
By the way, I have upda
You have information about how to test here:
http://wiki.sugarlabs.org/go/Features/Notification_System
By the way, I have updated http://wiki.sugarlabs.org/go/0.102/Feature_List
Gonzalo
On Sat, Apr 5, 2014 at 12:23 AM, wrote:
> Thanks
>
> How and when are notifications generated? I want to
Thanks
How and when are notifications generated? I want to test the new
feature - notification system.
Tony
Hello Everyone,
I have created images for all XO models, with the updated sugar packages
that were provided by Gonzalo. These images are based on OLPC-AU au1b
images.
Please visit
On Fri, Apr 4, 2014 at 5:45 PM, James Cameron wrote:
> On Fri, Apr 04, 2014 at 05:38:08PM -0300, Gonzalo Odiard wrote:
> > manuq taught me a useful github trick:
> >
> > when you have a link like https://github.com/sugarlabs/sugar/pull/328
> > you can add .patch or .diff to the url
> > and get a
On Fri, Apr 04, 2014 at 05:38:08PM -0300, Gonzalo Odiard wrote:
> manuq taught me a useful github trick:
>
> when you have a link like https://github.com/sugarlabs/sugar/pull/328
> you can add .patch or .diff to the url
> and get a clean patch
> can be useful for you I imagine.
Agreed.
Now, th
On Fri, Apr 4, 2014 at 5:24 PM, James Cameron wrote:
> It is so irritating that to review patches to Sugar one has to click
> on the link in the mail, which doesn't even get you to the patch, but
> instead takes you to a page you have to click twice on to see the
> code. And since the pages are
On Fri, Apr 04, 2014 at 12:18:36PM +0100, Daniel Narvaez wrote:
> I think we should move more of our modules to github, at least all
> the ones we are currently building in sugar-build. [... and a list
> ...]
I agree with moving these.
--
James Cameron
http://quozl.linux.org.au/
___
It is so irritating that to review patches to Sugar one has to click
on the link in the mail, which doesn't even get you to the patch, but
instead takes you to a page you have to click twice on to see the
code. And since the pages are SSL over HTTP, the time to connect can
be considerable. This r
Thanks Martin,
I hope we get more testing this cycle...
Gonzalo
On Fri, Apr 4, 2014 at 12:37 PM, Martin Abente <
martin.abente.lah...@gmail.com> wrote:
> Hello Everyone,
>
> I have created images for all XO models, with the updated sugar packages
> that were provided by Gonzalo. These images a
Hello Everyone,
I have created images for all XO models, with the updated sugar packages
that were provided by Gonzalo. These images are based on OLPC-AU au1b
images.
Please visit [1] for the download information.
I have quick tested on XO4, XO1.75 and XO1.5, but not on XO1.
Regards,
tch.
Re
I was exploring use the gi api for network manager,
instead of our old dbus api.
This was not done when we ported sugar to gtk3.
I have sent two pr [1] and [2] with the easy parts.
The last piece missing is jarabe/model/network.py
and is a big piece. I started to change it, but look like a big pro
This is a bug that has been present for a while.
It occurs when your code have the same name for a class for the file that
contains it.
For example, this fails: from Record import Record
2014-04-04 9:01 GMT-03:00 Puneet Kaur :
> cool ! :-)
>
>
> On Fri, Apr 4, 2014 at 5:27 PM, Gonzalo Odiard w
On Fri, Apr 4, 2014 at 10:06 AM, Chris Leonard wrote:
> I did not do the move to github and I do not know how to either. I am
> going to need help to teach me how to do that.
>
> In fact, I am getting overwhelmed with other things and may need to
> pull back from some of the Pootle maintenance I
I did not do the move to github and I do not know how to either. I am
going to need help to teach me how to do that.
In fact, I am getting overwhelmed with other things and may need to
pull back from some of the Pootle maintenance I have been doing.
On Fri, Apr 4, 2014 at 7:18 AM, Gonzalo Odiard
> 4 Update pootle. Gonzalo, did you volunteer? :)
>
Asked cjl who did it the last time.
Gonzalo
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
cool ! :-)
On Fri, Apr 4, 2014 at 5:27 PM, Gonzalo Odiard wrote:
> Ok, we are looking at solving this issue in sugar-toolkit,
> then copy the file is not needed in the future.
>
> Gonzalo
>
>
> On Fri, Apr 4, 2014 at 8:55 AM, Puneet Kaur wrote:
>
>> yup that solved the problem.
>>
>> copied own
I'm in (pippy and turtleart). For Pootle purposes, there is also
turtleart-extras; not sure if it is relevant in this case: I use it to
provide translation services for the various Turtle Art forks, of
which there are about a dozen)
-walter
On Fri, Apr 4, 2014 at 7:18 AM, Daniel Narvaez wrote:
>
Ok, we are looking at solving this issue in sugar-toolkit,
then copy the file is not needed in the future.
Gonzalo
On Fri, Apr 4, 2014 at 8:55 AM, Puneet Kaur wrote:
> yup that solved the problem.
>
> copied owner.key.pub file to ~/.sugar/default and now it runs :-)
>
>
> Thanks,
>
>
> On Fri,
With sugar 0.100 or better, you can use Collections (the .xol files)
just as activities. Are displayed in the Home, can be updated,
uninstalled, and so.
I imagine that can be useful for you.
Gonzalo
On Fri, Apr 4, 2014 at 8:43 AM, Martin Dluhos wrote:
> On 4.4.2014 16:26, Gonzalo Odiard wrote:
yup that solved the problem.
copied owner.key.pub file to ~/.sugar/default and now it runs :-)
Thanks,
On Fri, Apr 4, 2014 at 5:19 PM, Gonzalo Odiard wrote:
> Can you copy the file in the directory ~/.sugar/default ?
>
> Gonzalo
>
>
> On Fri, Apr 4, 2014 at 8:48 AM, Puneet Kaur wrote:
>
>> H
Can you copy the file in the directory ~/.sugar/default ?
Gonzalo
On Fri, Apr 4, 2014 at 8:48 AM, Puneet Kaur wrote:
> Hey,
>
> The key is already there in owner.key.pub file inside
> /home/dotsugar/default directory.
>
>
> On Fri, Apr 4, 2014 at 2:59 PM, Sam Parkinson wrote:
>
>> Hi,
>>
>> Tr
Hey,
The key is already there in owner.key.pub file inside
/home/dotsugar/default directory.
On Fri, Apr 4, 2014 at 2:59 PM, Sam Parkinson wrote:
> Hi,
>
> Try copying your ssh keys to [dot sugar dir]/default/. You should copy the
> id_rsa.pub to owner.key.pub
>
> Have a look at this for how to
On 4.4.2014 16:26, Gonzalo Odiard wrote:
> Nice. Just for curiosity, what is the shortcut needed?
My goal was to make launching E-Paath, a collection of interactive activities
based on Nepali curriculum, as easy as possible. I had difficulty converting it
into a sugarized activity on 12.1.0, so I
Hello,
I think we should move more of our modules to github, at least all the ones
we are currently building in sugar-build.
That will make it easier for contributors because they won't have to go
through two different processes to submit patches. Also gitorious lacks pr
notifications which is re
Hi Chris,
If we need update the repositories where pootle server should work
for different projects who can do it?
I don't remember who did it the last time, and I don't have permissions.
Thanks!
--
Gonzalo Odiard
SugarLabs - Learning Software for children
___
Should we move sugar-toolkit to github too?
Gonzalo
On Fri, Apr 4, 2014 at 7:46 AM, Daniel Narvaez wrote:
> Oooh damn gtk2... This needs to be backported to sugar-toolkit
>
> commit fe192be798ac1a9bd13983d197cb5775b7da2ad5
> Author: Daniel Narvaez
> Date: Wed Sep 11 16:36:31 2013 +0200
>
>
Oooh damn gtk2... This needs to be backported to sugar-toolkit
commit fe192be798ac1a9bd13983d197cb5775b7da2ad5
Author: Daniel Narvaez
Date: Wed Sep 11 16:36:31 2013 +0200
Add a SUGAR_HOME environment variable
We should really use XDG directories but that will be a bit
more complic
Nice. Just for curiosity, what is the shortcut needed?
Gonzalo
On Fri, Apr 4, 2014 at 2:42 AM, Martin Dluhos wrote:
> On 2.4.2014 17:49, Gonzalo Odiard wrote:
> > I don't think that has changed,
> > try /usr/share/sugar/extensions/globalkey
>
> Thanks a bunch. That worked for me!
>
> Martin
>
Record is a gtk2 activity, then is using sugar.profile, not sugar3.profile,
and is not looking at the broot directory, but to .sugar/default/
I think we discussed this issue about the compatibility with gtk2
activities before,
but don't remember what we decided.
Gonzalo
On Fri, Apr 4, 2014 at 7:
Aren't the keys supposed to be created by sugar on first start?
On Friday, 4 April 2014, Sam Parkinson wrote:
> Hi,
>
> Try copying your ssh keys to [dot sugar dir]/default/. You should copy the
> id_rsa.pub to owner.key.pub
>
> Have a look at this for how to make ssh keys if you need to:
> http
You can see the /home/broot path inside an osbuild shell, it corresponds to
sugar-build/home.
On Friday, 4 April 2014, Puneet Kaur wrote:
> I am unable to launch the record activity in my sugar development
> environment due to the following (as seen in the log):
>
> ** Message: pygobject_registe
Hi,
Try copying your ssh keys to [dot sugar dir]/default/. You should copy the
id_rsa.pub to owner.key.pub
Have a look at this for how to make ssh keys if you need to:
https://help.github.com/articles/generating-ssh-keys
Hope that helps :)
Sam
On Apr 4, 2014 8:15 PM, "Puneet Kaur" wrote:
> I
I am unable to launch the record activity in my sugar development
environment due to the following (as seen in the log):
** Message: pygobject_register_sinkfunc is deprecated (GstObject)
** Message: pygobject_register_sinkfunc is deprecated (HippoCanvasBox)
Traceback (most recent call last):
Fil
34 matches
Mail list logo
