12.1.0 devel build 3 released, for XO-1.5 and XO-1
The It's a new dawn, it's a new day, it's a new life and I'm release. THIS IS A DEVELOPMENT RELEASE AIMED AT CORE SUGAR/DEVICE DEVELOPERS This is the first build with support for gtk3 activies and we have lovely examples with working Browse and Read :-D Other than that we have the usual rawhide updates including various bits we need for sugar gtk3 including fixes in the gtk3 css themes and various fixes and improvements for introspection support. Some other improvements include for this round of rawhide updates include libpng 1.5 which should include some perf improvements. With the festive period coming to a close the next month will ramp up rawhide changes. The big one being gcc 4.7.0 due to hit in the coming week or so with a mass rebuild following soon after. Some of the details of this release are: - Fedora rawhide (it will become Fedora 17) - Sugar 0.95.3 - sugar-toolkit-gtk3 - Browse 130... webkit based and it works! - Read 94 and it works! - gnome 3.3.3 - likely a lot of other bits I've missed Download from: http://build.laptop.org/12.1.0/os3/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Techteam] 12.1.0 devel build 3 released, for XO-1.5 and XO-1
On Tue, Jan 3, 2012 at 3:24 AM, Peter Robinson pbrobin...@gmail.com wrote: This is the first build with support for gtk3 activies and we have lovely examples with working Browse and Read :-D Welcome to 2012, with this uncut diamond from Peter. This is the brave new world of systemd, and gtk3. The first snapshot of the fruits of the heavy work from Simon, Gonzalo, Daniel and Manuel from the OLPC team, and contributions from SugarLabs folks. It also includes GNOME 3. Time to try it all out! cheers, m -- mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
The Fedora Fifteen Franken ARM hardfp build 1 for XO 1.75
The This sonic transducer, it is I suppose some kind of audio-vibratory-physio-molecular transport device? release. THIS IS A DEVELOPMENT RELEASE AIMED AT CORE OS/HW DEVELOPERS This is a hard floating point Franken release for development and testing of the hardfp on the XO 1.75. Its very incomplete and has a number of things that don't work. This is expected and its a release only really intended for people that understandard what hardfp is and the significance of it and wish to test and develop further for this fairly major feature both for upstream Fedora and the XO releases. This isn't a release that shouldn't have bug reports against it. So what are the known issues, and what works? - X works using fbdev. There's an issue with resolution. Fix this by removing the Virtual line from /etc/X11/xorg.conf.d/xo1.75.conf - No accelerated X - Sugar and GNOME do work quite well - Networking seems to work OK - Firefox DOESN'T work. Known issue, hopefully should be fixed before long - Midori for GNOME, Surf for Sugar included as browsers. I've been working to get this to a reasonable testing state for a while and finally all the bits fell into place. There's quite a bit of change going on in the ARM Fedora 15 world. I would suggest regular yum update to get the latest builds. I'm not expecting to do regular builds of this, but will happily cut more builds if people think a new one would be useful. Download from: http://build.laptop.org/F15-arm/os1/ For those interested in hardfp stuff enjoy :-) Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: USB permissions for educational robots
roughly speaking, we chose the dialout group because a) it's a
traditional group for access to UNIX serial devices, b) many USB
devices that activities need access to are actually serial devices,
and c) the olpc user is already a member of dialout. is it
important that Lego devices be protected by a separate group
membership?
the current udev rule isn't added by Sugar -- it's in the olpc-utils
rpm distributed by OLPC. we can add a modified rule once we agree
on what it should look like.
i can't remember at the moment where the default passwd and group
files come from -- if the rule needs a new group, we'll need to modify
those files as well.
paul
alan jhonn aguiar schwyn wrote:
Hi,
In a few of months, all our High Schools (of Uruguay) will receive and
robotic
kit (Lego).
At Universidad de la República, Facultad de Ingeniería we are
workingwith
it and the XO...
http://www.youtube.com/watch?v=S8HRbDLO7LM
In other parallel road, we are working on a 2.0 version of the Butia Robot
www.fing.edu.uy/inco/proyectos/butia
That uses USB4all IO board which resulted from a thesis given at
ourUniversity
(also will have arduino compatibility)
http://www.fing.edu.uy/inco/grupos/mina/pGrado/pgusb/
USB4all is based on 18f4550 pic.The vendor is Microchip,
SYSFS{idVendor}==04d8And have: productID=0x000b //bootloader
productID=0x000c //pic18f4550 generic comunication
The actual Sugar image, only have permissions for LEGO WeDo.
If you see in: /etc/udev/rules.d you find the correspondient:
30-olpc-wedo.rules.
The file add this rule:
SYSFS{idVendor}==0694, SYSFS{idProduct}==0003, GROUP=dialout,
MODE=0660
This means: 0694 is LEGO 0003 the model: WeDo
To the NXT we need add: {idProduct}==0002
But, for each model add a new line.. not is a good form..
Exist another way, a generic rule:
BUS==usb, SYSFS{idVendor}==0694, GROUP=lego, MODE=0660
That says: if is USB and fabricated by 0694 (LEGO) lets 0660 (4: read+ 2:
write)
If add this permissions to lego group, we need create it..
But, we don't make it, an use an existing group like root? Or another...
Suggestions?
We can make a generic group robot that have permissions for: lego wedo,
lego
nxt, butia, etc...
Regards!
Alan part 2 text/plain
129
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
=-
paul fox, p...@laptop.org
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: USB permissions for educational robots
I think martin_xsa wanted create a group robots too,
as part of http://wiki.laptop.org/go/11.2.0/Robotics_plan
Gonzalo
On Tue, Jan 3, 2012 at 11:12 AM, Paul Fox p...@laptop.org wrote:
roughly speaking, we chose the dialout group because a) it's a
traditional group for access to UNIX serial devices, b) many USB
devices that activities need access to are actually serial devices,
and c) the olpc user is already a member of dialout. is it
important that Lego devices be protected by a separate group
membership?
the current udev rule isn't added by Sugar -- it's in the olpc-utils
rpm distributed by OLPC. we can add a modified rule once we agree
on what it should look like.
i can't remember at the moment where the default passwd and group
files come from -- if the rule needs a new group, we'll need to modify
those files as well.
paul
alan jhonn aguiar schwyn wrote:
Hi,
In a few of months, all our High Schools (of Uruguay) will receive and
robotic
kit (Lego).
At Universidad de la República, Facultad de Ingeniería we are
workingwith
it and the XO...
http://www.youtube.com/watch?v=S8HRbDLO7LM
In other parallel road, we are working on a 2.0 version of the Butia
Robot
www.fing.edu.uy/inco/proyectos/butia
That uses USB4all IO board which resulted from a thesis given at
ourUniversity
(also will have arduino compatibility)
http://www.fing.edu.uy/inco/grupos/mina/pGrado/pgusb/
USB4all is based on 18f4550 pic.The vendor is Microchip,
SYSFS{idVendor}==04d8And have: productID=0x000b //bootloader
productID=0x000c //pic18f4550 generic comunication
The actual Sugar image, only have permissions for LEGO WeDo.
If you see in: /etc/udev/rules.d you find the correspondient:
30-olpc-wedo.rules.
The file add this rule:
SYSFS{idVendor}==0694, SYSFS{idProduct}==0003, GROUP=dialout,
MODE=0660
This means: 0694 is LEGO 0003 the model: WeDo
To the NXT we need add: {idProduct}==0002
But, for each model add a new line.. not is a good form..
Exist another way, a generic rule:
BUS==usb, SYSFS{idVendor}==0694, GROUP=lego, MODE=0660
That says: if is USB and fabricated by 0694 (LEGO) lets 0660 (4: read+
2: write)
If add this permissions to lego group, we need create it..
But, we don't make it, an use an existing group like root? Or
another...
Suggestions?
We can make a generic group robot that have permissions for: lego
wedo, lego
nxt, butia, etc...
Regards!
Alan part 2 text/plain
129
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
=-
paul fox, p...@laptop.org
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: [Techteam] The Fedora Fifteen Franken ARM hardfp build 1 for XO 1.75
On Tue, Jan 3, 2012 at 8:03 AM, Peter Robinson pbrobin...@gmail.com wrote: The This sonic transducer, it is I suppose some kind of audio-vibratory-physio-molecular transport device? release. Right out of Barbarella! This is a hard floating point Franken release for development and testing of the hardfp on the XO 1.75. Its very incomplete and has a number of things that don't work. And I am downloading it now :-) m -- mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Techteam] The Fedora Fifteen Franken ARM hardfp build 1 for XO 1.75
On Tue, Jan 3, 2012 at 6:55 AM, Martin Langhoff mar...@laptop.org wrote: On Tue, Jan 3, 2012 at 8:03 AM, Peter Robinson pbrobin...@gmail.com wrote: The This sonic transducer, it is I suppose some kind of audio-vibratory-physio-molecular transport device? release. Right out of Barbarella! This is a hard floating point Franken release for development and testing of the hardfp on the XO 1.75. Its very incomplete and has a number of things that don't work. And I am downloading it now :-) We can build some binary graphics drivers for performance testing. Still not to sort out the long term solution. -Jon ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
RE: USB permissions for educational robots
roughly speaking, we chose the dialout group because a) it's a traditional group for access to UNIX serial devices, b) many USB devices that activities need access to are actually serial devices, and c) the olpc user is already a member of dialout. is it important that Lego devices be protected by a separate group membership? No.. was only a idea... Seeing the Wiki appears this: http://wiki.laptop.org/go/Robots/udev_rules In the article: http://wiki.laptop.org/go/11.2.0/Robotics_plan Can be add USB4all in the list? http://wiki.laptop.org/go/11.2.0/Robotics_plan#Dev_and_test_matrix the current udev rule isn't added by Sugar -- it's in the olpc-utils rpm distributed by OLPC. we can add a modified rule once we agree on what it should look like. +1___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: USB permissions for educational robots
Please add it, with the information needed to continue the work. Contact info too if possible. Gonzalo In the article: http://wiki.laptop.org/go/11.2.0/Robotics_plan Can be add USB4all in the list? http://wiki.laptop.org/go/11.2.0/Robotics_plan#Dev_and_test_matrix the current udev rule isn't added by Sugar -- it's in the olpc-utils rpm distributed by OLPC. we can add a modified rule once we agree on what it should look like. +1 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: USB permissions for educational robots
andres wrote:
Here in uruguay xo`s are distributed with no permission to install rpm or
modify udev rules, so is very important to have this rules added to work
with butiá 2.0 and nxt in a near future.
we can add it, but clearly it would be best if deployments or even
local classrooms could add new device capabilities on their own.
because as soon as we say great, we're done, someone will create
a new USB device that kids and teachers everywhere will want to use.
i would greatly appreciate someone coming up with a scheme to allow
the end-user, or a deployment, to add devices on their own.
perhaps the user should be given r/w permission for any USB device.
(yes, i understand there are big risks with that. feel free to
propose exceptions that would make this safe.)
paul
Regards
Andrés
Enviado desde mi teléfono móvil, disculpe los errores de tipeo.
El 03/01/2012 12:12, Paul Fox p...@laptop.org escribió:
roughly speaking, we chose the dialout group because a) it's a
traditional group for access to UNIX serial devices, b) many USB
devices that activities need access to are actually serial devices,
and c) the olpc user is already a member of dialout. is it
important that Lego devices be protected by a separate group
membership?
the current udev rule isn't added by Sugar -- it's in the olpc-utils
rpm distributed by OLPC. we can add a modified rule once we agree
on what it should look like.
i can't remember at the moment where the default passwd and group
files come from -- if the rule needs a new group, we'll need to modify
those files as well.
paul
alan jhonn aguiar schwyn wrote:
Hi,
In a few of months, all our High Schools (of Uruguay) will receive and
robotic
kit (Lego).
At Universidad de la República, Facultad de Ingeniería we are
workingwith
it and the XO...
http://www.youtube.com/watch?v=S8HRbDLO7LM
In other parallel road, we are working on a 2.0 version of the Butia
Robot
www.fing.edu.uy/inco/proyectos/butia
That uses USB4all IO board which resulted from a thesis given at
ourUniversity
(also will have arduino compatibility)
http://www.fing.edu.uy/inco/grupos/mina/pGrado/pgusb/
USB4all is based on 18f4550 pic.The vendor is Microchip,
SYSFS{idVendor}==04d8And have: productID=0x000b //bootloader
productID=0x000c //pic18f4550 generic comunication
The actual Sugar image, only have permissions for LEGO WeDo.
If you see in: /etc/udev/rules.d you find the correspondient:
30-olpc-wedo.rules.
The file add this rule:
SYSFS{idVendor}==0694, SYSFS{idProduct}==0003, GROUP=dialout,
MODE=0660
This means: 0694 is LEGO 0003 the model: WeDo
To the NXT we need add: {idProduct}==0002
But, for each model add a new line.. not is a good form..
Exist another way, a generic rule:
BUS==usb, SYSFS{idVendor}==0694, GROUP=lego, MODE=0660
That says: if is USB and fabricated by 0694 (LEGO) lets 0660 (4: read+
2: write)
If add this permissions to lego group, we need create it..
But, we don't make it, an use an existing group like root? Or
another...
Suggestions?
We can make a generic group robot that have permissions for: lego
wedo, lego
nxt, butia, etc...
Regards!
Alan part 2 text/plain
129
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
=-
paul fox, p...@laptop.org
=-
paul fox, p...@laptop.org
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: 12.1.0 devel build 3 released, for XO-1.5 and XO-1
On an XO-1, build os3 was quite unusable until I disabled power management. All too soon after initial boot-up, the XO-1 would lock up -- it would not accept keystrokes (even though the Power LED was not blinking); after a couple of seconds it would not perform cursor movement either. I am no longer nimble - it felt to me that I had to really *rush* to My Settings to deactivate suspend/resume before their effect was to lock me out. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 12.1.0 devel build 3 released, for XO-1.5 and XO-1
On Tue, Jan 3, 2012 at 8:09 PM, Mikus Grinbergs mi...@bga.com wrote: On an XO-1, build os3 was quite unusable until I disabled power management. All too soon after initial boot-up, the XO-1 would lock up -- it would not accept keystrokes (even though the Power LED was not blinking); after a couple of seconds it would not perform cursor movement either. I am no longer nimble - it felt to me that I had to really *rush* to My Settings to deactivate suspend/resume before their effect was to lock me out. Weird, I've not seen that on my XO-1 at all, its just been sitting there running for over 24 hours without issues. Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: USB permissions for educational robots
Here in uruguay xo`s are distributed with no permission to install rpm or
modify udev rules, so is very important to have this rules added to work
with butiá 2.0 and nxt in a near future.
Regards
Andrés
Enviado desde mi teléfono móvil, disculpe los errores de tipeo.
El 03/01/2012 12:12, Paul Fox p...@laptop.org escribió:
roughly speaking, we chose the dialout group because a) it's a
traditional group for access to UNIX serial devices, b) many USB
devices that activities need access to are actually serial devices,
and c) the olpc user is already a member of dialout. is it
important that Lego devices be protected by a separate group
membership?
the current udev rule isn't added by Sugar -- it's in the olpc-utils
rpm distributed by OLPC. we can add a modified rule once we agree
on what it should look like.
i can't remember at the moment where the default passwd and group
files come from -- if the rule needs a new group, we'll need to modify
those files as well.
paul
alan jhonn aguiar schwyn wrote:
Hi,
In a few of months, all our High Schools (of Uruguay) will receive and
robotic
kit (Lego).
At Universidad de la República, Facultad de Ingeniería we are
workingwith
it and the XO...
http://www.youtube.com/watch?v=S8HRbDLO7LM
In other parallel road, we are working on a 2.0 version of the Butia
Robot
www.fing.edu.uy/inco/proyectos/butia
That uses USB4all IO board which resulted from a thesis given at
ourUniversity
(also will have arduino compatibility)
http://www.fing.edu.uy/inco/grupos/mina/pGrado/pgusb/
USB4all is based on 18f4550 pic.The vendor is Microchip,
SYSFS{idVendor}==04d8And have: productID=0x000b //bootloader
productID=0x000c //pic18f4550 generic comunication
The actual Sugar image, only have permissions for LEGO WeDo.
If you see in: /etc/udev/rules.d you find the correspondient:
30-olpc-wedo.rules.
The file add this rule:
SYSFS{idVendor}==0694, SYSFS{idProduct}==0003, GROUP=dialout,
MODE=0660
This means: 0694 is LEGO 0003 the model: WeDo
To the NXT we need add: {idProduct}==0002
But, for each model add a new line.. not is a good form..
Exist another way, a generic rule:
BUS==usb, SYSFS{idVendor}==0694, GROUP=lego, MODE=0660
That says: if is USB and fabricated by 0694 (LEGO) lets 0660 (4: read+
2: write)
If add this permissions to lego group, we need create it..
But, we don't make it, an use an existing group like root? Or
another...
Suggestions?
We can make a generic group robot that have permissions for: lego
wedo, lego
nxt, butia, etc...
Regards!
Alan part 2 text/plain
129
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
=-
paul fox, p...@laptop.org
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Preferred way to add touch to Sugar apps
What is the preferred API for adding touchscreen (or mouse) support to a Sugar activity ? Ideally it would support multitouch and provide simple gesture support, but I'll settle for much less :-) Fedora 15 or earlier please, this is for ARM. Cheers, wad ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Preferred way to add touch to Sugar apps
What is the preferred API for adding touchscreen (or mouse) support to a Sugar activity ? Ideally it would support multitouch and provide simple gesture support, but I'll settle for much less :-) Fedora 15 or earlier please, this is for ARM. Cheers, wad The 1.75 XO has a touchscreen ? M ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Preferred way to add touch to Sugar apps
On Jan 3, 2012, at 9:16 PM, Marek Vasut wrote: What is the preferred API for adding touchscreen (or mouse) support to a Sugar activity ? Ideally it would support multitouch and provide simple gesture support, but I'll settle for much less :-) Fedora 15 or earlier please, this is for ARM. Cheers, wad The 1.75 XO has a touchscreen ? No, but the A-prototypes of the XO-3 do. Cheers, wad ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
RE: [Sugar-devel] Preferred way to add touch to Sugar apps
No, but the A-prototypes of the XO-3 do. I want one! ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Preferred way to add touch to Sugar apps
On Jan 3, 2012, at 9:08 PM, Walter Bender wrote: On Tue, Jan 3, 2012 at 9:04 PM, John Watlington w...@laptop.org wrote: What is the preferred API for adding touchscreen (or mouse) support to a Sugar activity ? Should just work. The activity was limited to keyboard input in the past. But it really wants gesture based input, not buttons on the screen. Supporting mouse clicks would be a way of doing it in a backwards compatible way. Cheers, wad ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
SugarLabs server - web page
Hi, Many times, I wondered, what activities had to Sugar page SL (SugarLabs). But when you arelooking for, not is easily to find the activities that are not public. Furthermore, when adding anew activity, you do not know if there is already a similar (even the same) on the server.So I started making a list of everything I had in the server: http://download.sugarlabs.org/activities/ Is a simple system: a folder for an activity and after, in the web, with the same number: thepage of the activity.For example: the activity I know America was in the server in: http://download.sugarlabs.org/activities/4464/And in SugarLabs: http://activities.sugarlabs.org/en-US/sugar/addon/4464 When I check all the files, I encountered many interesting things..Activities that did not even have a page on SL... Duplicate activities/files..So we have supplemented the list with that information.In the first column, see the id that is automatically generated on the server. In the second columnshows the name of the activity that is in that folder. In the spaces are blank, because there are nosuch folders on the server. In the column Notes are cases in which there are empty folders.The third column Page indicates the status of that activity in SL. Green means it is public.Orange means it is as Experimental. Red means there is no page for this activity!With the same color, I try to show the duplicate files.. Who is the maintainer of the site / server? File attached: https://docs.google.com/spreadsheet/ccc?key=0AntaXnq4oy2_dFJjNE9TemZUUGtzLVNEQnF4UlIwQkE Regards Alan ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: SugarLabs server - web page
I've added a column for L10n. ther are some uncertainties. tr.sl.o = our Pootle instance pending = awaiting upload to Pootle gnome = Gnome Damned Lies server cjl On Tue, Jan 3, 2012 at 11:20 PM, Alan Jhonn Aguiar Schwyn alan...@hotmail.com wrote: Hi, Many times, I wondered, what activities had to Sugar page SL (SugarLabs). But when you are looking for, not is easily to find the activities that are not public. Furthermore, when adding a new activity, you do not know if there is already a similar (even the same) on the server. So I started making a list of everything I had in the server: http://download.sugarlabs.org/activities/ Is a simple system: a folder for an activity and after, in the web, with the same number: the page of the activity. For example: the activity I know America was in the server in: http://download.sugarlabs.org/activities/4464/ And in SugarLabs: http://activities.sugarlabs.org/en-US/sugar/addon/4464 When I check all the files, I encountered many interesting things.. Activities that did not even have a page on SL... Duplicate activities/files.. So we have supplemented the list with that information. In the first column, see the id that is automatically generated on the server. In the second column shows the name of the activity that is in that folder. In the spaces are blank, because there are no such folders on the server. In the column Notes are cases in which there are empty folders. The third column Page indicates the status of that activity in SL. Green means it is public. Orange means it is as Experimental. Red means there is no page for this activity! With the same color, I try to show the duplicate files.. Who is the maintainer of the site / server? File attached: https://docs.google.com/spreadsheet/ccc?key=0AntaXnq4oy2_dFJjNE9TemZUUGtzLVNEQnF4UlIwQkE Regards Alan ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel SugarLabs - Complete list of activities.ods Description: application/vnd.oasis.opendocument.spreadsheet ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
RE: SugarLabs server - web page
Thank you! I updated the document... From: cjlhomeaddr...@gmail.com Date: Wed, 4 Jan 2012 00:57:59 -0500 Subject: Re: SugarLabs server - web page To: alan...@hotmail.com CC: a...@lists.sugarlabs.org; sugar-de...@lists.sugarlabs.org; devel@lists.laptop.org; walter.ben...@gmail.com I've added a column for L10n. ther are some uncertainties. tr.sl.o = our Pootle instance pending = awaiting upload to Pootle gnome = Gnome Damned Lies server cjl On Tue, Jan 3, 2012 at 11:20 PM, Alan Jhonn Aguiar Schwyn alan...@hotmail.com wrote: Hi, Many times, I wondered, what activities had to Sugar page SL (SugarLabs). But when you are looking for, not is easily to find the activities that are not public. Furthermore, when adding a new activity, you do not know if there is already a similar (even the same) on the server. So I started making a list of everything I had in the server: http://download.sugarlabs.org/activities/ Is a simple system: a folder for an activity and after, in the web, with the same number: the page of the activity. For example: the activity I know America was in the server in: http://download.sugarlabs.org/activities/4464/ And in SugarLabs: http://activities.sugarlabs.org/en-US/sugar/addon/4464 When I check all the files, I encountered many interesting things.. Activities that did not even have a page on SL... Duplicate activities/files.. So we have supplemented the list with that information. In the first column, see the id that is automatically generated on the server. In the second column shows the name of the activity that is in that folder. In the spaces are blank, because there are no such folders on the server. In the column Notes are cases in which there are empty folders. The third column Page indicates the status of that activity in SL. Green means it is public. Orange means it is as Experimental. Red means there is no page for this activity! With the same color, I try to show the duplicate files.. Who is the maintainer of the site / server? File attached: https://docs.google.com/spreadsheet/ccc?key=0AntaXnq4oy2_dFJjNE9TemZUUGtzLVNEQnF4UlIwQkE Regards Alan ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Techteam] The Fedora Fifteen Franken ARM hardfp build 1 for XO 1.75
On 03/01/12 14:03, Peter Robinson wrote: The This sonic transducer, it is I suppose some kind of audio-vibratory-physio-molecular transport device? release. THIS IS A DEVELOPMENT RELEASE AIMED AT CORE OS/HW DEVELOPERS This is a hard floating point Franken release for development and testing of the hardfp on the XO 1.75. Its very incomplete and has a number of things that don't work. This is expected and its a release only really intended for people that understandard what hardfp is and the significance of it and wish to test and develop further for this fairly major feature both for upstream Fedora and the XO releases. This isn't a release that shouldn't have bug reports against it. So what are the known issues, and what works? - X works using fbdev. There's an issue with resolution. Fix this by removing the Virtual line from /etc/X11/xorg.conf.d/xo1.75.conf - No accelerated X - Sugar and GNOME do work quite well - Networking seems to work OK - Firefox DOESN'T work. Known issue, hopefully should be fixed before long - Midori for GNOME, Surf for Sugar included as browsers. I've been working to get this to a reasonable testing state for a while and finally all the bits fell into place. There's quite a bit of change going on in the ARM Fedora 15 world. I would suggest regular yum update to get the latest builds. I'm not expecting to do regular builds of this, but will happily cut more builds if people think a new one would be useful. Download from: http://build.laptop.org/F15-arm/os1/ For those interested in hardfp stuff enjoy :-) Peter For booting I had to use the 'checker'-key (the right one of the game keys), otherwise I had a white screen after booting. (I think I had this with one of Daniel's early F16 builds, he might know how to fix this). Removing the 'Virtual' line as indicated above fixed the resolution fine for me. Regards, Simon ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
