[Sugar-devel] Activity Updates

2016-03-27 Thread Utkarsh Tiwari
Hello,
   I have now sugarized all of my activities' icons and fixed some
of their bugs. Please review them and share your suggestions.

link - http://activities.sugarlabs.org/en-US/sugar/users/info/13555

Thank you,
Utkarsh Tiwari
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Iconify sugar icons

2016-03-27 Thread Dave Crossland
On 26 March 2016 at 10:04, Utkarsh Tiwari 
wrote:

> Sir I didn't get you?
>

He meant he edited the SVG by hand in a text editor, in this case emacs
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Updating activities (and Sugar)

2016-03-27 Thread James Cameron
On Sun, Mar 27, 2016 at 04:34:08PM -0400, Chris Leonard wrote:
> So, back in the day, there were two PO files in a grouping on Pootle I
> had named "OLPC Software".  They were things related to Sugar, but
> were more-or-less unique to running it on XO laptops:
> 
> 1)
> 
> olpc_switch_desktop.pot contains the strings for switching between
> Sugar and Gnome on an XO.
> 
> This corresponds to this package in the 13.2.7 build:
> olpc-switch-desktop-0.9.2-1.olpc.noarch
> 
> olpc-switch-desktop repo is at:
> http://dev.laptop.org/git/projects/olpc-switch-desktop/
> 
> I recovered the strings we had from the old Pootle backups and loaded
> them on the current Pootle server, adding additional languages we may
> want.
> 
> http://translate.sugarlabs.org/projects/OLPC_switch_desktop/
> 
> We'll eventually recover our Pootle-repo connections, and I will work
> with Quozl to make sure it works (in due time); but at least for now
> we are collecting strings again against the next release (technically
> the next packaging, I guess).  New XO deployments (or re-deployments)
> will want these strings in their own language.
> 
> 2)
> 
> There is one other PO file called sugar-update-control.pot, that I am
> trying to figure out and I wanted your help.  As I recall, this was
> the strings for updating activities and also Sugar (see attached POT
> file for the strings).  I honestly don't know if we are still using
> them anymore or if updating happens in some other way.  I can't seem
> to find the repo (or package listed in the 13.2.7 build) for a
> certainty.
> 
> I find these packages on Fedora:
> 
> >From 0,20 - 0,23
> http://pkgs.fedoraproject.org/repo/pkgs/sugar-update-control/
> 
> and there is this package in the 13.2.7 build (see attached package
> inventory, from an XO-4 example):
> 
> olpc-update-2.29-1.fc18.noarch
> http://dev.laptop.org/git/projects/olpc-update/

olpc-update is an operating system updater, similar to ostree.

Since the activities on an XO are in the /home directory, they are not
affected by an olpc-update.

> but it does not seem to have any strings (no po folder) in the repo.
> I have recovered the old PO files for the sugar-update-control
> package, but I wanted some questions answered before I post them on
> Pootle again.
> 
> 
> So here are my questions:
> 
> 1) Does a Sugar user on an XO need the sugar-update-control package
> to update?

No.  Sugar has an updater built-in.  sugar:src/jarabe/model/update

The built-in updater updates _only_ activities, not Sugar itself, and
has several backends.

On the XO we use the microformat backend, with the URL pointing at the
OLPC Wiki.  e.g. http://wiki.laptop.org/go/Activities/13.2.7

We set the URL in
http://dev.laptop.org/git/projects/olpc-os-builder/tree/modules/sugar_activity_group/kspost.60.activities.py?h=v7.0

> 2) Does a Sugar user not on an XO need this?

No.  Sugar not on an XO uses either native packaging of activities,
or the built-in updater.  For my builds, the built-in updater is
pointing at an empty file on our servers, just in case we need it.

Martin did work on a native packaging updater backend, but that isn't
merged yet.

> 3) If needed on an XO, why is it not in the 13.2.7 build, i.e. does it
> serve a function distinct from olpc-update-2.29-1.fc18.noarch? Am I
> missing something here?
> 
> 4) Where is the repo for sugar-update-control?

No idea.  But I don't need it on XO or non-XO.  Can't remember needing
it.

A quick search of previous releases shows it was in 13.2.1 alongside
Sugar 0.98.  With the move to later Sugar, it was no longer a dependency.

> Thanks for any help you can give me in learning about this issue.  I'm
> just trying to make sure that all Sugar users get the all strings they
> need to have a fully localized learning experience, but I have lost
> touch with some of the technical details so I appreciate any time you
> might take to investigate this matter and relieve me of my ignorance.
> 
> regards,
> 
> cjl

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


[Sugar-devel] Updating activities (and Sugar)

2016-03-27 Thread Chris Leonard
So, back in the day, there were two PO files in a grouping on Pootle I
had named "OLPC Software".  They were things related to Sugar, but
were more-or-less unique to running it on XO laptops:

1)

olpc_switch_desktop.pot contains the strings for switching between
Sugar and Gnome on an XO.

This corresponds to this package in the 13.2.7 build:
olpc-switch-desktop-0.9.2-1.olpc.noarch

olpc-switch-desktop repo is at:
http://dev.laptop.org/git/projects/olpc-switch-desktop/

I recovered the strings we had from the old Pootle backups and loaded
them on the current Pootle server, adding additional languages we may
want.

http://translate.sugarlabs.org/projects/OLPC_switch_desktop/

We'll eventually recover our Pootle-repo connections, and I will work
with Quozl to make sure it works (in due time); but at least for now
we are collecting strings again against the next release (technically
the next packaging, I guess).  New XO deployments (or re-deployments)
will want these strings in their own language.

2)

