Re: [Sugar-devel] New feature: add information in About this computer

2013-11-11 Thread Esteban Bordón
Hi Gonzalo,

Is it possible to show/hide the control panel sections by some gconf entry?
It can be useful to clean some sections that some deployment have not
been using.


Cheers,
Esteban.

2013/11/11 Gonzalo Odiard gonz...@laptop.org

 The deployments need a few pieces of information about the software in the
 Xos. This feature collect these changes because are small, and are
 connected to the About Computer section. The actual implementation is only
 a reference, is not proposed to be included in the actual form.

 The information to be added is:
 * Computer model.
 * Other licenses
 * Last update

 More information:
 http://wiki.sugarlabs.org/go/Features/AddInformationInAboutComputer

 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] New feature: add information in About this computer

2013-11-11 Thread Gonzalo Odiard
Right now, every section is packaged in a rpm,
may be is only needed install/uninstall the needed section?

Can you give us a example?

Gonzalo



On Mon, Nov 11, 2013 at 12:03 PM, Esteban Bordón ebor...@plan.ceibal.edu.uy
 wrote:

 Hi Gonzalo,

 Is it possible to show/hide the control panel sections by some gconf
 entry? It can be useful to clean some sections that some deployment have
 not been using.


 Cheers,
 Esteban.

 2013/11/11 Gonzalo Odiard gonz...@laptop.org

 The deployments need a few pieces of information about the software in
 the Xos. This feature collect these changes because are small, and are
 connected to the About Computer section. The actual implementation is only
 a reference, is not proposed to be included in the actual form.

 The information to be added is:
 * Computer model.
 * Other licenses
 * Last update

 More information:
 http://wiki.sugarlabs.org/go/Features/AddInformationInAboutComputer

 ___
 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] Proposing backup/restore as feature for 0.102

2013-11-11 Thread Martin Abente
The level of indirection was added because it used different backup
mechanisms, IE: to the XS (via dsd's rsync scripts) and to memory sticks.
Not sure who else is using dsd's scripts, other than Paraguay though.


On Mon, Nov 11, 2013 at 10:40 AM, Gonzalo Odiard gonz...@laptop.org wrote:

 One of the features we want upstream is Backup/Restore of the Journal.

 There are already a page for this feature [1] but the currently only
 is implemented
 the backup/restore to a connected device (pen drive), and not to/from
 the school server.

 I did the port to Sugar 0.100 of the code in dextrose, (patches [2] and
 [3])
 but still think need more work before pushing upstream.

 Here my comments/questions:

 * Right now, the access to backup/restore functionality is available in
 the menu
 of the connected device (see [4]). May be should be in the Journal button,
 to allow other destinations in the future, like google drive/dropbox/etc?
 Or should be as a option in the control panel? (If the control panel is
 only
 for configuration this may be not the right place)

 * The screen look alien [5]. Should be better if we add a toolbar or
 should be in a modal dialog similar to the control panel/ object chooser?

 * We need a better icon.

 * The actual implementation have scripts to backup/restore from the
 command line.
 Then the sugar code execute the scripts, and the scripts execute tar. Is
 needed
 this indirection or should be better call tar from sugar?

 This implementation can be tested in our AU images [6]

 Comments?

 Gonzalo

 [1] http://wiki.sugarlabs.org/go/Features/Backup_and_Restore

 [2]
 https://github.com/godiard/au1b_rpms/blob/master/sugar/0001-Backup-and-Restore-to-a-mounted-device.patch

 [3]
 https://github.com/godiard/au1b_rpms/blob/master/sugar/0001-Fix-backup-restore-functionality-SL-4616.patch

 [4] http://wiki.sugarlabs.org/go/File:Backup_usb_menu.png

 [5] http://wiki.sugarlabs.org/go/File:Backup_before.png

 [6] http://wiki.sugarlabs.org/index.php?title=0.100/Testing
 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] New feature: add information in About this computer

2013-11-11 Thread Esteban Bordón
I'm talking about the about-computer module. For example, Activation info
is not being used in Uruguay and we comment the lines that show these info