There is one other PO file called sugar-update-control.pot, that I am
trying to figure out and I wanted your help.  As I recall, this was
the strings for updating activities and also Sugar (see attached POT
file for the strings).  I honestly don't know if we are still using
them anymore or if updating happens in some other way.  I can't seem
to find the repo (or package listed in the 13.2.7 build) for a
certainty.

I find these packages on Fedora:

>From 0,20 - 0,23
http://pkgs.fedoraproject.org/repo/pkgs/sugar-update-control/

and there is this package in the 13.2.7 build (see attached package
inventory, from an XO-4 example):

olpc-update-2.29-1.fc18.noarch
http://dev.laptop.org/git/projects/olpc-update/

but it does not seem to have any strings (no po folder) in the repo.
I have recovered the old PO files for the sugar-update-control
package, but I wanted some questions answered before I post them on
Pootle again.


So here are my questions:

1) Does a Sugar user on an XO need the sugar-update-control package to update?

2) Does a Sugar user not on an XO need this?

3) If needed on an XO, why is it not in the 13.2.7 build, i.e. does it
serve a function distinct from olpc-update-2.29-1.fc18.noarch? Am I
missing something here?

4) Where is the repo for sugar-update-control?

Thanks for any help you can give me in learning about this issue.  I'm
just trying to make sure that all Sugar users get the all strings they
need to have a fully localized learning experience, but I have lost
touch with some of the technical details so I appreciate any time you
might take to investigate this matter and relieve me of my ignorance.

regards,

cjl
aalib-libs-1.4.0-0.21.rc5.fc18.armv7hl
abattis-cantarell-fonts-0.0.10.1-1.fc18.noarch
abiword-2.9.3-1.git20121011.fc18.olpc12.armv7hl
adwaita-cursor-theme-3.6.5-1.fc18.noarch
adwaita-gtk2-theme-3.6.5-1.fc18.armv7hl
adwaita-gtk3-theme-3.6.5-1.fc18.armv7hl
agg-2.5-13.fc17.armv7hl
aiksaurus-1.2.1-26.fc18.armv7hl
alsa-lib-1.0.26-2.fc18.armv7hl
alsa-utils-1.0.26-1.fc18.armv7hl
atk-2.6.0-1.fc18.armv7hl
atkmm-2.22.6-2.fc18.armv7hl
atlas-3.8.4-7.fc18.armv7hl
at-spi2-atk-2.6.2-1.fc18.armv7hl
at-spi2-core-2.6.3-1.fc18.armv7hl
audacity-2.0.4-2.fc18.armv7hl
audit-libs-2.3.2-1.fc18.armv7hl
avahi-0.6.31-6.fc18.armv7hl
avahi-autoipd-0.6.31-6.fc18.armv7hl
avahi-glib-0.6.31-6.fc18.armv7hl
avahi-gobject-0.6.31-6.fc18.armv7hl
avahi-libs-0.6.31-6.fc18.armv7hl
avahi-tools-0.6.31-6.fc18.armv7hl
babl-0.1.10-4.fc18.armv7hl
basesystem-10.0-7.fc18.noarch
bash-4.2.45-1.fc18.armv7hl
bind-libs-lite-9.9.3-7.P2.fc18.armv7hl
bind-license-9.9.3-7.P2.fc18.noarch
bitfrost-1.0.19-1.fc18.armv7hl
blueman-1.23-5.fc18.armv7hl
bluez-4.101-6.fc18.armv7hl
bluez-libs-4.101-6.fc18.armv7hl
boost-chrono-1.50.0-7.fc18.armv7hl
boost-date-time-1.50.0-7.fc18.armv7hl
boost-iostreams-1.50.0-7.fc18.armv7hl
boost-program-options-1.50.0-7.fc18.armv7hl
boost-serialization-1.50.0-7.fc18.armv7hl
boost-system-1.50.0-7.fc18.armv7hl
boost-thread-1.50.0-7.fc18.armv7hl
bzip2-1.0.6-7.fc18.armv7hl
bzip2-libs-1.0.6-7.fc18.armv7hl
ca-certificates-2013.1.95-1.fc18.noarch
cairo-1.12.14-2.fc18.armv7hl
cairo-gobject-1.12.14-2.fc18.armv7hl
cairomm-1.10.0-5.fc18.armv7hl
cdparanoia-libs-10.2-12.fc18.armv7hl
celt-0.11.1-4.fc18.armv7hl
chkconfig-1.3.59-2.fc18.armv7hl
colord-libs-1.0.5-1.fc18.armv7hl
control-center-filesystem-3.6.3-2.fc18.armv7hl
coreutils-8.17-8.fc18.armv7hl
cpio-2.11-12.fc18.armv7hl
cracklib-2.8.22-2.fc18.armv7hl
cracklib-dicts-2.8.22-2.fc18.armv7hl
crda-1.1.3_2013.02.13-2.fc18.armv7hl
cryptsetup-1.6.3-1.fc18.armv7hl
cryptsetup-libs-1.6.3-1.fc18.armv7hl
csound-5.13.0-9.fc18.armv7hl
csound-python-5.13.0-9.fc18.armv7hl
cups-libs-1.5.4-28.fc18.armv7hl
curl-7.27.0-12.fc18.armv7hl
cyrus-sasl-lib-2.1.23-37.fc18.armv7hl
dbus-1.6.12-1.fc18.armv7hl
dbus-glib-0.100-3.fc18.armv7hl
dbus-libs-1.6.12-1.fc18.armv7hl
dbus-python-1.1.1-3.fc18.armv7hl
dbus-x11-1.6.12-1.fc18.armv7hl
dconf-0.14.1-3.fc18.armv7hl
dejavu-fonts-common-2.33-4.fc18.noarch
dejavu-s