2013/11/11 Gonzalo Odiard gonz...@laptop.org

 Right now, every section is packaged in a rpm,
 may be is only needed install/uninstall the needed section?

 Can you give us a example?

 Gonzalo



 On Mon, Nov 11, 2013 at 12:03 PM, Esteban Bordón 
 ebor...@plan.ceibal.edu.uy wrote:

 Hi Gonzalo,

 Is it possible to show/hide the control panel sections by some gconf
 entry? It can be useful to clean some sections that some deployment have
 not been using.


 Cheers,
 Esteban.

 2013/11/11 Gonzalo Odiard gonz...@laptop.org

 The deployments need a few pieces of information about the software in
 the Xos. This feature collect these changes because are small, and are
 connected to the About Computer section. The actual implementation is only
 a reference, is not proposed to be included in the actual form.

 The information to be added is:
 * Computer model.
 * Other licenses
 * Last update

 More information:
 http://wiki.sugarlabs.org/go/Features/AddInformationInAboutComputer

 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel




___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] New feature: add information in About this computer

2013-11-11 Thread Jerry Vonau
On Mon, 2013-11-11 at 13:08 -0200, Gonzalo Odiard wrote:
 Right now, every section is packaged in a rpm,
 
 may be is only needed install/uninstall the needed section?
 
 
 Can you give us a example?
 
 
 Gonzalo
 
 

Please check the spec file, About my Computer, and About Me are not
packaged by themselves as cp-applets, those are part of sugar. Perhaps
having each field that is viewable controlled via gconf to make those
optional, much like logout and register currently are selectable. No
point in having serial number, model and lease viewable on SOAS.

Jerry  

 
 
 On Mon, Nov 11, 2013 at 12:03 PM, Esteban Bordón
 ebor...@plan.ceibal.edu.uy wrote:
 Hi Gonzalo, 
 
 
 Is it possible to show/hide the control panel sections by some
 gconf entry? It can be useful to clean some sections that
 some deployment have not been using. 
 
 
 
 
 Cheers,
 Esteban.
 
 2013/11/11 Gonzalo Odiard gonz...@laptop.org
 
 The deployments need a few pieces of information about
 the software in the Xos. This feature collect these
 changes because are small, and are connected to the
 About Computer section. The actual implementation is
 only a reference, is not proposed to be included in
 the actual form.
 
 
 The information to be added is:
 * Computer model.
 * Other licenses
 * Last update
 
 
 More
 information: 
 http://wiki.sugarlabs.org/go/Features/AddInformationInAboutComputer 
 
 
 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel
 
 
 
 
 
 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Sugar Labs Roadmap. [SD 61;79]

2013-11-11 Thread Daniel Narvaez
On 11 November 2013 05:10, David Farning dfarn...@activitycentral.comwrote:

 My experience has been that educational software politics and
 policies have been been the dominate influence within Sugar Labs. If
 this is the role that Sugar Labs wants to maintain that is fine, as
 long as they open the door to other organizations focusing on proven
 educational software quality.


The commits stats Gonzalo posted on this thread tells something very
different. In the last year Sugar Labs community developers made a lot more
more commits than company sponsored ones. Commits are not the most reliable
way of measuring contributions of course, but here they reflects pretty
well reality IMO.


 Both approaches have challenges. If Sugar Labs is willing to assume
 responsibility for quality education software, they will have to adopt
 a culture and processes which encourage feedback (even negative
 feedback) and ways to implement solutions to that feedback.


I think Sugar Labs is already assuming responsibility for the quality of
the software, in the form of contributions to the code base. We are doing
what we can to gather feedback too. How many times we asked for testing on
0.100 and we got almost none? I wish we had more feedback from the
deployments, but I have not idea of how to do that. Please help out with it?


 Otherwise they are going to have to accept the lose of control if
 other organizations such as AC provide that service.


I don't think we are afraid of organizations like AC getting involved. All
the contrary, I'd say the main Sugar Labs goal is to get more organizations
and individuals involved. Please contribute to the project and if you see
concrete roadblocks point them out, we will do what we can to remove them.


 As the bottom line; the Association is good at sales and marketing,
 Sugar Labs is good and vision and inspiration, and Activity Central is
 good at support and implementation. The most likely way to success is
 to figure out how these three, and any other organizations, can work
 together. Rather than focus on grudges.


Well, to set the facts straigths... OLPC is not selling Sugar anymore, as
far as I can tell from the comments on this list, some from ex OLPC
employees. And implementation has been done almost exclusively by the Sugar
Labs community in the last six months.

I hope AC will get more involved in the implementation and I'm encouraged
by the recent contributions. I'm sure a discussion on how we can concretely
help your support work would be welcome.

(You might have intended implementation in a larger sense, but the stricter
sense I'm using is a big part of it).
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] New feature: add information in About this computer

2013-11-11 Thread Gonzalo Odiard
Ahh, ok. I get it.

On Mon, Nov 11, 2013 at 1:03 PM, Esteban Bordón
ebor...@plan.ceibal.edu.uy wrote:
 I'm talking about the about-computer module. For example, Activation info is
 not being used in Uruguay and we comment the lines that show these info



 2013/11/11 Gonzalo Odiard gonz...@laptop.org

 Right now, every section is packaged in a rpm,
 may be is only needed install/uninstall the needed section?

 Can you give us a example?

 Gonzalo



 On Mon, Nov 11, 2013 at 12:03 PM, Esteban Bordón
 ebor...@plan.ceibal.edu.uy wrote:

 Hi Gonzalo,

 Is it possible to show/hide the control panel sections by some gconf
 entry? It can be useful to clean some sections that some deployment have
 not been using.


 Cheers,
 Esteban.

 2013/11/11 Gonzalo Odiard gonz...@laptop.org

 The deployments need a few pieces of information about the software in
 the Xos. This feature collect these changes because are small, and are
 connected to the About Computer section. The actual implementation is only 
 a
 reference, is not proposed to be included in the actual form.

 The information to be added is:
 * Computer model.
 * Other licenses
 * Last update

 More information:
 http://wiki.sugarlabs.org/go/Features/AddInformationInAboutComputer

 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel




___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] New feature: add information in About this computer

2013-11-11 Thread Gonzalo Odiard
True. Not all the sections are separated.

Anyway, Esteban clarification point to make the information in the
About my computer optative,
not to make the different sections optative.

Gonzalo

On Mon, Nov 11, 2013 at 1:05 PM, Jerry Vonau jvo...@shaw.ca wrote:
 On Mon, 2013-11-11 at 13:08 -0200, Gonzalo Odiard wrote:
 Right now, every section is packaged in a rpm,

 may be is only needed install/uninstall the needed section?


 Can you give us a example?


 Gonzalo



 Please check the spec file, About my Computer, and About Me are not
 packaged by themselves as cp-applets, those are part of sugar. Perhaps
 having each field that is viewable controlled via gconf to make those
 optional, much like logout and register currently are selectable. No
 point in having serial number, model and lease viewable on SOAS.

 Jerry



 On Mon, Nov 11, 2013 at 12:03 PM, Esteban Bordón
 ebor...@plan.ceibal.edu.uy wrote:
 Hi Gonzalo,


 Is it possible to show/hide the control panel sections by some
 gconf entry? It can be useful to clean some sections that
 some deployment have not been using.




 Cheers,
 Esteban.

 2013/11/11 Gonzalo Odiard gonz...@laptop.org

 The deployments need a few pieces of information about
 the software in the Xos. This feature collect these
 changes because are small, and are connected to the
 About Computer section. The actual implementation is
 only a reference, is not proposed to be included in
 the actual form.


 The information to be added is:
 * Computer model.
 * Other licenses
 * Last update


 More
 information: 
 http://wiki.sugarlabs.org/go/Features/AddInformationInAboutComputer


 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel





 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4

2013-11-11 Thread Daniel Drake
On Sun, Nov 10, 2013 at 5:18 PM, James Cameron qu...@laptop.org wrote:
 If you need to scale up this change to many laptops, contact
 reu...@laptop.org or myself.  I must know the SKU number.

In the particular case of changing language/keyboard defaults as we
are discussing, instead of changing manufacturing data I would
recommend doing it via olpc-os-builder, configuration for [base], see
http://dev.laptop.org/git/projects/olpc-os-builder/tree/modules/base/README#n46

Daniel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4

2013-11-11 Thread Jerry Vonau
On Mon, 2013-11-11 at 11:38 -0600, Daniel Drake wrote:
 On Sun, Nov 10, 2013 at 5:18 PM, James Cameron qu...@laptop.org wrote:
  If you need to scale up this change to many laptops, contact
  reu...@laptop.org or myself.  I must know the SKU number.
 
 In the particular case of changing language/keyboard defaults as we
 are discussing, instead of changing manufacturing data I would
 recommend doing it via olpc-os-builder, configuration for [base], see
 http://dev.laptop.org/git/projects/olpc-os-builder/tree/modules/base/README#n46
 

Or use TinyCore's xo-custom plugin to make the customizations to an
existing image on an unlocked XO.

http://dev.laptop.org/~quozl/mktinycorexo/HOWTO.xo-custom

Jerry

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Performance: activities start up time

2013-11-11 Thread Daniel Drake
On Fri, Nov 8, 2013 at 12:44 PM, Gonzalo Odiard gonz...@laptop.org wrote:
 One of the arguments of the dynamic bindings was a better startup time due
 to not need initialize all the libraries until is needed use them. Then the
 import should
 be lighter than before. Looks like that is not so true.

You should look in the last few months of archives of the pygobject
list, the discussions that I was involved in. pygobject is not doing
much lazy-loading, the overrides are really heavy, etc. Lots of
improvements to be made.

Daniel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


[Sugar-devel] [ASLO] Release Browse-156

2013-11-11 Thread Sugar Labs Activities
Activity Homepage:
http://activities.sugarlabs.org/addon/4024

Sugar Platform:
0.100 - 0.100

Download Now:
http://activities.sugarlabs.org/downloads/file/28823/browse-156.xo

Release notes:
Fixes: keep image doesn't work if the image is also a link.
Translations.


Sugar Labs Activities
http://activities.sugarlabs.org

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Proposing backup/restore as feature for 0.102

2013-11-11 Thread David Farning
On Mon, Nov 11, 2013 at 7:40 AM, Gonzalo Odiard gonz...@laptop.org wrote:
 One of the features we want upstream is Backup/Restore of the Journal.

 There are already a page for this feature [1] but the currently only
 is implemented
 the backup/restore to a connected device (pen drive), and not to/from
 the school server.

 I did the port to Sugar 0.100 of the code in dextrose, (patches [2] and [3])
 but still think need more work before pushing upstream.

 Here my comments/questions:

 * Right now, the access to backup/restore functionality is available in the 
 menu
 of the connected device (see [4]). May be should be in the Journal button,
 to allow other destinations in the future, like google drive/dropbox/etc?
 Or should be as a option in the control panel? (If the control panel is only
 for configuration this may be not the right place)

 * The screen look alien [5]. Should be better if we add a toolbar or
 should be in a modal dialog similar to the control panel/ object chooser?

 * We need a better icon.

 * The actual implementation have scripts to backup/restore from the
 command line.
 Then the sugar code execute the scripts, and the scripts execute tar. Is 
 needed
 this indirection or should be better call tar from sugar?

 This implementation can be tested in our AU images [6]

 Comments?

Perfect. Cleaning up the Dextrose patches and included them in
mainline Sugar is an excellent way of adding value:
1. The patches represent feedback from deployments in the form of
issues they felt were important enough to pay to fix.
2. The patches are often limited in their scoop due to deployment
budget restraints.
3. After a clean up, they will be available to anyone using Sugar.

 Gonzalo

 [1] http://wiki.sugarlabs.org/go/Features/Backup_and_Restore

 [2] 
 https://github.com/godiard/au1b_rpms/blob/master/sugar/0001-Backup-and-Restore-to-a-mounted-device.patch

 [3] 
 https://github.com/godiard/au1b_rpms/blob/master/sugar/0001-Fix-backup-restore-functionality-SL-4616.patch

 [4] http://wiki.sugarlabs.org/go/File:Backup_usb_menu.png

 [5] http://wiki.sugarlabs.org/go/File:Backup_before.png

 [6] http://wiki.sugarlabs.org/index.php?title=0.100/Testing
 ___
 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] seeking help to enable nepali keyboard input for XO-4

2013-11-11 Thread Basanta Shrestha
I made the changes but how do we set the key combination to invoke the
nepali layout. We need to have english as default and then nepali as and
when required.
-Basanta



On Mon, Nov 11, 2013 at 5:03 AM, James Cameron qu...@laptop.org wrote:

 On Sun, Nov 10, 2013 at 11:08:18AM +0545, Basanta Shrestha wrote:
  But I am still wondering how we could alter/change the stored data
  to our preference or if we can do it ourselves. Please suggest.

 At the firmware ok prompt [1], you may change the tag values [2], for
 example;

 ok tags(
 ok delete-tag KL
 ok add-tag KL np
 ok delete-tag KV
 ok add-tag KV olpc2
 ok )tags

 The )tags command will force a reboot.

 If you need to scale up this change to many laptops, contact
 reu...@laptop.org or myself.  I must know the SKU number.

 References:

 1.  http://wiki.laptop.org/go/Ok
 2.
 http://wiki.laptop.org/go/Manufacturing_Data_Specification#Defined_Tags

 --
 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] seeking help to enable nepali keyboard input for XO-4

2013-11-11 Thread Basanta Shrestha
D


On Mon, Nov 11, 2013 at 11:23 PM, Daniel Drake d...@laptop.org wrote:

 On Sun, Nov 10, 2013 at 5:18 PM, James Cameron qu...@laptop.org wrote:
  If you need to scale up this change to many laptops, contact
  reu...@laptop.org or myself.  I must know the SKU number.

 In the particular case of changing language/keyboard defaults as we
 are discussing, instead of changing manufacturing data I would
 recommend doing it via olpc-os-builder, configuration for [base], see

 http://dev.laptop.org/git/projects/olpc-os-builder/tree/modules/base/README#n46


Doing it via olpc-os-builder would be easier especially when we be having
more than 200 laptops to work on. This way we won't have to deal with each
and every laptop. So the lines I would have to add would be following :

[base]
default_language=us

default_kbd_model=us
default_kbd_layout=us
default_kbd_variant=np


But where do we set the key combination to switch between default and
nepali. I would like to assign alt+space or alt+shift as combination.

Note: We need to set default layout to english. Nepali input is only
required for few activities in Epaath and for typing document in Nepali.

-basanta
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Few sugar activities crashes

2013-11-11 Thread Basanta Shrestha
On Mon, Nov 11, 2013 at 4:40 AM, Gonzalo Odiard gonz...@laptop.org wrote:

 You should check where are you getting the list of activities and versions.

 In the file  olpc-os-13.2.0-xo4.ini you have a section:

 [sugar_activity_group]
 url=http://wiki.laptop.org/go/Activities/G1G1


The activities that get installed doesn't match the version shown on above
link. I wonder why.



 this url points to a page with the activities and versions to download.

 If you want try, I am working with a cloned repository
 https://github.com/godiard/olpc-os-builder/tree/v7.0
 with the last version of sugar, many activities updates,
 and a few changes implemented for the Australia deployment.

 Gonzalo


Yes I am giving it a try.



 On Sun, Nov 10, 2013 at 5:56 AM, Basanta Shrestha
 basanta.shres...@olenepal.org wrote:
  HI,
  On my 13.2.0 build, few activities like peppy, write, terminal doesn't
 work.
 
  When I uninstall the default version of terminal ( version 41) and
 install
  terminal-40.xo, it works.  But when I try to generate image by putting
  version 40 under
 /usr/share/doc/olpc-os-builder-7.0.0/examples/activities/
  it doesn't install.
 
  I always use olpc-os-builder --cache-only olpc-os-13.2.0-xo4.ini. I was
  wondering will removing --cache-only in the above command will look for
 new
  terminal version and solve the issue?
 
  Or is there a way to exclude installing some sugar activities through
  olpc-os.13.2.0.xo4.ini file ? so that I can test and install the ones
 that
  works?
 
  Please suggest.
 
  Regards,
  Basanta Shrestha
 
  ___
  Sugar-devel mailing list
  Sugar-devel@lists.sugarlabs.org
  http://lists.sugarlabs.org/listinfo/sugar-devel
 




-- 
Basanta Shrestha
Network Engineer
Open Learning Exchange (OLE) Nepal
Tel: +977.1.551, 5520075 Ext. 303
Cell: +977.9818 605110
http://www.olenepal.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Few sugar activities crashes

2013-11-11 Thread James Cameron
On Tue, Nov 12, 2013 at 11:25:22AM +0545, Basanta Shrestha wrote:
 On Mon, Nov 11, 2013 at 4:40 AM, Gonzalo Odiard gonz...@laptop.org wrote:
  You should check where are you getting the list of activities and
  versions.
  In the file  olpc-os-13.2.0-xo4.ini you have a section:
 
[sugar_activity_group]
url=http://wiki.laptop.org/go/Activities/G1G1

 The activities that get installed doesn't match the version shown on
 above link. I wonder why.

Cache between you and our web server?
Try this instead:

url=http://wiki.laptop.org/index.php?title=Activities/G1G1

(I have not tried this.)

-- 
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] seeking help to enable nepali keyboard input for XO-4

2013-11-11 Thread Basanta Shrestha
The laptops(XO-4) have arrived but it turns out the keyboard is the other
one the rubber one (Improved Membrane Keyboard ?).
-Basanta


On Tue, Nov 12, 2013 at 10:36 AM, Basanta Shrestha 
basanta.shres...@olenepal.org wrote:

 D


 On Mon, Nov 11, 2013 at 11:23 PM, Daniel Drake d...@laptop.org wrote:

 On Sun, Nov 10, 2013 at 5:18 PM, James Cameron qu...@laptop.org wrote:
  If you need to scale up this change to many laptops, contact
  reu...@laptop.org or myself.  I must know the SKU number.

 In the particular case of changing language/keyboard defaults as we
 are discussing, instead of changing manufacturing data I would
 recommend doing it via olpc-os-builder, configuration for [base], see

 http://dev.laptop.org/git/projects/olpc-os-builder/tree/modules/base/README#n46


 Doing it via olpc-os-builder would be easier especially when we be having
 more than 200 laptops to work on. This way we won't have to deal with each
 and every laptop. So the lines I would have to add would be following :

 [base]
 default_language=us

 default_kbd_model=us
 default_kbd_layout=us
 default_kbd_variant=np


 But where do we set the key combination to switch between default and
 nepali. I would like to assign alt+space or alt+shift as combination.

 Note: We need to set default layout to english. Nepali input is only
 required for few activities in Epaath and for typing document in Nepali.

 -basanta





-- 
Basanta Shrestha
Network Engineer
Open Learning Exchange (OLE) Nepal
Tel: +977.1.551, 5520075 Ext. 303
Cell: +977.9818 605110
http://www.olenepal.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Few sugar activities crashes

2013-11-11 Thread Basanta Shrestha
On Mon, Nov 11, 2013 at 4:40 AM, Gonzalo Odiard gonz...@laptop.org wrote:

 You should check where are you getting the list of activities and versions.

 In the file  olpc-os-13.2.0-xo4.ini you have a section:

 [sugar_activity_group]
 url=http://wiki.laptop.org/go/Activities/G1G1

 this url points to a page with the activities and versions to download.

 If you want try, I am working with a cloned repository
 https://github.com/godiard/olpc-os-builder/tree/v7.0
 with the last version of sugar, many activities updates,
 and a few changes implemented for the Australia deployment.

 Abacus-53.xo is breaking.

 Gonzalo


 On Sun, Nov 10, 2013 at 5:56 AM, Basanta Shrestha
 basanta.shres...@olenepal.org wrote:
  HI,
  On my 13.2.0 build, few activities like peppy, write, terminal doesn't
 work.
 
  When I uninstall the default version of terminal ( version 41) and
 install
  terminal-40.xo, it works.  But when I try to generate image by putting
  version 40 under
 /usr/share/doc/olpc-os-builder-7.0.0/examples/activities/
  it doesn't install.
 
  I always use olpc-os-builder --cache-only olpc-os-13.2.0-xo4.ini. I was
  wondering will removing --cache-only in the above command will look for
 new
  terminal version and solve the issue?
 
  Or is there a way to exclude installing some sugar activities through
  olpc-os.13.2.0.xo4.ini file ? so that I can test and install the ones
 that
  works?
 
  Please suggest.
 
  Regards,
  Basanta Shrestha
 
  ___
  Sugar-devel mailing list
  Sugar-devel@lists.sugarlabs.org
  http://lists.sugarlabs.org/listinfo/sugar-devel
 




-- 
Basanta Shrestha
Network Engineer
Open Learning Exchange (OLE) Nepal
Tel: +977.1.551, 5520075 Ext. 303
Cell: +977.9818 605110
http://www.olenepal.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel