[Sugar-devel] Technical Release - Sugar 0.110

[Sam P.]

Hi All,

It has been a huge cycle and there has been lots of great work done by many
members of this community.  One sum of that work is the Sugar 0.110
release.  Tonight I will be doing the technical side of the release -
tarballs only.  I'd like to take my time to properly summarize the
contributions that have made this release possible; so you will have to
wait for that.

This includes the following components: sugar, sugar-toolkit-gtk3,
sugar-toolkit, sugar-runner, sugar-datastore, sugar-artwork

Please find the tarballs on download.sugarlabs.org in the usual places.
This is a great time if you are fedora or another distro to pick up the
changes!

We also have updated developer docs, just on the off chance that somebody
wants to make a sugar activity:  https://developer.sugarlabs.org/sugar3/

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

[Sugar-devel] Release Sugar 0.109.2

[Sam P.]

Hi All,

This is this release of Sugar 0.109.2, a feature, string, api and UI frozen
version on the road to 0.110.

Please find the tarballs on download.sugarlabs.org in the usual places.
Note that there are tarballs for only the following modules:  sugar,
sugar-toolkit-gtk3,
sugar-toolkit.  There is no sugar-artwork or sugar-datastore release this
time, please use the latest unstable releases of those components.
Currently, the only full release (of all components) I plan to do is 0.110.

Thank you to everybody who has contributed to this release specifically
(@Quozl and @Icarito), as well as everybody who has helped on the road so
far to 0.110.

If there is any more things that need to be done to facilitate the
successful translation of this release, please let me know.

Thanks,
Sam

Links:

https://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.109.2.tar.xz
https://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.109.2.tar.bz2
https://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.109.2.tar.xz

To be used in conjunction with:

https://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.109.0.3.tar.xz
https://download.sugarlabs.org/sources/sucrose/glucose/sugar-runner/sugar-runner-0.108.1.tar.xz
https://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.109.0.3.tar.xz
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Release 0.109.0.3 unstable

[Sam P.]

Hi All,

Today I have released 0.109.0.3 unstable for sugar, sugar-artwork,
sugar-toolkit-gtk3 and sugar-artwork.  The tarballs are in the usual places
on download.sugarlabs.org.  And as always, the COPR is the easiest way to
access the builds on fedora:
https://copr.fedorainfracloud.org/coprs/samtoday/sugar/

What has happened this release?

* Abhijit's Project Based Journal view is introduced.
* Many, many quality patches from James Cameron
* Ported sugar shell to WebKit2

Feedback and bug reports are always appreciated.

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

Re: [Sugar-devel] Thoughts on Collab

[Sam P.]

Looking great.  I will test it very soon, but the code looks nice.

We probably now need to look at activity collab.  I was thinking that we
have a leader, and everybody connects to the leader.  The connection
protocol could be zeromq or whatever you think is best.  We need to have
authentication so that only invited people can join the activity (unless it
is public) - this would be part of the "leader"s server code.  Otherwise
the server would just re-broadcast incoming messages to everybody else.
The server could just run inside the activity process.  It would be best if
the "server" could be subclasses by activities - eg. to implement text
editing algorithms.

Encryption would also be useful.  I think there is something called CurveMQ
which adds encryption to ZeroMQ, but you can investigate that.

What do you think about that?

Thanks,
Sam

On Fri, Jul 29, 2016 at 9:54 AM, Abhijit Patel <abhisandhyasp...@gmail.com>
wrote:

> Hi all,
> I have implemented the neighborhood view using Avahi instead of telepathy.
> Here, all the buddies that are connected to the same port are shown in
> neighborhood view.
>
> Whenever buddy gets connected he adds a service to an EntryGroup which is
> discovered by all buddies(including the ones that are connected later) and
> hence buddy is added to neighborhood.
>
> And when buddy gets disconnected the service started by that buddy is
> stopped and hence removed from the ServiceBrowser this emits a signal
> "ItemRemove" which is received by other buddies and hence buddy
> disconnected is removed from the neighborhood view.
>
> I have used profile.pub_key  to overcome the issue of duplicate buddies.
>
> You could test my code[1] and review it and even a few suggestions that
> pops up in your mind :)
> [1] https://goo.gl/PBWy08
>
> Regards,
> Abhijit
> On 27 July 2016 at 21:30, <sugar-devel-requ...@lists.sugarlabs.org> wrote:
>
>> Send Sugar-devel mailing list submissions to
>> sugar-devel@lists.sugarlabs.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>> or, via email, send a message with subject or body 'help' to
>> sugar-devel-requ...@lists.sugarlabs.org
>>
>> You can reach the person managing the list at
>> sugar-devel-ow...@lists.sugarlabs.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Sugar-devel digest..."
>>
>>
>> Today's Topics:
>>
>>1. Re: Thoughts on Collab (Dave Crossland)
>>2. Re: Thoughts on Collab (Sebastian Silva)
>>
>>
>> ----------
>>
>> Message: 1
>> Date: Tue, 26 Jul 2016 19:16:30 -0400
>> From: Dave Crossland <d...@lab6.com>
>> To: Sebastian Silva <sebast...@fuentelibre.org>
>> Cc: sugar-devel <sugar-devel@lists.sugarlabs.org>, "Sam P."
>> <sam.parkins...@gmail.com>
>> Subject: Re: [Sugar-devel] Thoughts on Collab
>> Message-ID:
>> <CAEozd0zY5ve1YOnOdsV7fhkpWcyrD+h3mkL-xDE=YMUex8cT=
>> w...@mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>>
>> On Jul 26, 2016 4:12 PM, "Sebastian Silva" <sebast...@fuentelibre.org>
>> wrote:
>> >
>> > El 26/07/16 a las 14:05, Dave Crossland escribió:
>> >>
>> >>
>> >> On Jul 26, 2016 2:36 PM, "Sebastian Silva" <sebast...@fuentelibre.org>
>> wrote:
>> >> >
>> >> > El 26/07/16 a las 13:08, Dave Crossland escribió:
>> >> >>
>> >> >> Despite my suggestion to look at zeromq, I think we should be using
>> the collaboration protocols that Lionel is using in Sugarizer, so that
>> someone running Sugar desktop and someone using Sugarizer on a Chromebook
>> (for example, 2 kids in a family at home who attend 2 different schools
>> that have different hardware purchasing decisions ;) could collaborate.
>> >> >
>> >> > It's not a dichotomy.
>> >> >
>> >> > If two users use the same app [and it supports collaboration] - it
>> should just work regardless of the environment where they are run.
>> >> >
>> >> > Much like running etherpad @ titanpad.
>> >>
>> >> I mean to propose a requirement for any new collaboration system that
>> is
>> recommended to all sugar developers be that it support collaboration
>> between a python paint application and a Javascript paint a

Re: [Sugar-devel] MIME type?

[Sam P.]

Hi Sebastian,

We have Sphinx docs avbaliable online:
https://developer.sugarlabs.org/sugar3/

Contributions to add more docstrings are always appreciated.

Thanks,
Sam

On Wed, Jun 22, 2016, 04:53 Sebastian Silva 
wrote:

> El 21/06/16 a las 13:32, Gonzalo Odiard escribió:
>
> > (btw, would be good have this information in a official place)
> +1 in fact the Sugar Toolkit API docs are not online. Aleksey used to
> maintain a website for them. Also, recently Tony complained that there's
> no toolkit docs.
>
> I don't know how those were generated (epydocs?). They were not pretty
> but worked.
> ___
> 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] [IAEP] Go Social via Social Media (Proposal/Motion)

[Sam P.]

Sean, I completely agree with everything you said.  We seem to have such a
leaky conversion funnel that advertising and social media would be a waste
of money anyway.  You are 100% right that content is key now.

Thanks,
Sam

On Thu, Jun 9, 2016, 19:41 Sean DALY  wrote:

> I'm sorry, I don't see how SL can support a new paid position. My
> suggestion would be to evaluate how the paid Translation Manager position
> works out.
>
> I'm glad Samson you are eager to work on social media (as I've said),
> however I don't understand your marketing objectives. Put another way, just
> what content, from where, will generate lots of likes and clicks, towards
> what goal? I think the goal is developer recruitment, not for teachers or
> education IT buyers, or small donors, or major donors. If they matter too,
> do we use the same plan and tactics for them?
>
> As I've said, I am opposed to associating random advertising with Sugar
> Labs for negligeable income. We should really do Google AdGrants. This can
> be done in cooperation with the SFC which is the nonprofit entity which
> will qualify (and Dave - we shouldn't try to control their account for
> this).
>
> I am pleased there is motivation to work on PR, however major media tech
> sites won't publish anything about us unless we have news, and right now we
> don't. (Ifeanyi - it's not the case that buying ads from news sites will
> generate coverage, that's not how journalists work.)
>
> I'm not comfortable with the idea of creating a Facebook-only version of
> Sugarizer (? if there are resources to do so?) - as fun and ubiquitous as
> fb is, it's a proprietary environment with highly questionable privacy
> policies. It's already possible to link to a public website from Facebook,
> this would be far better.
>
> The previous times I have raised these points they haven't been answered.
> Perhaps the time has come for me to step away from Marketing/PR at SL and
> let you guys reinvent the wheel.
>
> Sean
>
>
> On Tue, Jun 7, 2016 at 11:11 PM, Dave Crossland  wrote:
>
>> [ Here is the full text of the doc, by Samson with editing assistance
>> by myself ]
>>
>> Concerning SL vision 2016, I think that SL should add social media as
>> one of our main ways to get new members. With the big name we have, we
>> should use that as an advantage to get people into our community - but
>> we aren’t.
>>
>> Let me use myself as an example, I am a very active user in the social
>> world (facebook, twitter, instagram, and YouTube) even though I don’t
>> have a smartphone or a laptop of my own to use regularly. I have over
>> 560 followers on twitter. According to twitter official report, my
>> tweets receive more than 1.9k impressions per day. For the past 28
>> days I have gotten over 42.4k impressions. My lowest impression is
>> about 50 on a tweet. My highest tweet is about 4,800 on a tweet. Now
>> imagine if SL can get this number of impressions by activeness alone
>> on twitter. Same goes to facebook, also posting images on instagram.
>> We can get more than 400 impressions a day via twitter, Also facebook
>> and instagram. If we do the math correctly, SL can get over 600 people
>> a day from social media to sugarlabs.org. That’s valuable traffic for
>> our sites.
>>
>>
>> How do we get started with this new development?
>>
>>
>> It’s very simple; I propose the following motion:
>>
>>
>> Motion: create a “Social Media Manager,” role, similar to the
>> translation manager position, paid $1,000/month plus discretionary use
>> of an advertising budget of $100/month.
>>
>>
>> I believe that the role will not be taken seriously if it is volunteer
>> driven. I am in charge of the social accounts of my church,another
>> non-profit organization. Their social media marketing was also not
>> taken seriously until the church made a modestly paid role. The church
>> community and I both saw it as a responsibility when the role was
>> paid; and my work was effective, as now we have over 4,000 followers
>> on facebook.
>>
>>
>> Money should be spent in order to gain more. More social media
>> followers will lead to more active members which will lead to member
>> donations. I know it’s a non-profit organization but that does not
>> mean we shouldn’t grow.
>>
>> To get my contract approved by SLOBs. I spent almost 100 USD (21,000
>> naira) in cyber cafes answering questions that were not related to my
>> project, so if anyone does not understand this proposal, I strongly
>> suggest they make research on the internet first before asking
>> questions, because I will not answer if the questions are not
>> relevant.
>>
>>
>> I believe in the growth of SL, but I think we can’t grow big if we are
>> not doing well on social media. Even if I am not experienced in
>> business, based on the fact that I am still young and not yet a
>> college graduate, this seems essential to any non-profit business. I
>> always thank God for Nigeria because even if the government 

Re: [Sugar-devel] The future of Sugar on XO-1s

[Sam P.]

On 30 May 2016 12:36:37 PM AEST, Dave Crossland  wrote:
>Hi
>
>I want to return to this older thread because of James Cameron's
>comment in
>https://github.com/sugarlabs/sugar/pull/688#issuecomment-222393275 :
>
>On the assumption that Sugar Labs is dropping support for XO-1, I'll
>close
>this pull request. Thanks for your time!
>
>
>But I understood from Tony and Adam in this thread that Sugar Labs
>_should_
>keep support for the XO-1 as a goal. Adam said,
>
>In Haiti XO-1s will be dominant across many schools for years and year
>to
>come.  Similar to Tony's description, but these typically will be using
>32GB SD cards -- thankfully these are incredibly affordable. The
>resilience/repairability of the XO-1 laptops is the absolutely
>fascinating
>part.
>
>
>I think this goal is wise because it ensures that Sugar runs well on
>the
>cheapest computers - like the $10 getchip.com/pages/pocketchip and $5
>https://www.raspberrypi.org/blog/raspberry-pi-zero - and ensures
>performance is only better on later XO models and 'regular'
>desktops/laptops.

Making sure sugar runs well on slow computers is an important goal.  Android 
runs fast on everything, and it has tonnes of pretty animations even.  Making 
sugar fast on every device doesn't limit us at all - let's keep on doing it.

Supporting XO1s is more than just performance though.  XOs don't run normal, up 
to date versions of fedora.  This means we must keep workarounds and redundant 
code to support ancient library versions.  This is the biggest issue with 
maintaining support - XOs aren't "normal" commodity hardware.

>
>I edited https://wiki.sugarlabs.org/go/Vision_proposal_2016 to reflect
>this.
>
>Cheers
>Dave
>
>
>On 5 April 2016 at 17:04, James Cameron  wrote:
>
>> On Tue, Apr 05, 2016 at 07:37:45AM -0400, Dave Crossland wrote:
>> >
>> > Hi James
>> >
>> > On 1 April 2016 at 15:06, James Cameron <[1]qu...@laptop.org>
>wrote:
>> >
>> > Let me spin you a tail.
>> >
>> > The myth of forward human development doesn't apply to
>software.
>> >
>> > This is a parade of people, several walking abreast, beside a
>slow
>> > moving flat bed truck, all holding on to a ribbon.
>> >
>> > The truck is the world, and the internet as it stands.
>> >
>> > The first person, next to the truck, are our learners or users.
>> >
>> > The second person is Sugar Labs; with our activities, and
>Sugar.
>> >
>> > The third person is distributions of Linux, like Fedora and
>Ubuntu,
>> >
>> > The fourth person are the hardware vendors, like commodity
>suppliers
>> > or OLPC.
>> >
>> > The fifth person are the Linux kernel developers.
>> >
>> > As the procession walks beside the truck, the ribbon is not
>always
>> > straight.
>> >
>> > Some people walk faster than others.  Some let go of the ribbon
>and
>> > others take their place.
>> >
>> > I'm glad you're here, you're bringing a new perspective.
>> >
>> > But the ribbon is actually toilet paper, so the pressure to
>keep up,
>> > while real, doesn't get felt, instead the paper breaks.
>> >
>> > Do not target a rapidly diminishing enthusiastic group, or the
>future
>> > users will suffer.
>> >
>> > I'm sorry, I didn't fully understand you here at the last line. You
>had
>> said
>> > earlier,
>> >
>> > > for the future of Sugar Labs, they should be concentrating on
>> > > later designs than one from 2007 that is no longer available
>and
>> > > rapidly dying from old age.
>> >
>> > So you mean, it would be unwise for Sugar Lab's
>vision/mission/strategy
>> for the
>> > next 3-5 years to focus on supporting the rapidly diminishing (yet
>> > enthusiastic) group of XO owners, and focus on the future users who
>are
>> not XO
>> > owners?
>>
>> You might target this group of XO-1 owners and become a closed
>> community into which all communications are judged against
>suitability
>> for the majority (which would then be XO-1 owners).
>>
>> It would feel good!  [warning, sarcasm in this paragraph]
>>
>> I'm loath to battle the laws of physics, 'cause I know who wins.
>>
>> --
>> James Cameron
>> http://quozl.netrek.org/
>>

-- 
Sent from my phone. Please excuse my brevity.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar 0.110 Release Cycle

[Sam P.]

Hi Thomas,

Thanks for testing!  The copr doesn't include activities yet.  If any activity 
authors want their activities in the copr, please send me tarballs (and 
probably send them to Peter Robinson as well so that they get into rawhide).

Thanks,
Sam

On 6 June 2016 8:02:12 AM AEST, Thomas Gilliard  wrote:
>I have the copr installed in f24 workstation with a sugar-desktop 
>installed (0.108)
>I see sugar 0.109 after dnf update and reboot.
>
>  dnf copr enable samtoday/sugar
>
>  dnf update
>
>
>Observations:
>
>Does chat 81 now work? (I did not need to make a friend in f2 to enter
>text)
>jabber.sugarlabs.org is still listed as server

That change of server patch will be in the next release.

>help 62 is for sugar 0.106
>irc 12 works but still renders the user list as a double list
>Browse 157.3 and terminal  44 work
>I can copy a journal entry to the Documents folder shown on the frame
>(more to follow)
>
>Very Nice
>Thanks
>
>Tom Gilliard
>satellit
>
>Look at this wiki page [ 1 ] for ways to build a live.cd
>  I wonder if the copr could be used in the flattened kickstart file

+1.

>
>[ 1 ] 
>https://wiki.sugarlabs.org/go/Build_Your_Own_Remix_with_Fedora#livemedia-creator
>
>On 05/26/2016 04:53 PM, sam@sam.today wrote:
>> Hi All,
>>
>> I will be doing the release management for the 0.110 cycle.  Please 
>> see the timeline [1]. I would appreciate any comments on the
>timeline.
>> I've also setup a COPR for sugar, which I hope to maintain throughout
>
>> this cycle. Are there any other packaging services that we should
>have 
>> to push testing releases to? Is there a service for automatic
>building 
>> of live SoaS images? XO images? /Let's make this the most tested
>sugar 
>> release ever!/
>> Thanks,
>> Sam
>> [1] https://wiki.sugarlabs.org/go/0.110/Roadmap
>>
>>
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel

-- 
Sent from my phone. Please excuse my brevity.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Release Sugar 0.109.0.0

[Sam P.]

I'm not sure if it will.  Copr doesn't seem to support fedora 18 builds.

What is the best way to setup a f18 rpmbuild?  Does anybody have one?  Maybe we 
could setup our own f18 repo?

On 30 May 2016 4:47:28 PM AEST, Tony Anderson  wrote:
>Hi, Sam
>
>Does this mean that Sugar 0.109 works with Fedora 18 and that this 
>update procedure will work for an
>XO 1.75 with 0.106 installed.
>
>Tony
>
>On 05/30/2016 12:01 AM, Sam Parkinson wrote:
>>
>>
>> On Mon, May 30, 2016 at 1:55 AM, Jerry Vonau  wrote:
>>>
>>> On May 29, 2016 at 5:27 AM Sam Parkinson
>>> >
>>> wrote: Hello All, This is an unstable release, the 1st of the
>>> 0.110 development series. Tarballs are avaliable for sugar [1]
>>> and sugar-toolkit-gtk3 [2]. I'd like to thank all the
>>> contributors towards this release. There have been many new
>>> features [1] including Proxy Settings [2] (thanks to Manash
>>> Pratim Das) and running sugar activities outside sugar (thanks
>to
>>> Sebastian Silva) and overhalling favourites model (thanks to
>>> Martin Abente Lahaye). Additionally there are many smaller
>>> improvements and large bug fixes. For testing on Fedora 23,
>>> Fedora 24 or Fedora Rawhide, we have a COPR repository that you
>>> can install very quickly:
>>> https://copr.fedorainfracloud.org/coprs/samtoday/sugar/ 
>>>
>>> Cool, Thanks for implementing my suggestion, might be helpful to
>have 
>>> instructions on how to enable it.
>>
>> Hi Jerry,
>>
>> If you already have Sugar installed, you can just run the following 
>> commands:
>>
>> dnf copr enable samtoday/sugar
>> dnf update
>> And then your normal sugar version will be updated.
>>
>> Thanks,
>> Sam
>>>
>>> Please report bugs on bugs.sugarlabs.org. 
>>>
>>> Sorry I have not being paying close attention, isn't that moving?
>Jerry
>>>
>>> Thanks, Sam [1]
>>>
>http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.109.0.0.tar.xz
>>> [2]
>>>
>http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.109.0.0.tar.xz
>>> [3] https://wiki.sugarlabs.org/go/0.110/Feature_List [4]
>>> https://wiki.sugarlabs.org/go/Features/Proxy_Settings [5]
>>> https://wiki.sugarlabs.org/go/Features/FreeDesktop_integration
>>> ___ 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

-- 
Sent from my phone. Please excuse my brevity.___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] GSOC Day 3

[Sam P.]

On 27 May 2016 7:49:16 AM AEST, Abhijit Patel  
wrote:
>Hi Sam,
>I have fixed the keyboard input handler. 
>
>Icons like blocksoff.svg in turtleart are preferable. What do you
>think?

Also, this may help you:  http://wiki.sugarlabs.org/go/Sugar_iconify

>
>I am now working on metadata for projects implemented the
>initialize_journal_obj for project which will create jobject for
>projects.
>
>I'll update my branch with changes soon.
>
>Regards,
>Abhijit
>
>-Original Message-
>From: "sam@sam.today" 
>Sent: ‎26-‎05-‎2016 15:39
>To: "Abhijit Patel" 
>Cc: "sugar-devel" 
>Subject: GSOC Day 3
>
>Hello Abhijit,
>
>
>How is it going?
>
>
>Did you fix up the icon for the project view?
>
>
>Did you fix up the keyboard input handling?
>
>
>Thanks,
>Sam

-- 
Sent from my phone. Please excuse my brevity.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] GSOC Day 3

[Sam P.]

On 27 May 2016 7:49:16 AM AEST, Abhijit Patel  
wrote:
>Hi Sam,
>I have fixed the keyboard input handler. 
>
>Icons like blocksoff.svg in turtleart are preferable. What do you
>think?

Yep, that box looks nice.

>
>I am now working on metadata for projects implemented the
>initialize_journal_obj for project which will create jobject for
>projects.
>
>I'll update my branch with changes soon.

Can't wait to see it!  Let's try to beat the timeline!

>
>Regards,
>Abhijit
>
>-Original Message-
>From: "sam@sam.today" 
>Sent: ‎26-‎05-‎2016 15:39
>To: "Abhijit Patel" 
>Cc: "sugar-devel" 
>Subject: GSOC Day 3
>
>Hello Abhijit,
>
>
>How is it going?
>
>
>Did you fix up the icon for the project view?
>
>
>Did you fix up the keyboard input handling?
>
>
>Thanks,
>Sam

-- 
Sent from my phone. Please excuse my brevity.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [GSOC] Font Editor Next Steps

[Sam P.]

On 25 May 2016 8:45:53 AM AEST, Yash Agarwal  wrote:
>On Tue, May 24, 2016 at 7:18 PM Dave Crossland  wrote:
>
>> On 23 May 2016 at 18:52, Yash Agarwal  wrote:
>>
>>>
>>>- Dave, Eli could you guys make a UI mock for the character map, 
>so
>>>that I can build it tomorrow
>>>
>>>
>> I think the current plan is for a horizontal bar along the top, like
>in
>> Eli's HTML mock:
>>
>>
>>
>https://sugarlabs.github.io/edit-fonts-activity/mockups/EditFontsMockUpJS.activity/
>>
>>
>
>My aim for today was to build this, but I couldn't figure out how to
>make
>the Gtk layout, Then I decided to go through this link to gain more
>understanding about the Gtk workings and basic fundamentals, though its
>for
>Gtk 2 it explains the fundamentals quite well
>http://www.pygtk.org/dist/pygtk2-tut.pdf

You might be interested in the gtk3 version:  
https://python-gtk-3-tutorial.readthedocs.io/en/latest/

Sugar uses gtk3, and there are some differences vs gtk2.
>
>I also found this amazing list of demos
>https://git.gnome.org/browse/pygobject/tree/demos/gtk-demo/demos
>
>apart from this I also reread the FLOSS Manual to better understand the
>tasks at hand. Well thats all I did Today, and I'll hope to make a
>working
>demo the character map tomorrow.
>
>I think we will also need a table, like the TruFont one:
>>
>> https://sugarlabs.github.io/edit-fonts-activity/files/img/3.png
>>
>>
>>>- [Regarding defcon] I am having a some trouble understanding the
>>>concept behind the representation factories and notifications,
>>>
>>>
>> Please be more specific, perhaps quoting the part of the docs you are
>> unclear about :)
>>
>>
>http://ts-defcon.readthedocs.io/en/latest/concepts/representations.html
>>
>> http://ts-defcon.readthedocs.io/en/latest/concepts/notifications.html
>>
>> https://en.wikipedia.org/wiki/Observer_pattern
>>
>This was what I was looking for, thanks, Gtk also uses this
>
>>
>>
>how should I implement these in the glyphRenderer Class?
>>
>>
>> I'm not sure - what does TruFont do?
>>
>>
>>>- whats the difference between an Anchor and Point in an UFO
>file?
>>>
>>>
>> A point is a bezier point, part of a contour.
>>
>> An anchor is a 'singleton' point, used to 'snap' glyphs together
>using
>> OpenType Features (GPOS/GSUB code)
>>
>> https://glyphsapp.com/tutorials/diacritics
>>
>
>do we need to implement these in our activity?
>
>>
>>
>> https://fontforge.github.io/overview.html#Anchors
>>
>> --
>> Cheers
>> Dave
>>
>
>
>
>
>___
>Sugar-devel mailing list
>Sugar-devel@lists.sugarlabs.org
>http://lists.sugarlabs.org/listinfo/sugar-devel

-- 
Sent from my phone. Please excuse my brevity.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [GSOC] Font Editor Next Steps

[Sam P.]

Lionel - we've already discussed this before.  Python is objectively better for 
every activity; Gtk+ is more stable, has more stability, creates better code 
quality and supports collaboration.

But for the font editor world, python has even more advantages.  There are 
tonnes of libraries for font editing and none of them are for the 'JavaScript' 
language.  They are for python.

I don't think it will ever be ported to sugarizer even.  Sugatizer is just 
cheap in comparison to the smooth and feature rich sugar environment.  Who 
wants to edit fonts in a browser?

On 17 May 2016 6:32:26 AM AEST, "Lionel Laské"  wrote:
>2016-05-15 19:45 GMT+02:00 :
>
>>
>> 2. I want to keep working on learning how to make GTK mockups for
>sugar,
>> this is going a little slow for me but I'm getting there.
>>
>>
>Does it mean that you choose Python to write the activity ?
>Of course, as you could imagine, I think it's not a good idea.
>JavaScript will allow to the activity to run both on Sugar and on
>Sugarizer.
>So it's a good investment on the future.
>
> Lionel.
>
>
>
>
>___
>Sugar-devel mailing list
>Sugar-devel@lists.sugarlabs.org
>http://lists.sugarlabs.org/listinfo/sugar-devel

-- 
Sent from my phone. Please excuse my brevity.___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Python code standards?

[Sam P.]

I think that we currently use the Flake8 standard.

On 15 May 2016 2:25:28 PM AEST, Dave Crossland  wrote:
>Hi
>
>What code standards should we use today in 2016 for python code? :)
>
>Python 2.7 + PEP8?
>
>-- 
>Cheers
>Dave
>
>
>
>
>___
>Sugar-devel mailing list
>Sugar-devel@lists.sugarlabs.org
>http://lists.sugarlabs.org/listinfo/sugar-devel

-- 
Sent from my phone. Please excuse my brevity.___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] View Source Code [BROWSE]

[Sam P.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

That feature is already kind of there.  Open browse.  Then open view source 
from the frame (ctrl-shift-v probably).  The current HTML is displayed under 
"current activity source", the default tab.

Thanks,
Sam

On 5 May 2016 5:20:08 PM AEST, Utkarsh Tiwari  
wrote:
>Hi,
>I need to add the facility to view the source code of the current
>open webpage in a new tab. I tried that by fetching the source code
>using webkit and displaying it via javascript query
>'browser.execute_query('JS_Query')' but have been some problems while
>parsing the html code to string.
>
>Could anyone here suggest any other possible way to get about it?
>
>Thanks,
>Utkarsh Tiwari
>___
>Sugar-devel mailing list
>Sugar-devel@lists.sugarlabs.org
>http://lists.sugarlabs.org/listinfo/sugar-devel

- --
Sent from my phone. Please excuse my brevity.
-BEGIN PGP SIGNATURE-
Version: APG v1.1.1

iQJOBAEBCgA4BQJXK7OlMRxTYW0gUC4gKE1vYmlsZSBOZXh1cyA0IEN5YW5vZ2Vu
KSA8c2FtQHNhbS50b2RheT4ACgkQvdyMwXnhrYPL+w//X67nooKXUUUwfWwMtG1b
I2+36xz1ffsU6zof27GzuwndDJn7TCXUQ9+ELycQcMQA0498ma21kOQMT7wqcSg+
q21YLE+4P67gRFPURgoRGH24/3uC91IrdH5Tq27A2EEMsNe/Mn7X+a3JnP8IvjLk
2/22hRygbZEYIlHpqAnZnz1LQ6aeLsQiK6CebXUkb/CPAzYMIpn6TYGb3TtLc6bL
K+bHh/MCnJBAmuaxPztIUgLsNlgW9oK0IncVIvw6VBJ2CUo7/XwCl7Dmrqm1bP4Q
0cg+oodNaKeuwG33bC4pEJ7FOPOVkSV78thJc+1Gp5gZPMpiEujPQb9M1NwYxqp/
N+qjaeax94rrjKtHRE5balCOs4LdTooUyvLBAAh6mmeaotB5MicDx/c+0w2IlCMe
EbW5dNxkKjDDOzg/Tyzacer4NaCgNPjCQaaliorh+TGco//23X6jpL/JstE0Ekip
PCXdgqhtI7W2LMHBVr0Ig5TNRYBwmHkT9oOlCA30e8lmqAfrX+HcpXwmnCkSYJso
e747Or7LgJ907xe0Cw7b0tYsvAch9viTWvFPQaOeNco3SjvPvIffUOyZkXDjglNc
7+gYnEd+3/ofy0ebtN6G316QDmHRPc/hfZGbdLwXxT72KVvzyHraWzPe63C2Kxdt
ZeclxHXyk0Ke9arOCuxYZyc=
=kN6k
-END PGP SIGNATURE-

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

Re: [Sugar-devel] [support-gang] Screenshot of gnome desktop (OLPC OS)

[Sam P.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

There is always social help for sugar related things.  
https://socialhelp.sugarlabs.org/

On 30 April 2016 12:21:11 PM AEST, Tony Anderson  wrote:
>Hi, Dave
>
>Not to my knowledge. This falls on the Gnome side.
>
>Gimp is installed in the OLPC OS image and so this capability is
>available.
>
>Your bigger question is where are the forums, faq and other customary
>media for the community to communicate and support its user base?
>This is part of the 'vision' question.
>
>Tony
>
>On 04/30/2016 08:50 AM, Dave Crossland wrote:
>>
>> Is there a suitable FAQ page on the wiki to add this to?
>>
>> On Apr 29, 2016 7:32 PM, "Tony Anderson" > > wrote:
>>
>> Sebastian,
>>
>> Thanks. I had vaguely remembered making some screen shots in
>gnome
>> - that was how I did it.
>> I'll forward this info.
>>
>> Tony
>>
>> On 04/29/2016 09:34 PM, Sebastian Silva wrote:
>>
>> El 29/04/16 a las 07:49, Kevin Gordon escribió:
>>
>>   I believe there is also functionality in scrot or gimp
>>
>> Confirmed, Gimp can do it. File menu -> Create / Acquire ->
>> Screenshot.
>>
>> ___
>> 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
>
>
>
>
>
>___
>Sugar-devel mailing list
>Sugar-devel@lists.sugarlabs.org
>http://lists.sugarlabs.org/listinfo/sugar-devel

- --
Sent from my phone. Please excuse my brevity.
-BEGIN PGP SIGNATURE-
Version: APG v1.1.1

iQJOBAEBCgA4BQJXJCazMRxTYW0gUC4gKE1vYmlsZSBOZXh1cyA0IEN5YW5vZ2Vu
KSA8c2FtQHNhbS50b2RheT4ACgkQvdyMwXnhrYPyThAAiOOpQPtyCdtNI8AsNQXX
hIF3oc3TcYDN1CEUIbTZ57el1urF9IMceEtm2RTnSOZND8tnw8B5UKbRNxYcJ81i
S7tYbZKYT7l0o7x3G/BDCBSlMMoJsdSEGCI1ImNq4K6ZNmPnp3SAthcqbRz2OvEF
Ijt2Jksmj4NmlYS9toP/5vuwAio+cnYOv0pVxRXMGZSDVGSpvM9WdOd0ag0wRT4d
UgMzg6AvbUvZPenSPYnc/9AMdmOr6zC5oMj9onWWWP6WL1Vay3WGjHNLHolcHPbo
1371D1AMTOtF+LLR+6Ty1rxeWDNpcl4cvX0hFVEsJ13NpXWNB/8rrt2WQtfpYKhU
k+IW7WntJ8o55c/v7Eu++TeKSzDm+c/C9X+v5rmgUyjwHbKL+PMyiqnvYQoMzOJJ
rtNfcrrVEixa/G+OEfcYXTH384G/ncXAp53x5tpoOvxe/HQzLjDnkLN3aEVfLigQ
JjuIDieQLwIFmEdkxeACeCSB55t5tGNAiSDN/+VKsTICLZgXdUtX6AJdVnSaxgmT
nrqZdgvBBkwtDZNpesW03hVKJ/wjsk+7bcwXkQW97fJuwDsgCSZPSp3Fbf/y7Vbg
fD5ckIS3Vt9ZtQmw171RM2ZGQ1BDYqGA1Av/LspxidOlQglO8cbXXjPWjZi7PezO
iBtpexdVa8eX1DTOcWKv9tY=
=r770
-END PGP SIGNATURE-

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

Re: [Sugar-devel] Sugar On Broadway?

[Sam P.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I believe that abstracting the x11 dependency will be beneficial beyond 
Broadway.  It will help us when we move to Wayland for example.

Thanks,
Sam

On 27 April 2016 9:31:38 AM AEST, Manash Raja  wrote:
>>
>> You were? Awesome! Did you have to further patch sugar-toolkit-gtk3?
>
>I didn't have to do any further edits than your two patches.
>
>I wonder if running the full shell is really desirable on a browser. It
>> sounds difficult as it handles a lot of X11 specifics.
>>
>Ya, the jarabe.main is failing while handling jarabe.screen . Maybe we
>can
>have a modified jarabe.main to be run only with broadwayd which doesn't
>handle much of X11 and simple creates a GTK window for the desktop.
>
>On Wed, Apr 27, 2016 at 4:10 AM, Sebastian Silva
>
>wrote:
>
>> El 26/04/16 a las 17:18, Manash Raja escribió:
>> > I am trying to find out where the execution of "python2 -m
>> > jarabe.main" is failing to run sugar on broadwayd.
>>
>> I wonder if running the full shell is really desirable on a browser.
>It
>> sounds difficult as it handles a lot of X11 specifics.
>>
>> Also, I wonder how/if this could integrate with Sugarizer and
>sugar-web
>> activities...
>>
>> Regards,
>> Sebastian
>>
>
>
>
>
>___
>Sugar-devel mailing list
>Sugar-devel@lists.sugarlabs.org
>http://lists.sugarlabs.org/listinfo/sugar-devel

- --
Sent from my phone. Please excuse my brevity.
-BEGIN PGP SIGNATURE-
Version: APG v1.1.1

iQJOBAEBCgA4BQJXIBLdMRxTYW0gUC4gKE1vYmlsZSBOZXh1cyA0IEN5YW5vZ2Vu
KSA8c2FtQHNhbS50b2RheT4ACgkQvdyMwXnhrYMvFg//X1VusR1/ZIP9Xzcc2yh3
d8c5hPaOV2BXHYBagtMw9b5XKONrrYKKWjBl7MmZ1o3vTTAKKkHip89XiE1xFYI1
tFC9UtImaRaENfIyANfF1RSsPTHGMHSQehup19vHNw5AXrgyn1B3u0HIODjiKoxp
VoM3szI4Chr95lW6nk8Qp7YJbqAkQPrM43MSdWwHMZ8GHayS+NTb2E2AL2/Fc8Oy
CNF7LFLWOeY4okIaS28niTlDl788vFL8BnHoP3uojHak/yGozrmPpv+961Txn25O
qkrVl2nO0oRm5yp+XNqXFDwNQ8Oric7uICEygzQyd83DeHWHtyoFuU4RLpuQOBRN
dyj1h/d9ES5izfBLSlseZIfNT22RADk0FWrGDIbfzs5Ly+94JN9U5N2j/Q6QRbxU
Y9N4F6H54rdeTqwzAy+H0f00+DyrC1yg1ADln+av1aCqqBKNT+AH+cN51ZzYwEgP
Tnd+VwaiwZ6NhWmB5Nq0LptHNQTOPR63/8KgIPonTHm02YyhUifQlNN6Ja2jJ6i/
yAveFBzkPD7ZWAlvnTbcK8K9pTj2cLhKs86xbTKxriwDLhidjg5/8XnhHcbEdPgW
dwFmFiohX7KJFmB0B8ph9tsJ0jHS24qkrYbJIIm7AjUoeBb/cWU5iVE5Ye6bwrw1
FZKVVQ2E8sgQRFzsZYIfTDo=
=qKjn
-END PGP SIGNATURE-

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

Re: [Sugar-devel] GSoC 2016 Website Redesign

[Sam P.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

I tested your website in portrait on my phone.  Many of the text columns looked 
a little small.  Please try to test with that too.

When I went to your site, it seemed to be lacking in content.  Please don't add 
dummy text now and do content later.  Content is genuinely the most important.  
No matter how nice your design is, no new visitor will be able to get what 
sugarlabs is by looking at your site - it simply doesn't say it!

The pictures and design are only as important as they are good at pushing our 
message.  Please consider pushing a message - telling a story and having a 
conversation.

Thanks,
Sam

On 19 April 2016 7:50:12 AM AEST, Sanchit Bansal 
 wrote:
>Hey
>
>Can you guys take a looks at this and give me some feedback on the
>design :
>sanchitbansal.xyz/GSoC/
>
>Thanks a lot
>
>
>On Tue, Apr 19, 2016 at 3:18 AM, James Cameron 
>wrote:
>
>> On Mon, Apr 18, 2016 at 02:04:19PM -0500, Juan Carlos Murillo wrote:
>> > Hi developers,
>> >
>> > I hope you are doing well.
>>
>> Fine thanks!
>>
>> > I applied for the GSoC 2016 to work on the redesign of the Sugar
>Lab’s
>> > websites. I would like to have your opinions on the following
>> > questions.
>>
>> A question not asked, for perhaps it is obvious, is who is the
>> intended audience for each web site.
>>
>> > In addition to Sugar Labs main webpage, Wiki, Planet, and the
>> > Translation webpages, which other websites do you think will need
>to
>> > be redesigned?
>>
>> You might ask systems@ for a list of virtual hosts.
>>
>> Some may benefit from style changes, if consistency of style is
>> critical;
>>
>> help.sugarlabs.org
>> socialhelp.sugarlabs.org
>> developer.sugarlabs.org
>>
>> There is old information about Sugar on wiki.laptop.org.  If you need
>> an account to remove or redirect on wiki.laptop.org, contact me.
>>
>> > Which Sugar Lab’s logo color is going to be adopted: orange, green
>> > or blue?
>>
>> I don't think it matters.
>>
>> > What color schemes would you prefer to use on Sugar Lab’s websites?
>> > The current websites have a wide variety of color schemes; a same
>> > color scheme on all websites may look nicer.
>>
>> I don't think it matters.
>>
>> > Do you prefer a particular CMS? WordPress? Drupal? Joomla?
>>
>> No.  Something with git integration would be helpful so that
>> developers can link Sugar source code changes with changes to web
>> sites.  Otherwise a change might be made in only one place, leading
>to
>> inconsistency.
>>
>> --
>> James Cameron
>> http://quozl.netrek.org/
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>
>
>
>--
>
>Regards
>
>*"Per aspera ad astra"*
>
>*Sanchit Bansal*
>
>First Year Undergraduate | Class of 2018
>
>M +91 8222940537 | sanchit.bansal_u...@ashoka.edu.in |
>www.sanchitbansal.xyz
>
>
>CAMPUS Plot No. 2, Rajiv Gandhi Education City, Kundli, NCR
>
>[image: Inline image 1]
>
>*Notice*: This email and any files transmitted with it are confidential
>and
>intended solely for the use of the individual or entity to whom they
>are
>addressed. If you are not the intended recipient, any dissemination,
>use,
>review, distribution, printing or copying of the information contained
>in
>this e-mail message and/or attachments to it are strictly prohibited.
>If
>you have received this email by error, please notify us by return
>e-mail or
>telephone and immediately and permanently delete the message and any
>attachments.
>
>
>
>
>___
>Sugar-devel mailing list
>Sugar-devel@lists.sugarlabs.org
>http://lists.sugarlabs.org/listinfo/sugar-devel

- --
Sent from my phone. Please excuse my brevity.
-BEGIN PGP SIGNATURE-
Version: APG v1.1.1

iQJOBAEBCgA4BQJXFV35MRxTYW0gUC4gKE1vYmlsZSBOZXh1cyA0IEN5YW5vZ2Vu
KSA8c2FtQHNhbS50b2RheT4ACgkQvdyMwXnhrYPMFRAAjmBjkqDaiUQS5QJzxCU7
iyLSx4Cz+dOMcpoAacACi0G+lwaSNhs/kREtybgU0B6cDte/L+8riWmcH4ADuURv
XvOLqoNXrIEatYQHRO63ptbJCc49aF3Hhsp8+27ab/iVe3Ino+3ZfVn9MdsAmNsn
HDTyPjr3V+cZN7g3+fezmM2IXEakNKkiPed/VXLa41ws7c3jz5rwAdKLhAzdrtkt
FFlgo6AxWP+rwjFv9+16gVoQDls3vNttNNxluO2bqSUTGgJu4gFKsuKcN7x0gT6A
Nl/hGdvjbzDbPDISTtLyXFMqOo9dB7aZ8RlnVebpot/d0hf1pX6yJMhHqbmzc5x9
O348VgCgaNnHKGA+hLPNHWIfDbf+akb+qJgsoAsvPXtzYTUhRIqS40zGGt2wMUWe
N93FZpWW7Z28Bzq0+nyUvJ1oZLm3+gdw7RXz+Nlsr+Y09lpFVnQOkZ+ng40gDL3x
ScjGDR1F6Ne56ms1ZW8vGwiOCWFruLHfgJmv62Hyr1R19+WelMZjaRMSUNFurNio
YUqm+ycYIpGupQrn7YjxvmOPEVgUsiLFQ89pqdNmFvAfNAYhGsbLPUxweomPVrZ4
WU0YvkMqtloTN02UgWIL5Xd+ciQvgq7161KdbmfP+7Ft5HKNsZfZEFUlReacURju
RTXi2CNGj7wradCl+Bh8Vho=
=UrhE
-END PGP SIGNATURE-

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

Re: [Sugar-devel] Screenshot feature [GSoC Project]

[Sam P.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dave is right.  The my settings is the dominant and more flexable style.

Maybe we could move the password prompt into the palette, or convert it to the 
better style?

Isn't the journal full alert one of the most confusing things for users?  Isn't 
it something that really needs to be majored; instead of yelling at the user 
for doing using storage, we could suggest jobjects+bundles for them to remove!  
We could even integrate a backup function in there!

On 13 April 2016 2:18:10 PM AEST, James Cameron  wrote:
>On Tue, Apr 12, 2016 at 11:57:59PM -0400, Dave Crossland wrote:
>>
>> On 12 April 2016 at 21:05, James Cameron <[1]qu...@laptop.org> wrote:
>>
>> The question at hand is whether the new screenshot dialog from
>Utkarsh
>> should be styled like the wireless password dialog, or styled
>like My
>> Settings.
>>
>> Seems to me the "My Settings" style is better. 
>
>Thanks.  Do you think the wireless password prompt and journal full
>warnings should also follow this style?
>
>--
>James Cameron
>http://quozl.netrek.org/
>___
>Sugar-devel mailing list
>Sugar-devel@lists.sugarlabs.org
>http://lists.sugarlabs.org/listinfo/sugar-devel

- --
Sent from my phone. Please excuse my brevity.
-BEGIN PGP SIGNATURE-
Version: APG v1.1.1

iQJOBAEBCgA4BQJXDrdvMRxTYW0gUC4gKE1vYmlsZSBOZXh1cyA0IEN5YW5vZ2Vu
KSA8c2FtQHNhbS50b2RheT4ACgkQvdyMwXnhrYMhaw/9F7YRzsSqELrvvixf+hg0
AkhOVAjwTw29AF6KrHXgokdw9z69an0eLcdnLNLAXIl+3coKWGbJ7FKtDuE1d5Ey
t4zZ+wC0uGzb5pK/3abJwZiG/bk+Pk5p8AWZiXJ2ksBeqTMCHoZ7ZSWZIOWHT4g1
iwnYtQce/kpUgUN7iuD/+j9sQjPIGgOqFSq2rICobIEjqocUXu3BrzYUCwIq58ek
y+rUojzihFzDYPzN7dw2VRwtjijRIyKySKRuWYtFoDXX8HMJSQaBuT1HDtxXK/dD
6UFZ8oKCiIkdWsN0e8ys1QWCPAvYJiTzW3eyfDUYGVIV32VibsPsQaLEdkB3ltf8
BoxOFYrLmxrY9sJWrbtd1q7TgW3Qpgq4wJWdLNxcsUFrrzpn0cAfpoY2rpLUgNal
vNsjdEjewbbR2BNzU7XLhkXhstqq9HBbUUq6H2jyOFdXsu0fiDQfoI8iAv3dmmgD
SxVj1p3QpakccQZpAF7sB03qM6+zUhSujZXKiq1JaMEGYvfg28gZyFxBDYonEHp5
UyWirKvLdo7KsZDQJonpiwjlSxsNY/5CRMYlBSHrEtwS8447xrOJy5vA6QOcmEIr
PEpX7QLJnFXefNQ37bN3wSYnHwSzvkJSCRbC0aiLCjUwr3+EK9edbfelMSwtN0JJ
YOzN57sVdLXMskJ//hQrHXk=
=Rh1Q
-END PGP SIGNATURE-

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

Re: [Sugar-devel] [Bugs] #4906 Sugar NORM: No indicator when headphones are plugged in

[Sam P.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

You could probably start at with simply changing the text, then send a later 
patch to add new icons.

On 6 April 2016 10:36:09 PM AEST, Sugar Labs Bugs 
 wrote:
>#4906: No indicator when headphones are plugged in
>--+-
>  Reporter:  SAMdroid |Owner:
>  Type:  defect   |   Status:  new
>  Priority:  Normal   |Milestone:  Unspecified
> Component:  Sugar|  Version:  Git as of bugdate
>  Severity:  Minor|   Resolution:
>  Keywords:   |  Distribution/OS:  Fedora
>Bug Status:  Unconfirmed  |
>--+-
>
>Comment (by manashraja):
>
> Can you tell me what change is desired?
> For the "Speaker" text it should change to "Headphones".
>
>But for the speaker icon, what should it change to? Is there a icon for
> headphone already or shall I make it first?
>
>--
>Ticket URL: 
>Sugar Labs 
>Sugar Labs bug tracking system
>___
>Bugs mailing list
>b...@lists.sugarlabs.org
>http://lists.sugarlabs.org/listinfo/bugs

- --
Sent from my phone. Please excuse my brevity.
-BEGIN PGP SIGNATURE-
Version: APG v1.1.1

iQJOBAEBCgA4BQJXBYxNMRxTYW0gUC4gKE1vYmlsZSBOZXh1cyA0IEN5YW5vZ2Vu
KSA8c2FtQHNhbS50b2RheT4ACgkQvdyMwXnhrYMmvg/8DWp6DxhjeVWrNckfGPah
3njwqDCy9yYr0i02knNzshRRgHqoLUJoIktf+f5L9BdRIhi4wwMlf2ss7DnP0CmN
Vp8g8LR1cZiNo3fP6W8PonST0+g3XX+z2JxiO3Rg8+7Y3p5WnBYzc7/lz9X2rWQX
KNGopyDNR/9mNNhME+J6k7e3Ai8VyKI2hs/9UAwyWFZ1eTdnGAGOm7ZsjMXhU298
W/9O5rENswc+CuxjlevsvaIlXphXdLDh9j5p9+Vc8dFH8OynROVwst4Gdmgkkw+j
AAxPPAdwuiINGzG8fB/GiDxiS2Uy91hJPu7OPcqeI2a08eH0lWI0Z1YfqFpsSa3c
Ge5hEACGpftEVdWwIlKU3gJIBd2L4Nd1AVgm/bNjevJX5WMngr0chInRDybMf1ki
WoawV/+EYyUdMbPO6dDIhYiHDw4a1YCiL8D5BVAWRjC82v/SoESiGLldcqiyT1ie
Pr50rPXUdsTV07SLgVHGVSi9D95CXnc38+/FeMGhTvVxE4OkRcrPgehnPjpxQhEq
WDFfeesipRX4h3zl7Aq2V1WrFALKtQGg7I0Q2xL1hmAH8UacN7BAyKGzvNwjKiu+
xhc/EWWgJMTSUoEjZlAhKqjA67sgd9nIepK540w4pUjmf6AiDobM/GwBvdmZaQrz
csky3VFOATGPtyi4Ez9uVPE=
=BHOY
-END PGP SIGNATURE-

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

Re: [Sugar-devel] GSoC Aspirant

[Sam P.]

Did trac email you the validation token?  We recently changed the email setup 
so it now sends emails properly.  Please check all your folders if it is not in 
your inbox.

On 13 March 2016 4:22:40 am LHDT, Nitin Jain  wrote:
>It is still showing the same error. The screenshots of errors are
>attached.
>Please tell me if there's any way around this so that I can contribute.
>I
>also mailed Mr. Martin personally but did not get a reply.
>Thanks and Regards.
>Nitin
>ᐧ
>
>On Sat, Mar 12, 2016 at 10:40 PM, Walter Bender
>
>wrote:
>
>> I think the trac verification issue may finally be fixed? Please try
>again.
>>
>> On Sat, Mar 12, 2016 at 12:51 AM, Nitin Jain 
>> wrote:
>>
>>> Hi,
>>> This is Nitin Jain, a sophomore from IIT Roorkee, India.
>>> I went through the ideas page and loved the idea "Git Backend" and
>am
>>> quite interested to work on this project under GSoC this summer.
>>>
>>> I have a good knowledge of Python and PYGTK (related to the project)
>as
>>> well as of PHP, Javascript, HTML, CSS and Java. I also have a good
>>> understanding of Version Control Systems. I feel that I fulfill the
>>> pre-requisites for this project.
>>>
>>> I have also gained practical experience in developing institute
>level
>>> applications being a part of Information Management Group, IIT
>Roorkee
>>> which is responsible for development and maintenance of various
>intranet
>>> web apps as well as the official website of IITR.
>>>
>>> Regarding the GSoC idea, I have been experiencing problems with my
>trac
>>> account as my email is not getting verified even after being put
>into the
>>> unmoderated section by Mr. Walter.
>>> I wanted to know if there's anything to work around from that. Also
>it
>>> would be really helpful if I could have a discussion with the mentor
>>> regarding the project so that I can draft a proposal for review.
>>>
>>> Links:
>>> [1]: http://img.channeli.in/works/
>>>
>>> Thanks beforehand.
>>>
>>> Regards.
>>>
>>> Nitin Jain
>>> ( https://in.linkedin.com/in/nitin-jain-a010b3112 )
>>> ᐧ
>>>
>>> ___
>>> Sugar-devel mailing list
>>> Sugar-devel@lists.sugarlabs.org
>>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>>
>>>
>>
>>
>> --
>> Walter Bender
>> Sugar Labs
>> http://www.sugarlabs.org
>> 
>>
>
>
>
>
>___
>Sugar-devel mailing list
>Sugar-devel@lists.sugarlabs.org
>http://lists.sugarlabs.org/listinfo/sugar-devel

-- 
Sent from my phone. Please excuse my brevity.___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Regarding crash of sugar!

[Sam P.]

Did removing sugar runner and rebuilding it fix your problems?  Have you
already done it?

Usually, I find that this error surfaces when I make changes to sugar that
cause it to crash on startup.  Usually, it is just a syntax error in your
code, and the traceback will be visible in the log file.

Thanks,
Sam

On Mon, Feb 29, 2016 at 7:05 PM Abhijit Patel <abhisandhyasp...@gmail.com>
wrote:

> Hi Sam,
> So what changes should I make?
>
> I just google crashing of sugar-runner I found something like this
> rm -rf sugar-runner
> ./osbuild pull sugar-runner
> ./osbuild build sugar-runner
>
> Is this a better solution?
>
> On 29 February 2016 at 13:30, Sam P. <sam@sam.today> wrote:
>
>> Ah, this is one of the worst error messages of all time.  Usually it has
>> nothing to do with X, and is actually because jarabe (sugar shell) crashed.
>>
>> Try viewing the sugar log.  If you are using sugar-build, it will be in
>> "sugar-build/home/dotsugar/default/logs/shell.log".  Otherwise, it will be
>> in ".sugar/default/logs/shell.log".
>>
>> Thanks,
>> Sam
>>
>> On Mon, Feb 29, 2016 at 6:45 PM Abhijit Patel <abhisandhyasp...@gmail.com>
>> wrote:
>>
>>> I was successfully running sugar on my Ubuntu since a month. But
>>> suddenly today I am getting the below error!
>>>
>>> Command failed: sugar-runner
>>>
>>>
>>> Initializing built-in extension Generic Event Extension
>>> Initializing built-in extension SHAPE
>>> Initializing built-in extension MIT-SHM
>>> Initializing built-in extension XInputExtension
>>> Initializing built-in extension XTEST
>>> Initializing built-in extension BIG-REQUESTS
>>> Initializing built-in extension SYNC
>>> Initializing built-in extension XKEYBOARD
>>> Initializing built-in extension XC-MISC
>>> Initializing built-in extension XINERAMA
>>> Initializing built-in extension XFIXES
>>> Initializing built-in extension RENDER
>>> Initializing built-in extension RANDR
>>> Initializing built-in extension COMPOSITE
>>> Initializing built-in extension DAMAGE
>>> Initializing built-in extension MIT-SCREEN-SAVER
>>> Initializing built-in extension DOUBLE-BUFFER
>>> Initializing built-in extension RECORD
>>> Initializing built-in extension DPMS
>>> Initializing built-in extension X-Resource
>>> Initializing built-in extension XVideo
>>> Initializing built-in extension XVideo-MotionCompensation
>>> Initializing built-in extension SELinux
>>> xinit: XFree86_VT property unexpectedly has 0 items instead of 1
>>> Warning:  Key  not found in evdev+aliases(qwerty) keycodes
>>>   Symbols ignored
>>> Warning:  Key  not found in evdev+aliases(qwerty) keycodes
>>>   Symbols ignored
>>> Warning:  Key  not found in evdev+aliases(qwerty) keycodes
>>>   Symbols ignored
>>> Warning:  Key  not found in evdev+aliases(qwerty) keycodes
>>>   Symbols ignored
>>> Warning:  Key  not found in evdev+aliases(qwerty) keycodes
>>>   Symbols ignored
>>> Warning:  Key  not found in evdev+aliases(qwerty) keycodes
>>>   Symbols ignored
>>> Warning:  Key  not found in evdev+aliases(qwerty) keycodes
>>>   Symbols ignored
>>> Warning:  Key  not found in evdev+aliases(qwerty) keycodes
>>>   Symbols ignored
>>> Warning:  Key  not found in evdev+aliases(qwerty) keycodes
>>>   Symbols ignored
>>> Warning:  Key  not found in evdev+aliases(qwerty) keycodes
>>>   Symbols ignored
>>> Warning:  Key  not found in evdev+aliases(qwerty) keycodes
>>>   Symbols ignored
>>> Warning:  No symbols defined for  (keycode 97)
>>> Warning:  No symbols defined for  (keycode 103)
>>> Warning:  No symbols defined for  (keycode 120)
>>> Warning:  No symbols defined for  (keycode 132)
>>> Warning:  No symbols defined for  (keycode 149)
>>> Warning:  No symbols defined for  (keycode 154)
>>> Warning:  No symbols defined for  (keycode 161)
>>> Warning:  No symbols defined for  (keycode 168)
>>> Warning:  No symbols defined for  (keycode 178)
>>> Warning:  No symbols defined for  (keycode 183)
>>> Warning:

Re: [Sugar-devel] Regarding crash of sugar!

[Sam P.]

Ah, this is one of the worst error messages of all time.  Usually it has
nothing to do with X, and is actually because jarabe (sugar shell) crashed.

Try viewing the sugar log.  If you are using sugar-build, it will be in
"sugar-build/home/dotsugar/default/logs/shell.log".  Otherwise, it will be
in ".sugar/default/logs/shell.log".

Thanks,
Sam

On Mon, Feb 29, 2016 at 6:45 PM Abhijit Patel 
wrote:

> I was successfully running sugar on my Ubuntu since a month. But suddenly
> today I am getting the below error!
>
> Command failed: sugar-runner
>
>
> Initializing built-in extension Generic Event Extension
> Initializing built-in extension SHAPE
> Initializing built-in extension MIT-SHM
> Initializing built-in extension XInputExtension
> Initializing built-in extension XTEST
> Initializing built-in extension BIG-REQUESTS
> Initializing built-in extension SYNC
> Initializing built-in extension XKEYBOARD
> Initializing built-in extension XC-MISC
> Initializing built-in extension XINERAMA
> Initializing built-in extension XFIXES
> Initializing built-in extension RENDER
> Initializing built-in extension RANDR
> Initializing built-in extension COMPOSITE
> Initializing built-in extension DAMAGE
> Initializing built-in extension MIT-SCREEN-SAVER
> Initializing built-in extension DOUBLE-BUFFER
> Initializing built-in extension RECORD
> Initializing built-in extension DPMS
> Initializing built-in extension X-Resource
> Initializing built-in extension XVideo
> Initializing built-in extension XVideo-MotionCompensation
> Initializing built-in extension SELinux
> xinit: XFree86_VT property unexpectedly has 0 items instead of 1
> Warning:  Key  not found in evdev+aliases(qwerty) keycodes
>   Symbols ignored
> Warning:  Key  not found in evdev+aliases(qwerty) keycodes
>   Symbols ignored
> Warning:  Key  not found in evdev+aliases(qwerty) keycodes
>   Symbols ignored
> Warning:  Key  not found in evdev+aliases(qwerty) keycodes
>   Symbols ignored
> Warning:  Key  not found in evdev+aliases(qwerty) keycodes
>   Symbols ignored
> Warning:  Key  not found in evdev+aliases(qwerty) keycodes
>   Symbols ignored
> Warning:  Key  not found in evdev+aliases(qwerty) keycodes
>   Symbols ignored
> Warning:  Key  not found in evdev+aliases(qwerty) keycodes
>   Symbols ignored
> Warning:  Key  not found in evdev+aliases(qwerty) keycodes
>   Symbols ignored
> Warning:  Key  not found in evdev+aliases(qwerty) keycodes
>   Symbols ignored
> Warning:  Key  not found in evdev+aliases(qwerty) keycodes
>   Symbols ignored
> Warning:  No symbols defined for  (keycode 97)
> Warning:  No symbols defined for  (keycode 103)
> Warning:  No symbols defined for  (keycode 120)
> Warning:  No symbols defined for  (keycode 132)
> Warning:  No symbols defined for  (keycode 149)
> Warning:  No symbols defined for  (keycode 154)
> Warning:  No symbols defined for  (keycode 161)
> Warning:  No symbols defined for  (keycode 168)
> Warning:  No symbols defined for  (keycode 178)
> Warning:  No symbols defined for  (keycode 183)
> Warning:  No symbols defined for  (keycode 184)
> Warning:  No symbols defined for  (keycode 197)
> Warning:  No symbols defined for  (keycode 202)
> Warning:  No symbols defined for  (keycode 217)
> Warning:  No symbols defined for  (keycode 219)
> Warning:  No symbols defined for  (keycode 221)
> Warning:  No symbols defined for  (keycode 222)
> Warning:  No symbols defined for  (keycode 230)
> Warning:  No symbols defined for  (keycode 247)
> Warning:  No symbols defined for  (keycode 248)
> Warning:  No symbols defined for  (keycode 249)
> Warning:  No symbols defined for  (keycode 250)
> Warning:  No symbols defined for  (keycode 251)
> Warning:  No symbols defined for  (keycode 252)
> Warning:  No symbols defined for  (keycode 253)
> gnome-keyring-daemon: insufficient process capabilities, unsecure memory
> might get used
> The XKEYBOARD keymap compiler (xkbcomp) reports:
> > Warning:  Compat map for group 2 redefined
> >   Using new definition
> > Warning:  Compat map for group 3 redefined
> >   Using new definition
> > Warning:  Compat map for group 4 redefined
> >   Using new definition
> Errors from xkbcomp are not fatal to the X server
> The XKEYBOARD keymap compiler (xkbcomp) reports:
> > Warning:  Compat map for group 2 redefined
> >   Using new definition
> > Warning:  Compat map for group 3 redefined
> >   Using new 

Re: [Sugar-devel] Browse as a GSoC 2016 Project

[Sam P.]

Hi Utakarsh,

I am not familiar with Richa's project, however maybe you could look into
surfacing the WebInspector provided by webkitgtk+ in your ui?  It is a
pretty standard web inspector, and is used by Epiphany (GNOME Web) and
Safari.  See the WebKit2 api for this [1].

Maybe another feature to evaluate is annotations?   Browse currently has
the consept of bookmarking (adding a site to the bottom bar) and saving it
in the journal.  However it could be very helpful for researching users to
be able to annotate the page and save that in the bookmark.  The Microsoft
Edge browser has a similar feature, although doesn't intergrate with their
bookmarking system (which is very different from ours anyway) and seems to
rely on annotating a png screenshot of the webpage rather than the actual
page.

Thanks,
Sam

[1]
http://webkitgtk.org/reference/webkit2gtk/unstable/WebKitWebView.html#webkit-web-view-get-inspector

On Thu, Feb 25, 2016 at 12:01 AM utkarsh Dhawan <dhawanutka...@gmail.com>
wrote:

> Hi,
>
> Last year Richa was involved in the JavaScript Interactive Shell project,
> which I guess was successfully completed.As far as I remember it pretty
> much was on the tracks of Tony's idea of the generic toolbar button ,
> though it only had three options in totality Save file,Open file and Open
> Web console.I would really like to continue on this project with the other
> features enhancing the browse.
>
> Thanking You,
> Utkarsh Dhawan
> (Developer/Student)
>
> Note:Please Consider The environment before printing.
>
> On Tue, Feb 23, 2016 at 10:01 AM, Tony Anderson <tony_ander...@usa.net>
> wrote:
>
>> I suspect we need a GSOC task to make this project visible. The GSOC task
>> could define the starting point (webkit2 or new branch). We still have
>> Richa Sehgal's contribution from last year to integrate with Browse.
>> Godiard believes that some developer tools are available in Browse but not
>> directly by the toolbar. I would like to see a 'generic' toolbar button
>> like Firefox/Googles 3x3 array of dots to open up a more complete set of
>> options including access to developer tools like 'show source page', and
>> any like Firebug that can be made available.
>>
>> Tony
>>
>>
>> On 02/23/2016 10:41 AM, Sam P. wrote:
>>
>>
>> Hello,
>>
>> Please have a look at the pull requests and the 'webkit2' branch..
>> Testing and contributions are appreciated.
>>
>> I think this port is very close to done, so would you have enough to do
>> in your project?
>>
>> Thanks,
>> Sam
>> On Tuesday, February 23, 2016, Utkarsh Tiwari <
>> <iamutkarshtiw...@gmail.com>iamutkarshtiw...@gmail.com> wrote:
>> > Hello everyone,
>> >  Few days back I read on a sugar-devel thread
>> > where Mr. James Cameron wrote -> "An interesting blog post describing
>> > the situation with WebKit security
>> > updates:
>> >
>> >
>> https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-security-updates/
>> >
>> > Browse in Sugar is without security updates because it depends on
>> > an old WebKit version of WebKitGTK+, and the great API break called
>> > WebKit2 has not yet been fixed in a Browse release."
>> >
>> > So are we talking up 'Browse' this summer as a potential GSoC project?
>> > Since I have been working on it for a while and I am getting familiar
>> > with it's codebase,  so I would love to work on it. :)
>> >
>> > regards,
>> > Utkarsh Tiwari
>> > ___
>> > Sugar-devel mailing list
>> > Sugar-devel@lists.sugarlabs.org
>> > http://lists.sugarlabs.org/listinfo/sugar-devel
>> >
>>
>> ___
>> Sugar-devel mailing 
>> listSugar-devel@lists.sugarlabs.orghttp://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
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Browse as a GSoC 2016 Project

[Sam P.]

Hello,

Please have a look at the pull requests and the 'webkit2' branch.. Testing
and contributions are appreciated.

I think this port is very close to done, so would you have enough to do in
your project?

Thanks,
Sam
On Tuesday, February 23, 2016, Utkarsh Tiwari 
wrote:
> Hello everyone,
>  Few days back I read on a sugar-devel thread
> where Mr. James Cameron wrote -> "An interesting blog post describing
> the situation with WebKit security
> updates:
>
> https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-security-updates/
>
> Browse in Sugar is without security updates because it depends on
> an old WebKit version of WebKitGTK+, and the great API break called
> WebKit2 has not yet been fixed in a Browse release."
>
> So are we talking up 'Browse' this summer as a potential GSoC project?
> Since I have been working on it for a while and I am getting familiar
> with it's codebase,  so I would love to work on it. :)
>
> regards,
> Utkarsh Tiwari
> ___
> 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] Download Manager ProgressBar [DESIGN]

[Sam P.]

This looks great!  Please send a patch and we can review it!

On Sun, Feb 21, 2016, 05:29 Utkarsh Tiwari <iamutkarshtiw...@gmail.com>
wrote:

> Hello everyone,
>   I finally managed to pull through 50% of the
> downloadManagerIcon integration task. Here is the gif of all what I did
> till now -> http://imgur.com/zS0W9dG
> There is still a long way to go. Reviews on this would be helpful :)
>
> regards,
> Utkarsh Tiwari
>
>
>
> On Sat, Feb 13, 2016 at 8:36 PM, Utkarsh Tiwari <
> iamutkarshtiw...@gmail.com> wrote:
>
>> I need to update a toolbutton in webtoolbar as the download progresses
>> in background. Could anyone please guide me how to go about it?
>>
>> On 2/11/16, Utkarsh Tiwari <iamutkarshtiw...@gmail.com> wrote:
>> > @James As mentioned, I tried making a blend of 'progressIcon' &
>> > 'ToolButton' by making some changes to the SugarToolButton code. Here is
>> > how the download ProgressIcon @50% completion looks like ->
>> > http://imgur.com/iBg4Ktr
>> >
>> > Waiting for your reviews :)
>> >
>> > On Thu, Feb 11, 2016 at 3:28 PM, Sam P. <sam@sam.today> wrote:
>> >
>> >> Hello,
>> >>
>> >> I believe that it passes all the key word and normal arguments to the
>> >> superclass constructors.
>> >>
>> >> Out of interest, why are you using a Gtk drawing area as an additional
>> >> base class?  Every widget (even the tool button) has the draw signal.
>> Is
>> >> this what you are using it for or is there something else?
>> >>
>> >> Thanks,
>> >> Sam
>> >>
>> >> On Thu, Feb 11, 2016, 09:03 Utkarsh Tiwari <iamutkarshtiw...@gmail.com
>> >
>> >> wrote:
>> >>
>> >>> What does the line "GObject.GObject.__init__(self, **kwargs)" exactly
>> >>> does in the following gist?
>> >>>
>> >>> https://gist.github.com/iamutkarshtiwari/5024762d0e8924b52085
>> >>>
>> >>> On Thu, Feb 4, 2016 at 5:00 AM, James Cameron <qu...@laptop.org>
>> wrote:
>> >>>
>> >>>> Thanks.  Yes, the position is as I described.
>> >>>>
>> >>>> Your question puzzles me.  I didn't think there was any ambiguity or
>> >>>> doubt.  It is unfortunate that I'm the only one who has posted about
>> >>>> the positioning of this design change.
>> >>>>
>> >>>> Is it because you have an alternate suggestion?
>> >>>>
>> >>>> Good to hear combining the widgets worked.  Looking forward to seeing
>> >>>> a patch or pull request.
>> >>>>
>> >>>> On Thu, Feb 04, 2016 at 03:49:54AM +0530, Utkarsh Tiwari wrote:
>> >>>> > @James Is this the icon position you were talking about as shown in
>> >>>> > the
>> >>>> > attachment below? Your hint for using ProgressIcon alongwith
>> >>>> Toolbutton worked!
>> >>>> > ;)
>> >>>> >
>> >>>> > On Tue, Feb 2, 2016 at 2:17 AM, James Cameron <[1]qu...@laptop.org
>> >
>> >>>> wrote:
>> >>>> >
>> >>>> > A ToolButton normally has an Icon.
>> >>>> >
>> >>>> > Instead of the Icon, assign the ProgressIcon?
>> >>>> >
>> >>>> > As nobody else may have done this, you may need to find and fix
>> >>>> > any
>> >>>> > bugs in ProgressIcon or ToolButton that prevent it.
>> >>>> >
>> >>>> > On Mon, Feb 01, 2016 at 11:31:28PM +0530, Utkarsh Tiwari wrote:
>> >>>> > > Is there any way to use a ProgressIcon as a Toolbutton ?
>> >>>> > >
>> >>>> > > On 2/1/16, Sam P. <sam@sam.today> wrote:
>> >>>> > > > Hello!
>> >>>> > > >
>> >>>> > > > Maybe just a large down arrow and fill it vertically?  See
>> >>>> > > > 'emblem-downloads' or 'transfer-from' in sugar-artwork.
>> >>>> > > >
>> >>>> > > > Thanks,
>> >>>> > > > Sam
>> >>>> > > >
>> >>>> > > >
>> >&g

Re: [Sugar-devel] wiki problems

[Sam P.]

Hi Tony,

The freedom issue is related to the Visual Editor function of mediawiki.
Try using the edit source temporally, I will try and find what is wrong in
the mean time.

I'm not sure about the recapatcha though.  Maybe it is a mixed content
issue.  Is there anything in your browsers console log (the inspect element
thing)?

Thanks,
Sam

On Sun, Feb 21, 2016 at 5:42 PM Tony Anderson  wrote:

> Hi,
>
> I am trying to edit https://wiki.sugarlabs.org/go/Translation_Proposal
> which I created earlier today.
>
> I am logged in but get the message: Error loading data from server:
> parsoidserver-http-curl-error: Failed to connect to
> freedom.sugarlabs.org port 8001: Connection refused: . Would you like to
> retry?
>
> Amusingly, when I saved the page I got a recaptcha asking for me to type
> the two words shown 'in the box below'. The only two words in the box were
> 'Privacy & Terms'. However, it turns out the recaptcha wanted a house
> number shown on a door.
>
> Tony
> ___
> 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] GSoC proposal status

[Sam P.]

On Sat, Feb 20, 2016 at 6:00 PM Tony Anderson  wrote:

> Hi, Walter
>
> I have some concerns about the proposed GSOC tasks as well as some ideas
> for new tasks.
>
> I agree that the Journal needs rethinking. Below are my thoughts
> (re-thoughts?).
>
> Specifically,
>
> The Journal is the file system for Sugar. It does not use directories but
> instead was intended to collect objects by tag (a la Picasa). Currently,
> the user sees
> a scrolled list of objects in chronological order. However, selection is
> by activity or media type, not by a user defined criteria (as represented
> in other systems by the directory).
>
> The Journal acts as an activity with awkward consequences for the user. On
> the keyboard, the icon for the Journal (a magnifying glass or search icon -
> not the icon shown in the frame) is to the left of the zoom group on the
> keyboard and to the right on the frame. If the Journal is selected, it
> replaces the current activity when the activity key is pressed. It also
> appears as an activity when using alt-tab. The first makes using
> screenshots awkward. Screenshots are given a title by the system of
> 'Screenshot of '. The user needs to switch to the Journal to provide a
> meaningful name. However, the user must open the frame and click on the
> activity icon to return to it. If the Journal were viewed as a Sugar
> service, the activity key would return the user to make another screen shot
> or continue whatever the task is. Similarly, it is convenient to present
> the user with instructions to perform a task using a Sugar activity (e.g.
> Write). The instructions can be given by a web page or by a document in a
> different activity. For example, a user could show a flag as an image in
> Image Viewer and try to duplicate the flag with TurtleBlocks. However,
> using alt-tab to switch between the activities requires cycling through the
> irrelevant Journal activity or open the frame to click on the activity icon.
>
> More importantly, when a Journal object is launched from the Journal
> activity, it is immediately loaded into activity.py. Therefore, any
> subsequent action by the user will be saved and the previous object will be
> overwritten. Suppose I resume the Paint Activity to continue making a
> picture. However, I decide that after some strokes, the original picture
> was better. There is nothing as a user I can do to revert to the original.
> I suspect the reference to git may be intended to address this problem.
> When an object is launched, activity.py should make a clone. The user
> should then have the option to revert to the original or to overwrite it or
> to change it's name so that a new object is created alongside the original.
> I believe an implementation of the 'save/save as' logic of virtually all
> other systems should be provided.
>

Just my 2c, but this complicates the experience a lot.  Do we show this
temp journal entry to the user?  If so, wouldn't that be confusing?  But it
we hide it, it becomes more complex.  Eg, a user is adding the finishing
touches to a diagram in Paint, and adds it to Write activity, however since
only the old version is visible they don't see the image they expected, and
become confused.  Maybe this could be better served by basic git features
in the journal, one of Martin's project ideas I believe.


>
> Probably, in the interests of 'reflection' or possibly statistical data,
> the Journal saves every activity instance - by default with the name of the
> activity. Further,
> most activities now implement write_file to create a data file associated
> with the object. This creates clutter in the Journal and takes storage for
> meaningless data files. For example, the Browse activity saves a data file
> containing URLs of open tabs. Aside from the fact that this creates
> spurious error messages if Browse is opened in a different network
> environment, it creates the unnecessary need to save a data file. I believe
> that activities should only save a data file if the user supplies a name
> for it and that activities should save state in the metadata, not in a data
> file. Naturally, it may be desirable for Memorize to save its state so the
> user can resume the game - this can be done by a field in the metadata.
> However, when the Paint Activity saves a file, it is reasonable to assume
> it contains an image (usable, for example, by the Image Viewer).
>

Browse save files work fine cross network connections.  I made one at home,
and opening it at school I was able to show people all of my tabs.

Using the metadata is also much harder, it is so easy to just chuck the
json in there.  Even if we use metadata for eg, saving memorize, the
metadata will be so activity specific that it is hard to use in a
reflection tool.  I'm not sure what you want by this.


>
> The XO has limited storage capacity. A freshly installed XO-1 image leaves
> about 300MB free space. A freshly installed image on other models with 4GB

Re: [Sugar-devel] DESIGN TEAM Assemblage

[Sam P.]

On Wed, Feb 17, 2016 at 10:09 PM Ifeanyi Peter 
wrote:

> Dear Sir,
>
> Yes, it sounds like marketing, but who designs what the marketing
> department uses for their functions? It's the design team, that is the
> point I am trying to make as well.
>
> How do I get confirmed as a Design Team member since Gary is away?
>

I can't answer that question.  But I am sure that everybody is always open
for contributions from people, even if they are not part of a "team"!  I'm
excited to new creations!

Thanks,
Sam


>
> regards,
> Ifeanyi Matthew
>
>
>
> __
> Message: 2
> Date: Tue, 16 Feb 2016 07:17:44 +1100
> From: James Cameron 
> To: sugar-devel@lists.sugarlabs.org
> Subject: Re: [Sugar-devel] DESIGN TEAM Assemblage
> Message-ID: <20160215201744.ga6...@us.netrek.org>
> Content-Type: text/plain; charset=us-ascii
>
>
> No, what you describe sounds like a Marketing Team.
>
> Our Design Team acts in the context of the Sugar software, and
> participation is by replying to threads on sugar-devel@ that have a
> [DESIGN] subject tag.  Since you are on sugar-devel@ you can
> participate already, just wait for a thread that asks.
>
> Previous design team organisation also did not include marketing, see
> https://wiki.sugarlabs.org/go/Design_Team (last updated 2010).
>
> We have a mailing list for marketing@, see
> http://lists.sugarlabs.org/listinfo/marketing
>
> On Mon, Feb 15, 2016 at 11:05:22AM +, Ifeanyi Peter wrote:
> > Hi all,
> >
> > Design team leader, Mr. Gary has been off for a while and that has led
> to mails
> > not been responded to intending member who are willing to join the
> SugarLabs
> > design team.
> >
> > I would like SugarLabs admins to organize a reassemble the design team to
> > enhance effectiveness?
> >
> > The design team should be let more into designing Icons for SugarLabs,
> because
> > it seems they are not let in more to so these works.
> >
> > The design team should be the "branding managers" for SugarLabs.
> >
> > The design team should also be responsible for presentation designs,
> > info-graphics to attract prospects who would like to join (they say,
> pictures
> > speaks more than words).
> >
> > And also in terms of Advertising, GIF images might also be handled by the
> > design team while the code can be gotten from our Coders so that we can
> have
> > these web adverts around the web on our various blogs to get more
> volunteer for
> > SugarLabs.
> >
> > What do you think?
> >
> > Ifeanyi Matthew
> >
>
> > ___
> > Sugar-devel mailing list
> > Sugar-devel@lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
> --
> James Cameron
> http://quozl.netrek.org/
>
>
> --
>
> Subject: Digest Footer
>
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
> --
>
> End of Sugar-devel Digest, Vol 88, Issue 33
> ***
>
>
> ___
> 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] Need Assistance

[Sam P.]

Hello,

If trac is not emailing you, try going to the forgot password page and
getting it to reset the password email.  Alternatively, maybe the solution
is just to attempt to log in in spite of receiving the email.  This seems
to be an annoying trac issue as I haven't yet found a case that always
reproduces it.

Regarding beginner tasks, maybe the Google code in tasks will interest
you?  I assume they are still available.  Otherwise please say that and I
will do a search.

Thanks,
Sam

On Sat, Feb 13, 2016, 21:36 Nitin Jain  wrote:

> Hi,
>
> I am a B.Tech sophomore from India. After going through the ideas page, I
> think that the "Versioned Datastore" idea is pretty cool.
> I am familiar with Python and PYGTK and I want to contribute to it.
>
> I have succesfully cloned and installed sugar on my PC and also looked at
> bugs.sugarlabs.org and all the related links as suggested.
>
> I tried registering on trac but I am not getting the email confirmation
> mail. Could you please help me on this?
>
> Also, if you could suggest any beginner bugs that would help me to get
> familiar with the code?
> Please suggest if there's anything else that I could contribute to.
> Looking forward to the feedback.
>
> Thanks.
>
> Regards,
> Nitin Jain
>
> ᐧ
> ___
> 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] Download Manager ProgressBar [DESIGN]

[Sam P.]

Hello,

I believe that it passes all the key word and normal arguments to the
superclass constructors.

Out of interest, why are you using a Gtk drawing area as an additional base
class?  Every widget (even the tool button) has the draw signal.  Is this
what you are using it for or is there something else?

Thanks,
Sam

On Thu, Feb 11, 2016, 09:03 Utkarsh Tiwari <iamutkarshtiw...@gmail.com>
wrote:

> What does the line "GObject.GObject.__init__(self, **kwargs)" exactly does
> in the following gist?
>
> https://gist.github.com/iamutkarshtiwari/5024762d0e8924b52085
>
> On Thu, Feb 4, 2016 at 5:00 AM, James Cameron <qu...@laptop.org> wrote:
>
>> Thanks.  Yes, the position is as I described.
>>
>> Your question puzzles me.  I didn't think there was any ambiguity or
>> doubt.  It is unfortunate that I'm the only one who has posted about
>> the positioning of this design change.
>>
>> Is it because you have an alternate suggestion?
>>
>> Good to hear combining the widgets worked.  Looking forward to seeing
>> a patch or pull request.
>>
>> On Thu, Feb 04, 2016 at 03:49:54AM +0530, Utkarsh Tiwari wrote:
>> > @James Is this the icon position you were talking about as shown in the
>> > attachment below? Your hint for using ProgressIcon alongwith Toolbutton
>> worked!
>> > ;)
>> >
>> > On Tue, Feb 2, 2016 at 2:17 AM, James Cameron <[1]qu...@laptop.org>
>> wrote:
>> >
>> > A ToolButton normally has an Icon.
>> >
>> > Instead of the Icon, assign the ProgressIcon?
>> >
>> > As nobody else may have done this, you may need to find and fix any
>> > bugs in ProgressIcon or ToolButton that prevent it.
>> >
>> > On Mon, Feb 01, 2016 at 11:31:28PM +0530, Utkarsh Tiwari wrote:
>> > > Is there any way to use a ProgressIcon as a Toolbutton ?
>> > >
>> > > On 2/1/16, Sam P. <sam@sam.today> wrote:
>> > > > Hello!
>> > > >
>> > > > Maybe just a large down arrow and fill it vertically?  See
>> > > > 'emblem-downloads' or 'transfer-from' in sugar-artwork.
>> > > >
>> > > > Thanks,
>> > > > Sam
>> > > >
>> > > >
>> > > > On Mon, Feb 1, 2016 at 9:15 AM, Utkarsh Tiwari <[2]
>> > iamutkarshtiw...@gmail.com>
>> > > > wrote:
>> > > >
>> > > >> How should the Icon for "Download Button" look like? Could you
>> please
>> > > >> provide me some artwork for reference. ?
>> > > >>
>> > > >> On 2/1/16, Utkarsh Tiwari <[3]iamutkarshtiw...@gmail.com>
>> wrote:
>> > > >> > Omg! I have been looking all over internet on how to
>> integrate a
>> > > >> > Gtk.ProgressBar into Gtk.Toolbutton and I even tried using
>> > > >> > Gtk.CssProvider styler to scale down the progressbar to a
>> button :D
>> > > >> > Now that(ProgressIcon.py) sounds really cool!
>> > > >> >
>> > > >> > Thank you :) You made my work a bit easier ;)
>> > > >> >
>> > > >> > On 2/1/16, James Cameron <[4]qu...@laptop.org> wrote:
>> > > >> >> ProgressBar from Gtk is overkill, we already have a
>> ProgressIcon
>> > > >> >> in Sugar.
>> > > >> >>
>> > > >> >> In sugar-toolkit-gtk3:
>> > > >> >>
>> > > >> >> Look at progressicon.py, you will see it does not use a
>> > ProgressBar,
>> > > >> >> but has a __draw_cb method connected to the "draw" signal.
>> > > >> >>
>> > > >> >> Look at toolbutton.py, you will see it wraps ToolButton
>> do_draw
>> > > >> >> method.
>> > > >> >>
>> > > >> >> On Mon, Feb 01, 2016 at 12:10:25AM +0530, Utkarsh Tiwari
>> wrote:
>> > > >> >>> "The button to be a blend of ProgressIcon and ToolButton".
>> How to
>> > > >> >>> convert a Gtk.ProgressBar to a Browse ToolButton?
>> > > >> >>>
>> > > >> >>> On 1/27/16, Jam

Re: [Sugar-devel] Browse, vulnerable

[Sam P.]

Hi James,

Borwse could eaisly be ported now, as webkit 2.11.4 finally includes
essential apis for functionality. Maybe this will be for next cycle?

Will the newer webkit version be avliable downstream on OLPC OS, or will
you use the older webkit1 browse?

Thanks,
Sam

On Wednesday, February 3, 2016, James Cameron  wrote:
> An interesting blog post describing the situation with WebKit security
> updates:
>
> https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-security-updates/
>
> Browse in Sugar is without security updates because it depends on
> an old WebKit version of WebKitGTK+, and the great API break called
> WebKit2 has not yet been fixed in a Browse release.
>
> --
> James Cameron
> http://quozl.netrek.org/
> ___
> 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] Download Manager ProgressBar [DESIGN]

[Sam P.]

Hello!

Maybe just a large down arrow and fill it vertically?  See
'emblem-downloads' or 'transfer-from' in sugar-artwork.

Thanks,
Sam


On Mon, Feb 1, 2016 at 9:15 AM, Utkarsh Tiwari 
wrote:

> How should the Icon for "Download Button" look like? Could you please
> provide me some artwork for reference. ?
>
> On 2/1/16, Utkarsh Tiwari  wrote:
> > Omg! I have been looking all over internet on how to integrate a
> > Gtk.ProgressBar into Gtk.Toolbutton and I even tried using
> > Gtk.CssProvider styler to scale down the progressbar to a button :D
> > Now that(ProgressIcon.py) sounds really cool!
> >
> > Thank you :) You made my work a bit easier ;)
> >
> > On 2/1/16, James Cameron  wrote:
> >> ProgressBar from Gtk is overkill, we already have a ProgressIcon
> >> in Sugar.
> >>
> >> In sugar-toolkit-gtk3:
> >>
> >> Look at progressicon.py, you will see it does not use a ProgressBar,
> >> but has a __draw_cb method connected to the "draw" signal.
> >>
> >> Look at toolbutton.py, you will see it wraps ToolButton do_draw
> >> method.
> >>
> >> On Mon, Feb 01, 2016 at 12:10:25AM +0530, Utkarsh Tiwari wrote:
> >>> "The button to be a blend of ProgressIcon and ToolButton". How to
> >>> convert a Gtk.ProgressBar to a Browse ToolButton?
> >>>
> >>> On 1/27/16, James Cameron  wrote:
> >>> > No.
> >>> >
> >>> > The position marked by your cursor seems to be inside the URL entry
> >>> > box.
> >>> >
> >>> > I said between the URL entry box and the back button.
> >>> >
> >>> > Review the Browse source code that defines these objects.
> >>> >
> >>> > On Wed, Jan 27, 2016 at 11:39:03AM +0530, Utkarsh Tiwari wrote:
> >>> >> Is this the exact expected location you were talking about the
> >>> >> 'download button' as shown in the screenshot below?
> >>> >>
> >>> >> http://imgur.com/T0hirTZ
> >>> >>
> >>> >> On 1/27/16, James Cameron  wrote:
> >>> >> > Thanks for working on this.
> >>> >> >
> >>> >> > Our Sugar human interface guidelines and existing code base don't
> >>> >> > have
> >>> >> > decorated floating windows or window management.  Your proposal
> >>> >> > would
> >>> >> > not scale to multiple downloads.
> >>> >> >
> >>> >> > You might ask for design suggestions on this mailing list.
> >>> >> >
> >>> >> > I've resisted making design suggestions on this problem because I
> >>> >> > don't want to constrain the good ideas that may come up.
> >>> >> >
> >>> >> > To get the design conversation started ...
> >>> >> >
> >>> >> > When the first download begins, show a button at the top between
> >>> >> > the
> >>> >> > URL entry box and the back button.
> >>> >> >
> >>> >> > The button to be a blend of ProgressIcon and ToolButton, with the
> >>> >> > progress fill to show average progress of all downloads.
> >>> >> >
> >>> >> > When the button is pressed a download tab is to be shown in the
> >>> >> > canvas, which lists downloads and progress.
> >>> >> >
> >>> >> > The download tab can be closed like any other tab.
> >>> >> >
> >>> >> > The button is to be be hidden before any downloads are started,
> >>> >> > shown
> >>> >> > on start of first download, and only hidden if the download tab is
> >>> >> > closed when there are no downloads still active.
> >>> >> >
> >>> >> > On Tue, Jan 26, 2016 at 06:08:32PM +0530, Utkarsh Tiwari wrote:
> >>> >> >> Hi,
> >>> >> >>
> >>> >> >>  I am trying to integrate the "Download ProgressBar" in the
> >>> >> >> download
> >>> >> >> manager. Here is the screenshot of the prototype on which I am
> >>> >> >> currently
> >>> >> >> working -> [1]http://imgur.com/WUJL8eX
> >>> >> >>
> >>> >> >> Since the download progress bar is popping over the browse
> >>> >> >> activity,
> >>> >> >> is
> >>> >> >> it
> >>> >> >> feasible?
> >>> >> >>
> >>> >> >> regards,
> >>> >> >> Utkarsh Tiwari
> >>> >> >>
> >>> >> >> References:
> >>> >> >>
> >>> >> >> [1] http://imgur.com/WUJL8eX
> >>> >> >
> >>> >> >> ___
> >>> >> >> Sugar-devel mailing list
> >>> >> >> Sugar-devel@lists.sugarlabs.org
> >>> >> >> http://lists.sugarlabs.org/listinfo/sugar-devel
> >>> >> >
> >>> >> >
> >>> >> > --
> >>> >> > James Cameron
> >>> >> > http://quozl.netrek.org/
> >>> >> > ___
> >>> >> > Sugar-devel mailing list
> >>> >> > Sugar-devel@lists.sugarlabs.org
> >>> >> > http://lists.sugarlabs.org/listinfo/sugar-devel
> >>> >> >
> >>> >
> >>> > --
> >>> > James Cameron
> >>> > http://quozl.netrek.org/
> >>> >
> >>
> >> --
> >> James Cameron
> >> http://quozl.netrek.org/
> >>
> >
> ___
> 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] embedding a Twitter "Follow" and facebook follow

[Sam P.]

Hi Samson,

I think that you missed the point of what James said.  Facebook engages in
lots of tracking and questionable business practices, see the Stallman
article on this subject [1].  Maybe adding a link could be acceptable
(however do we want to send the message that we endorse facebook?), but I
would be against adding a "like button" - which allows facebook to run
whatever code they want on our page.

Also, why do we want Q on Facebook?  We already have social help, which
is arguably a platform better suited to hosting discourse (infact it uses a
software package called discourse which specialises in just that).  Social
help is also embedded in Sugar, whereas facebook is not.  Even if facebook
was a slightly better service for this, we are then allowing facebook
control over our communications with our users.  We are putting a lot of
trust in an for-profit company, which produces non-free software (ethically
opposite to Sugar) and allowing them to censor all of our communications
with users.  I'm not cool with that.

Thanks,
Sam

[1]  https://stallman.org/facebook.html

On Tue, Jan 26, 2016 at 6:59 PM samson goddy 
wrote:

> Sure that it helps track users location to know where your followers are
> coming from. Also its enables Question and Answers, live streaming in case
> we have some related sugar workshop. Attracts users to your page. lots more
> features
>
> > Date: Tue, 26 Jan 2016 18:44:57 +1100
> > From: qu...@laptop.org
> > To: samsongo...@hotmail.com
> > CC: samparkins...@gmail.com; market...@lists.sugarlabs.org;
> sugar-devel@lists.sugarlabs.org; dwg...@gmail.com
> > Subject: Re: [Sugar-devel] embedding a Twitter “Follow” and facebook
> follow
>
> >
> > Interesting idea.
> >
> > What is the privacy impact? Will a content element like this make it
> > possible for Twitter or Facebook to track our visitors? Is that
> > tracking consistent with Sugar Labs own policies on privacy? Will
> > Sugar Labs have a contract with Twitter or Facebook, or is the
> > relationship standard terms and conditions?
> >
> > On Tue, Jan 26, 2016 at 08:31:00AM +0100, samson goddy wrote:
> > > Hello,
> > >
> > > I am letting the community to know that, I am seeking to get a
> verified profile
> > > for both of our account in twitter and facebook. It looks like one of
> the steps
> > > is embedding a Twitter “Follow” and facebook follow in our official
> website in
> > > order to get verified. So i am requesting the developers to enable
> this on the
> > > our home page and probably on the sugar labs wiki.
> > >
> > > Thanks
> >
> >
> > --
> > James Cameron
> > http://quozl.netrek.org/
> > ___
> > 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] activity instance directory

[Sam P.]

Thanks for the good analysis James!

I don't think that deleting on startup is an optimal idea.  It is
counter-intuitive that the user must open every activity on their computer
when they want to reclaim space.  It is also bad in the case of
infrequently used activities.

I think that a multi-pronged approach would be better.  As you noted, the
activity clearing their tmp and instance folders themselves is optimal
(option 3).  I agree with this, as it takes load out of the shell process
and means that the filesystem space is reclaimed a quick as possible.

However, to deal with the issue of crashing or non-sugar3 activities, we
could also delete ALL tmp and instance folders during the shutdown process
(after stopping all activities is successful).  In the best case, this
should be as quick as running ls on all of the folders (which is quick
right?).  It also helps users who are upgrading their system and preserving
their .sugar directory.  The shell does also not need to be responsive
during shutdown.

Thanks,
Sam

On Wed, Jan 20, 2016 at 1:50 PM, James Cameron  wrote:

> The API documentation was wrong, and has been edited.
>
> https://wiki.sugarlabs.org/go/Development_Team/Low-level_Activity_API
>
> Rainbow did delete instance and tmp.  Sugar did not.
>
> Rainbow has not been in OLPC OS for some time.  (/etc/olpc-security
> must exist, /usr/bin/rainbow-run must be executable).
>
> Rainbow is not in other builds that use Sugar.
>
> Sugar activities that were coded for Rainbow, and against this
> documentation, will leave an instance and tmp directory on the
> system.  Every activity.
>
> Sugar must delete both directories.
>
> The next question is when?
>
>
> 0.  on reinstall of OLPC OS, or reboot of SoaS,
>
> This is what we do at the moment.
>
>
> 1.  on Sugar start,
>
> cleanup_temporary_files in sugar:src/jarabe/main.py might be extended,
> so that Sugar starts up and deletes the directories.
>
> Disadvantage is a small delay during Sugar start, the need to iterate
> over the bundle ids, and which list of bundles to use.
>
>
> 2.  on activity start,
>
> The activity factory module function get_environment() in
> sugar-toolkit-gtk3:src/sugar3/activity/activityfactory.py
> might be extended to delete first, before making the directories.
>
> Disadvantage is a small delay during activity start.
>
>
> 3.  on activity close
>
> In the Activity class method _complete_close() in
> src/sugar3/activity/activity.py we might delete the directories as the
> activity is closing.
>
> Disadvantage is that an activity that crashes won't delete the
> directories.
>
> Advantage is that any waste will be cleaned as soon as possible.
>
>
> 4.  on activity close in shell
>
> Disadvantage is that Sugar may be momentarily unresponsive when an
> activity closes or crashes.
>
>
> Can we work toward a consensus?
>
> My preference is on activity start, since that is the last time it
> must be done to be consistent with the design intent.  Are you
> registered on github?
>
> On Tue, Jan 19, 2016 at 01:47:23AM +0200, Tony Anderson wrote:
> > At a workshop I am giving in Rwanda, an XO got 'Journal Full'. It
> > turns out that the Browse instance folder was using 1.2GB of store.
> >
> > The low-level API says:
> >
> > $SUGAR_ACTIVITY_ROOT/instance/
> > This directory is used similar to a /var/tmp directory, being
> > backed by flash rather than by RAM. It is unique per instance. It is
> > used for transfer to and from the datastore (see keeping and
> > resuming). This directory is deleted when the activity exits
> > (specifically, as soon as all children of the activity's first
> > process die)
> >
> > However, apparently in 0.106 this directory is not being deleted.
> >
> > Tony
>
> --
> James Cameron
> http://quozl.netrek.org/
> ___
> 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] [Bugs] #4928 Sugar UNSP: keyboard control panel does not show

[Sam P.]

Can not reproduce on fedora 24 (rawhide if it is still that).

Please specify the version that the issue occurs on.

On Wednesday, 30 December 2015 3:14:52 PM AEDT, Sugar Labs Bugs wrote:

#4928: keyboard control panel does not show
-+--
   Reporter:  quozl  |   Owner:
   Type:  defect |  Status:  new
   Priority:  Unspecified by Maintainer  |   Milestone:  Unspecified
  Component:  Sugar  | Version:  Unspecified
   Severity:  Unspecified|Keywords:
Distribution/OS:  Unspecified|  Bug Status:  Unconfirmed
-+--
 We don't use it on OLPC OS, but if the keyboard control panel is installed
 and used it fails.  The control panel title bar is changed to Keyboard,
 but the control panel icons remain.

--
Ticket URL: 
Sugar Labs 
Sugar Labs bug tracking system




--
Sent using Dekko from my Ubuntu device
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Getting a few errors when following tutorials given in the Write your Own Activity page

[Sam P.]

Hi Mukund!

On Mon, Jan 18, 2016 at 5:24 PM, mukund code  wrote:

> Hi guys,
>
> I am new to Sugar. I am currently going through the tutorial posted here:
> https://developer.sugarlabs.org/activity.md.html
>
> I created a sample activity(using exactly the same instructions given in
> the tutorial). In the console, I noticed the following error:
>
> Error: Load timeout for modules: webL10n
> http://require.js.org/docs/errros.html#timeout
> onError
> onError
> checkLoaded
> (anonymous function)
>
> I tried:
> volo add webL10n
>
> It gave me a 301 error.
>

That's funny.  301 shouldn't be an error, 3xx codes are redirect codes [1].

I don't involve my self with too many crazy nodejs things, but presenting
a 3xx code as an error sounds well within the relm of possibility
for some of these funny libraries.


>
> I then tried:
> volo add https://github.com/fabi1cazenave/webL10n
>
> which successfully installed webL10n. But the error still appears in the
> console.
>

Did the info at [2] help?

If not, maybe post your activity on github and try to find
somebody who knows about this js stuff to have a look
(CC Lionel).


>
> Also, I am not able to load any dynamic content using mustache(despite
> having a successful volo add) or console log out a statement when
> "my-button" (
> https://developer.sugarlabs.org/activity.md.html#first%20steps) is
> clicked. I guess all of this is possible once js/activity.js. That loading
> happens via lib/require.js. But that script is giving me this error. I
> don't see any failed fetches in the Network tab of the console window also.
>

Where did you put the console.log statements in the code?
Were they within the require.js callback?
If so, maybe your problems are all interconnected.

Thanks,
Sam

[1]  http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.2
[2]  http://requirejs.org/docs/errors.html#timeout


>
> Would be glad if someone helped out.
> Thanks!
>
> ___
> 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] Default Collaboration Server

[Sam P.]

Hi All,

Currently Sugar defaults to using "jabber.sugarlabs.org" as a collaboration
server in Sugar on a Stick and other GNU distros (fedora, debian, etc.).
However, I propose that we change the default (this release!) to use the
local network (telepathy salut).  This is a feature is that is already in
sugar, and is used on XOs and normal computers.

Why?

* Better activity support.  Tubes are supported by salut, but not by gabble
(server based collab.).  This means that activities that haven't been
ported this cycle (most of them) will still work under salut (proposed
default), but will not work under gabble (current default)

* More contextual neighbourhood view.  You only see people on your local
WiFi (or wired) network.  This is more helpful for finding your friends
than the trawling the crowded jabber.sugarlabs.org neighbourhood.

* More features.  File transfers work via salut, but not via
jabber.sugarlabs.org

* More speed and less lag.  Jabber.sugarlabs.org is hosted in the mit.
While that is good if you are a student at the mit, it is very laggy if you
are in say Australia.  I prefer near instant collaberation provided by my
local network.  Even if you are at the mit, your wifi router is still
closer than jabber.sugarlabs.org (hopefully)

* Privacy.  Users (specifically kids) aren't by default sharing their names
and colours online and inviting others to send them things.

Is this ok?  Will defaulting to use salut (local network) cause any issues
for anyone?  Is this ok for the 108 cycle?

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

Re: [Sugar-devel] Approach

[Sam P.]

Hi Samson,

They are interesting in a way, and they seem to have a nice presentation
editor.  Maybe that could be something to hack with the new collab text
editor apis?

But I disagree with their approach many ways.  I was chatting with some
people about this and struggled to see pedagogical use of many of their
tools:

* "Quickfire" quiz thing - is talking to students hard?  Is it hard to get
them to pass you an answer on paper?  Well, spend a lot of time setting up
some computer thing instead!
* "Discuss" - too hard to get kids to put up hands to discuss something?
Too hard to get them into groups?  Too hard to "pair share pair" or
whatever strategy?  Have them talk at each other over the internet, after
wasting time fussing with tech.
* "Team Up" - too hard to get them into groups irl?  Too hard to let them
talk so they can work together?  Too hard to use a normal presentation app
to make slides?  Use this thing!

Overall, I think this represents an interesting trend in edu tech - making
normal classroom things digital.  This is a trend that I view as useless
from my experiences.  These are not useful tools for teachers to teach
with, it doesn't let the kids make things or research things.  The
currently successful devices in edu tech seem to be chromebooks - which
don't add a single thing that is educational.  Instead they have
collaboration for word processing, slides, etc.  Real tools for making real
stuff.

Spiral does make me thing about what our approach should be though (hint:
not like spiral) - making tools for kids to work together and make stuff.
Tools that teachers can use in their lesson plans.

Thanks,
Sam

On Sat, Jan 9, 2016 at 10:08 PM, samson goddy 
wrote:

> Someone tweeted @sugar_labs via twitter, asking if the sugarlabs might be
> interested in this application. But it seems like she does not know that
> Sugar Labs has an OS. But the interesting thing is the approach about the
> application. It will be really good to have something like this as an
> activity in Sugar OS so it might make work for teachers in school easier.
> Here is the link to the site http://spiral.ac/r/miB
>
> Samson
>
> ___
> 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] [Announcing] UNSTABLE 0.107.1 release (feature freeze)

[Sam P.]

Hi Tony,

This is serious.  If an activity wants to work in collaboration mode on a
NEW version of telepathy gabble, it needs to be ported not to use tubes.

However, your activity will still work on OLPC OS 13/14, Fedora 21 and
before and on the current Debian (???).  Your activity will still work
everywhere in single user mode.

Thanks,
Sam

On Mon, Jan 4, 2016 at 9:40 PM, Tony Anderson  wrote:

> Hi,
>
> Is this serious? No current activities will run on 0.107.
>
> Tony
>
> On 01/04/2016 04:55 AM, Peter Robinson wrote:
>
>> TL;DR  All activities need to be ported, and there will be a very small
>> >toolkit change.  The toolkit change has not yet landed.
>>
>
> ___
> 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] [Announcing] UNSTABLE 0.107.1 release (feature freeze)

[Sam P.]

Hi Peter,

There was an email thread going around on the status of the collab work on
sugar-devel.  That may be of interest to you.

TL;DR  All activities need to be ported, and there will be a very small
toolkit change.  The toolkit change has not yet landed.

Thanks,
Sam

On Mon, Jan 4, 2016 at 1:08 PM, Peter Robinson  wrote:

> Hi Martin,
>
> > Moving forward with our current development cycle, I am pleased to
> announce
> > the release of Sugar 0.107.1 (unstable). This release means that we have
> > officially passed the time [1] for including new features and that we
> must
> > start focusing on stability and bug fixing.
> >
> > This release comes with many improvements that are worth mentioning:
> >
> > Changing the Frame settings in the control panel no longer requires to
> > restart Sugar.
> > Added new keyboard controls to access and navigate the control panel.
> > The control panel can display the serial number for commodity hardware.
> > Multiple bundles can be installed at once using good old
> > sugar-install-bundle script.
> > The shell now claims file transfer channels so Empathy won't interfere
> > anymore.
> > Home views names can be changed now.
> > Neighborhood icons are no longer placed randomly.
> > Sugar can now start even when the disk is full.
> > More documentation for our gtk3 toolkit.
> > More fixes for the Sugar theme.
> > and even more [2].
>
> Does the even more include the fixing of collaboration? If not what is
> the status of that?
>
> Peter
> ___
> 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] [DESIGN RFC] In-Sugar Introduction (was: Onboarding)

[Sam P.]

Hi All,

Thanks for the responses to my proposal.

Through reading, I have realized that it was very arrogant to imply that
this was *the* onboarding for sugar.  Onboarding is more than any
individual tour, it is the journey that users take before they can get
value from Sugar.  This journey is going to compose of multiple parts.

So how does the current landscape look like (in my opinion)?  We have lots
of great content.  There are Iain's slideshows and Training activity among
many others.  However many of these systems take time out of the users
control.  They require the user to do what the content says for 10 minutes
or multiple hours respectively.  This is perfectly appropriate in some
situations, and these are both easy to read/understand systems for
delivering good content.

However, users not all users are in the situation to use those mechanisms.
Some may be eager start working on their systems, and be dismissive of the
tutorials (users which the in-sugar intro would benefit from the contextual
hotspots when they are lost).  Others may be forgetful, or not in a good
state of mind during less interactive training, and benefit from the
reminders.  Some users may be evaluating sugar, and would benefit from
getting started on their own adventures sooner, which would be facilitated
better by the in sugar introduction.

I have updated my proposal to include F6 frame activation, help activity,
shutting down.  The link is now with https, and hopefully less line breaks:
 https://www.sam.today/blog/sugar-onboard-design.html

I have not updated it to include a better way of displaying progress.  I
agree with Quozl that it would be beneficial, however I am completely
unsure of how to visually design it.  Suggestions are always welcome.

Regarding teaching hotkeys over mouse based interactions, I feel that this
is not suited for a tour (unless it a tour of vim that is).  I don't want
to scare the user away in their first sitting, by trying to make them
remember every single key combination.  I also feel that hot keys can could
be more easily explained by a poster as Tony suggested initially.  I will
attempt to create a poster to demonstrate this idea.

Regarding translations and the promise of iconography:  I believe that
iconography is great.  But I think it is a very hard task to generate
images that represent the complex ideas in the sugar UI, a task above
myself.

Tony also raised the issue of users varying level of familiarity with
computers in general.  I have probably aimed this introduction proposal at
somebody who has never used sugar, but is familiar with basic computer
manipulation (how to use a mouse, how to "mouse over" something, how to
click buttons) as well as assuming that they may be familiar with basic
types of applications (do I want to launch "Write"?  It is probably like
MicroSoft Word, so yes).  In order to work with users without this
knowledge, I would need to change the introduction content very much, and
maybe even the mechanism.  I would probably need to also help the user
through the intro screen (where name and colour are setup) as well.
However, I plan to aim at the first subset of users, then it may be
possible to re-use the technology for the latter subset of users.  It is a
completely different debate about how to teach via the screen somebody to
use a mouse though.

Thanks,
Sam

On Thu, Dec 31, 2015 at 11:33 PM, Iain Brown Douglas <
i...@browndouglas.plus.com> wrote:

> Hi Sam,
>
> This is a fine proposal and I cannot fault your 15 points.
> One comment, some are essential, "first ten minutes of use issues" and
> some might be seen as essential to getting productive.
>
> Of course onboarding runs at many levels, and may be significantly
> different for different user groups.
>
> Elsewhere on this thread you asked for feedback on two items:
>
> 1.  adding references to the F6 and other Function keys. I say yes, as I
> try to introduce Function keys early - it is more easy to teach small
> children key presses than mouse movements.
>
> 2. I think a hint to Help Activity would be good.
>
> Without wanting to detract from your proposal, it is interesting that
> https://www.useronboard.com/ itself uses a slideshow technology.
>
> In general I like this, as it allows the user to speed read the material
> and salient points are more easily revisited in a slideshow than a
> youtube or screencast type presentation.
>
>
> My own New to Sugar concept lives here:
> http://inkyfingers.github.io/gallery/new.html
>
> I would very much like to hear detailed critical response to my work.
>
> This might give us both some insight into avenues that might be most
> appreciated by users.
>
> Kudos to all involved in champion work on www.sugarlabs.org btw.
>
> All the best in 2016,
>
> Iain
>
>
> On Sun, 2015-12-27 at 17:20 +1100,

Re: [Sugar-devel] "Another osbuild instance is running" error

[Sam P.]

Hi Shraddha,

I think that the easiest plan of action is just to delete the lock file.

If the issue persists, you can delete the lock file again as a workaround
and file a bug or make a patch.

Thanks,
Sam

On Thu, Dec 31, 2015 at 9:08 AM, Shraddha Barke 
wrote:

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

Re: [Sugar-devel] [DESIGN RFC] Onboarding

[Sam P.]

Hi Tony,

Thank you for the comments on the proposal.

(For context, by onboarding I refer to the users first run experience.
Similar to [1].  Specifically something that helps them understand the
basics of sugar)

>From an implementation perspective it is important as you note to bind to
widgets rather than hard coded positions and recognise when the user
completes the task.  I think from that perspective, it would be very
complex to use a JSON file.  I would much prefer to have a singleton class
"Onboarder" (or whatever) which would have 2 main methods.
 "add_hotspot_over(hotspot, widget)" and simmilar for other places that
hotspots are placed over and "signal_hotspot_completed(hotspot)" which
signals that a hotspot has been completed.  There would then be a separate
list of hotspots and their content.  Having more of the implementation in
python in will give this flexability.

I feel that adding lots of different tutorial in different places almost
conflicts with our contextual help system (the help window that pops up).
I think that adding a small initial explanation/tutorial is a different
issue and targets a different need.  Does this need to be added to the
onboarding though (how to open the help)?

Supporting the F6 frame activation could be added, I will mock something up
tomorrow.

Earlier you mentioned that design should use more icons than text.  I think
that I could show screen shots of the expected result.  However, sometimes
I personally find icons can be more vauge than text for explaining ideas,
and I believe that some users may feel a similar way.  Therefore I believe
that the supplementary copy could be helpful for many users.  However, I
you point out the issue of translation loads.  Should the copy be hidden if
text is not available in the same language?

Thanks,
Sam

[1]  https://useronboard.com

On Wed, Dec 30, 2015 at 6:24 PM, Tony Anderson 
wrote:

> Some thoughts:
>
> Trigger this with the help button (see TurtleBlocks). If there is
> already a help, make the help button show options:
> help
> tutorial: how to launch an activity
>
> where tutorial is the Onboarding implementation. It should be possible to
> have more than one tutorial with some description of the purpose.
>
> Add a help button to the left of the home view button on the home view and
> the list view (list view help gives tutorial on list view.
> Add a help button to the right upper corner of the frame.
> Add a help button on the bottom bar of the Journal view (away from the
> mount icons but not in the far corner to avoid conflict with the frame)
> Add a help button on the top bar of the neighborhood and group views (to
> the right, away from the corner)
>
> Implement the system so that activity author/maintainers can create their
> own help button tutorials.
>
> Use a list of jsons to define the steps in the tutorial:
> [{'hotspot':'x,y,w,h','click':test for completion,}
>
> On the home view, at the deployments I support, pressing the alt key makes
> 'always start new' the default. This makes it easier to separate a
> deliberate attempt to resume a task (from the Journal) from a new task
> (from the Home view). With the above approach, the home view tutorial can be
> easily modified.
>
> For the frame, the corners are disabled so that the frame is only
> available from the frame key. This is essential for the original XO-1
> keyboard since moving the cursor to stop an activity almost invariably
> covers the button with the frame. It would be nice if the tutorial
> implementation had a way to show a keyboard hotspot (e.g. a on-screen
> keyboard) to show how to access various views from the keyboard.
>
> In the context of the proposal:
>
> Onboarding goals should be supported by the implementation but not
> limited.
>
> User flow: user clicks on help button and clicks on tutorial (if more
> than one option).
> home view tutorial shows how to launch an activity -
> but an activity has it's own help button and tutorial
>
> When a user completes an onboarding task, the window should flash through
> a huge tick, then fade away.
> a new hotspot appears to set up the next task.
>
> The image in the popup could be a screen shot showing the expected result
> of the previous task.
>
> So, in general, the tutorial definition should be separated from the
> tutorial mechanism.
>
> I suspect the 'hotspot' implementation to be relatively easy but the
> tricky code will be to determine whether the task was executed correctly.
>
> The hotspot mechanism must be able to handle changes. Suppose that a home
> view tutorial sets a task to launch 'Record' by placing a hotspot around
> the Record icon. The mechanism needs to find where the Record icon is on
> the home view, not just position it where Record shows in a
> freshly-installed Home View. The user (or deployment) could have added or
> removed activities from favorites.
>
> Tony
>

Re: [Sugar-devel] display blocker errors in f24 (rawhide) Soas live in koji

[Sam P.]

Hi Tom,

I'm running rawhide now and it looks like a mess due to the huge changes
this gtk cycle.

I attempted to patch some things [1], and that fixed some issues.  However,
the changes are simpily massive this release [2].  I think that we are
going to need to have gtk3 and gtk3.20 with different css files.

I am currently looking into patching this, however, I do find some of the
css node issues annoying.  Especially issues with css node styles taking
importance over the normal SugarXYZ styles.  This is further compounded by
the fact that the css node api is not public yet, and I don't think it was
planned for this release.  There will be horrible hacks.

Thanks,
Sam

[1]  https://github.com/sugarlabs/sugar-artwork/pull/84
[2]  https://blogs.gnome.org/mclasen/2015/11/20/a-gtk-update/

On Tue, Dec 29, 2015 at 11:47 AM, Thomas Gilliard 
wrote:

> Just a heads up:
>
> I am seeing these display blocker errors in f24 (rawhide) Soas live in
> koji [1]
> [1]  http://koji.fedoraproject.org/koji/taskinfo?taskID=12325079
>
> *Name creation screen
>
>  https://wiki.sugarlabs.org/go/File:Soas-f24-1.png
>
> *F3 Main Screen with wrong buttons
>
>  https://wiki.sugarlabs.org/go/File:Soas-f24-2.png
>
> * sugar control panel with missing text
>
>  https://wiki.sugarlabs.org/go/File:Soas-f24-3.png
>
> Is this due to gtk3 mismatches?
>
> Tom Gilliard
> satellit
> ___
> 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] Current status of collaboration work

[Sam P.]

Hi Gonzalo,

I agree with your perspective that we do need to make the wrapper the best
it can be before locking ourselves into it.  That is a good plan.

I'm not sure what you mean about adding a parameter to the setup method.
Could you please elaborate?

Thanks,
Sam

On Sat, Dec 26, 2015 at 10:55 AM, Gonzalo Odiard 
wrote:

> Hi Martin,
> I like your proposal of use the wrapper in the activities by at least one
> cycle, before include it in the toolkit.
> In our experience, once the code is included in the toolkit, is difficult
> make changes without breaking activities in
> unexpected ways.
> I didn't have time to make tests with the wrapper, and is really difficult
> do tests for collaboration. We have seen
> bugs that appear only when you have many computers, or using jabber but
> not when using the mesh, etc.
> I think the wrapper is a very, very good start (Thanks Sam and Walter) and
> even they provided patches for some activities.
> Sadly, some of the activities are on my hands, but I didn't have time the
> last months to do the proper testing
> and integration of the patches.
> About the wrapper API, just looking at the code, I think would be better
> add a callback parameter to the setup() method
> because the initialization is async and then is the only way to execute
> your activity code when the initialization
> has finished. Issues like this are difficult to get right at the first
> time.
> I know I am not doing almost any work in sugar these months, don't take
> these comments as a critic,
> just as a way to try to help, and avoid problems in the future.
> Regards,
>
> Gonzalo
>
>
>
> On Wed, Dec 23, 2015 at 4:52 PM, Martin Abente <
> martin.abente.lah...@gmail.com> wrote:
>
>> Hello everyone,
>>
>> I have been reviewing the current state of the collaboration proposals
>> and I am afraid it is still too early for merging it. We need to explore
>> more use cases, and this will only happens when we start porting more
>> Activities that actually use TUBES. Therefore, i want to share some
>> thoughts on this.
>>
>> *Opinions:*
>>
>>1. There haven't been enough changes in the Activities regarding
>>Tubes deprecation.
>>2. Dropping the Tubes support from Sugar without changing all the
>>activities that depend on Tubes means that we will break collaboration for
>>those activities anyway, and there wont be much gain by just doing that.
>>3. Making changes in the Sugar API without proper testing with more
>>activities (and scenarios) is simply not a good idea.
>>4. But, making changes in the Activities can be easily handled since
>>they are self contained.
>>5. Most of our users still use Fedora 18 through OLPC deployments,
>>where Tubes is available.
>>
>> *Suggestions:*
>>
>>1. Lets make Sugar handle the Tubes deprecation better so it doesn't
>>break, but lets not remove the support for TUBES yet.
>>2. Instead, we can start changing the activities using the Wrapper
>>that Walter and Sam prepared, but using it locally on each Activity for 
>> now.
>>3. Once and if, we have most of our activities ported to the new
>>telepathy API (which will be based on the Wrapper), then we can include 
>> the
>>Wrapper into sugar-toolkit-gtk3, in a next release and remove it from
>>Activities.
>>
>> *Pros:*
>>
>>1. We avoid breaking collaboration for *(a)* Activities that use
>>TUBES and run on older systems where TUBES is available, and *(b)*
>>Activities that does not use TUBES on newer systems where TUBES is no
>>longer available. This _is_ an improvement versus the current situation
>>where is completely broken on newer systems.
>>2. We do this whole re-work incrementally, without having to change
>>the API (sort of) blindly.
>>3. There will be more flexibility to explore ideas in Activities land.
>>
>> *Cons:*
>>
>>1. There will be repeated code in Activities, but that can be changed
>>easily later.
>>
>>
>> *What would be needed:*
>>
>>1. To detect if there is TUBES support, as Sam mentioned in his first
>>PR [1]. *Can someone look into this?*
>>2. Do not create TUBES channel when there is not support. This [2] is
>>just a hack and the logic works fine, but it depends on whether or not we
>>can detect support.
>>3. Cleanup the Wrapper and make sure that it is possible to use it
>>locally in activities.
>>
>> *Other improvements that we could land now:*
>>
>>1. Give more flexibility to activities to use file transfer channels
>>without having the shell messing with them. [3]
>>
>> *Conclusions:*
>>
>> If we don't do something about this, next Sugar releases will still be
>> broken for collaboration, for more scenarios than necessary.
>>
>>
>> Let me know what you guys think,
>> Martin.
>>
>> *Refs:*
>> [1] https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/270
>> [2]
>> 

Re: [Sugar-devel] Current status of collaboration work

[Sam P.]

Hi Tony,

Sorry that I was a bit vague in the previous email.  The collab wrapper is
not yet merged into sugar-toolkit-gtk3, however can be used by activities
by copying a script and including it in their activity.

The collabwrapper script is available here:
https://github.com/samdroid-apps/collabwrapper

The readme details how to import it using a try/catch statment, so that the
backwards compatible.  It also links to the documentation, which included
usage examples.

The collabwrapper uses only telepathy features used already in sugar -
namely the text channels (used by chat and other activities) and the file
transfer channels (used in journal for file transfers).  This means that if
collabwrapper.py (the standalone script) is included in your activity, it
should run in any Gtk3 sugar.

Collab wrapper does not yet work in gtk2 sugar, as it uses GObject
syntactic sugar that is only available in newer versions.  It also depends
on Gio for file transfers, and I will need to investigate how sugar gtk2
shell does the file transfers.

Thanks,
Sam

On Sat, Dec 26, 2015 at 5:44 PM, Tony Anderson 
wrote:

> Hi Sam,
>
> I am still not clear on the status. I have a long-dormant activity 'bingo'
> which depends on the caller sending 'bingo cards', receiving a 'bingo
> call', and being able to check the card via collaboration. In developing
> those features, should I use the collab wrapper? Is it available for 0.106?
> Where can I find the version of
> chat that uses it as an example to follow? The version installed on 0.106
> (13.2.5) does not seem to use it.
>
> Tony
>
>
> On 12/26/2015 01:55 AM, Gonzalo Odiard wrote:
>
> Hi Martin,
> I like your proposal of use the wrapper in the activities by at least one
> cycle, before include it in the toolkit.
> In our experience, once the code is included in the toolkit, is difficult
> make changes without breaking activities in
> unexpected ways.
> I didn't have time to make tests with the wrapper, and is really difficult
> do tests for collaboration. We have seen
> bugs that appear only when you have many computers, or using jabber but
> not when using the mesh, etc.
> I think the wrapper is a very, very good start (Thanks Sam and Walter) and
> even they provided patches for some activities.
> Sadly, some of the activities are on my hands, but I didn't have time the
> last months to do the proper testing
> and integration of the patches.
> About the wrapper API, just looking at the code, I think would be better
> add a callback parameter to the setup() method
> because the initialization is async and then is the only way to execute
> your activity code when the initialization
> has finished. Issues like this are difficult to get right at the first
> time.
> I know I am not doing almost any work in sugar these months, don't take
> these comments as a critic,
> just as a way to try to help, and avoid problems in the future.
> Regards,
>
> Gonzalo
>
>
>
> On Wed, Dec 23, 2015 at 4:52 PM, Martin Abente <
> martin.abente.lah...@gmail.com> wrote:
>
>> Hello everyone,
>>
>> I have been reviewing the current state of the collaboration proposals
>> and I am afraid it is still too early for merging it. We need to explore
>> more use cases, and this will only happens when we start porting more
>> Activities that actually use TUBES. Therefore, i want to share some
>> thoughts on this.
>>
>> *Opinions:*
>>
>>1. There haven't been enough changes in the Activities regarding
>>Tubes deprecation.
>>2. Dropping the Tubes support from Sugar without changing all the
>>activities that depend on Tubes means that we will break collaboration for
>>those activities anyway, and there wont be much gain by just doing that.
>>3. Making changes in the Sugar API without proper testing with more
>>activities (and scenarios) is simply not a good idea.
>>4. But, making changes in the Activities can be easily handled since
>>they are self contained.
>>5. Most of our users still use Fedora 18 through OLPC deployments,
>>where Tubes is available.
>>
>> *Suggestions:*
>>
>>1. Lets make Sugar handle the Tubes deprecation better so it doesn't
>>break, but lets not remove the support for TUBES yet.
>>2. Instead, we can start changing the activities using the Wrapper
>>that Walter and Sam prepared, but using it locally on each Activity for 
>> now.
>>3. Once and if, we have most of our activities ported to the new
>>telepathy API (which will be based on the Wrapper), then we can include 
>> the
>>Wrapper into sugar-toolkit-gtk3, in a next release and remove it from
>>Activities.
>>
>> *Pros:*
>>
>>1. We avoid breaking collaboration for *(a)* Activities that use
>>TUBES and run on older systems where TUBES is available, and *(b)*
>>Activities that does not use TUBES on newer systems where TUBES is no
>>longer available. This _is_ an improvement versus the current situation
>>where is completely 

Re: [Sugar-devel] Current status of collaboration work

[Sam P.]

Hi James,

On Sat, Dec 26, 2015 at 2:28 PM, James Cameron  wrote:

> Thanks all for the thread and replies.
>
> I'm not sure I understand the situation fully yet, but I'll make some
> comments regardless.  Hopefully any disconnect between my comments and
> your understanding will help fix mine.
>
> I've learned long ago, to not change network protocols in a way that
> breaks things.  Interoperability is critical, regardless of difficulty
> of implementation or complexity.
>
> The Tubes API is effectively a network protocol.
>
> If we release a version of Sugar that is incompatible with previous
> versions of Sugar, at a network protocol level, what will happen?
>

The tubes API is kind of a network protocol.  We also can't drop tubes from
sugar per se, activities consume raw tubes.  On telepathy versions that
tubes are not avaliable, we never give any channels to the activity because
we wait (forever) for a tube.  If the activity requires a tube, but sugar
does not give it one, it will also break in unexpected ways.

In effect, if the user is using a "new" (not using tubes) activity things
will work on any system where it gives the text channel to the activity.
This included old sugar 98 systems, OLPC OS 13/14 systems and patched
fedora 24 systems.

If these users are updating their activities, everything will be fine.
Moving away from tubes will mean that the "old" (tubes) version of the
activity can not collaberate with the "new" (non tubes) version of the
activity.  However, if both users update their activities, all is well.


>
> If we release a version of an activity with incompatibility, what
> will happen?
>
> We've seen what happens, even with the trivial problems introduced by
> the activity.info file and the Gtk3 port.  The bias of the first
> failure report is severe and lasting.  Our users don't upgrade.  They
> persist with an old version of Sugar, like 0.96 on OLPC OS 12.1.0.  In
> effect, they ignore the Sugar developer community until the job is
> finished, the problems are fixed, or sufficient reasons are built up
> to upgrade.  During which we have no end-user feedback into the
> development process.  It has taken years to recover from the post-0.96
> breakage.
>
> Tony made a remark about Fedora amok.  Perhaps it was deeper than
> that, perhaps it was a failure of advocacy for the Tubes API, in the
> context of the Telepathy community, by members of the Sugar Labs
> developer community.  Rhetorical; did they know we were using it?
>
> If it was a failure of advocacy, we must expect further instances.
> Some other API will disappear.
>

*Looks at WebKit2*

I should probably comment more on that webkit ticket.


>
> I've seen no detailed analysis of adopting the Tubes API into Sugar.
> Why not?  What is so hard about taking the latest version of Tubes API
> and integrating it into the Sugar code base in a way that we can
> continue to use it?
>

There is no new tubes api.  And porting to a DBusTube channel or StreamTube
channel is probably as hard as porting to CollabWrapper - most of the
activity collab code is spend on tube initiation.  It believe that it is
obviously advantageous to move the collaboration setup code into a shared
wrapper, rather than migrate it from tube initiation to DBusTube
negotiation.


>
> Pull request 282 mentions 0.17.25, but of what package?  When did the
> Tubes API get removed from the Telepathy packages?  Yes, for Fedora it
> was 22, but we care about other downstreams.
>

I reference the telepathy spec version.  However, I do not know and can not
find where these map into telepathy-{gabbel,salut} versions.

You also touch on gabble vs salut later on and mention that salut still
supports tubes.  Maybe salut should be our new default then given it
supports older activities?  (also, jabber.sugarlabs.org is way to busy to
find any buddies!)


>
> On Fedora 18 builds with Sugar 0.107.0, I'm using
>
> telepathy-mission-control 5.14.0
> telepathy-salut 0.8.1
> telepathy-gabble 0.16.7
> python-telepathy 0.15.19
> telepathy-glib 0.20.4
>
> On Fedora 20 builds, I'm using
>
> telepathy-mission-control 5.16.3
> telepathy-salut 0.8.1
> telepathy-gabble 0.18.2
> python-telepathy 0.15.19
> telepathy-glib 0.22.0
>
> On Ubuntu 14.04 builds with Sugar 0.107.0, I'm using
>
> telepathy-mission-control 5.16.1
> telepathy-salut 0.8.1
> telepathy-gabble-legacy 0.16.7
> python-telepathy 0.15.19
> libtelepathy-glib0 0.22.1
>
> On Ubuntu 15.10 builds with Sugar 0.107.0, I'm using
>
> telepathy-mission-control 5.16.3
> telepathy-salut 0.8.1
> telepathy-gabble-legacy 0.16.7
> python-telepathy 0.15.19
> libtelepathy-glib0 0.24.1
>
> On Fedora 24 koji.fedoraproject.org says we'll expect
>
> telepathy-mission-control 5.16.3
> telepathy-salut 0.8.1
> telepathy-gabble 0.18.2
> python-telepathy 0.15.19
> telepathy-glib 0.24.1
>
> I don't have a test case for collaboration failure due to Tubes API
> missing.  The feature page doesn't say.  I can't find a bug report.
>

[Sugar-devel] [DESIGN RFC] Onboarding

[Sam P.]

Hi All,

Sugar has a novel user interface, with lots of beautiful and logical
things.  However, there are some important elements (such as the frame or
journal) that are not familiar or intuitive to new users.  This is an
issue, as sugar currently relys upon exploration as our only user
onboarding strategy.

The un-intuitiveness of our ui comes up every now and again.  I previously
conducted a small and probably skewed survey, however the lack of user
onboarding and the effects of that (how users did not understand the
interface) were apparent.  It's also written about in Jeff Atwood's (old)
article "the Sugar UI", where he says, "I have to admit that I didn't find
the Sugar UI particularly intuitive or discoverable, even after using it
for 10 minutes and learning the basics."

Please have a look at my design proposal to add help for new users [1].  No
implementation has been done (as you would expect due to the time in the
release cycle), and comments would be appreciated to create a great design
before even thinking of implementing.

Thanks,
Sam

[1] http://www.sam.today/blog/sugar-onboard-design.html
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Current status of collaboration work

[Sam P.]

Hi Martin,

On Thu, Dec 24, 2015 at 6:52 AM, Martin Abente <
martin.abente.lah...@gmail.com> wrote:

> Hello everyone,
>
> I have been reviewing the current state of the collaboration proposals and
> I am afraid it is still too early for merging it. We need to explore more
> use cases, and this will only happens when we start porting more Activities
> that actually use TUBES. Therefore, i want to share some thoughts on this.
>
> *Opinions:*
>
>1. There haven't been enough changes in the Activities regarding Tubes
>deprecation.
>2. Dropping the Tubes support from Sugar without changing all the
>activities that depend on Tubes means that we will break collaboration for
>those activities anyway, and there wont be much gain by just doing that.
>3. Making changes in the Sugar API without proper testing with more
>activities (and scenarios) is simply not a good idea.
>4. But, making changes in the Activities can be easily handled since
>they are self contained.
>5. Most of our users still use Fedora 18 through OLPC deployments,
>where Tubes is available.
>
> *Suggestions:*
>
>1. Lets make Sugar handle the Tubes deprecation better so it doesn't
>break, but lets not remove the support for TUBES yet.
>2. Instead, we can start changing the activities using the Wrapper
>that Walter and Sam prepared, but using it locally on each Activity for 
> now.
>3. Once and if, we have most of our activities ported to the new
>telepathy API (which will be based on the Wrapper), then we can include the
>Wrapper into sugar-toolkit-gtk3, in a next release and remove it from
>Activities.
>
> *Pros:*
>
>1. We avoid breaking collaboration for *(a)* Activities that use TUBES
>and run on older systems where TUBES is available, and *(b)*
>Activities that does not use TUBES on newer systems where TUBES is no
>longer available. This _is_ an improvement versus the current situation
>where is completely broken on newer systems.
>2. We do this whole re-work incrementally, without having to change
>the API (sort of) blindly.
>3. There will be more flexibility to explore ideas in Activities land.
>
> *Cons:*
>
>1. There will be repeated code in Activities, but that can be changed
>easily later.
>
>
> *What would be needed:*
>
>1. To detect if there is TUBES support, as Sam mentioned in his first
>PR [1]. *Can someone look into this?*
>
>
I looked into this a while ago, and it didn't seem that it would be easy.
Maybe we could add a gsetting that defaults to off (for new distros) and
then OLPC OS Builder can turn it on to say give activities tubes?

>
>1.
>2. Do not create TUBES channel when there is not support. This [2] is
>just a hack and the logic works fine, but it depends on whether or not we
>can detect support.
>
>
>1. Cleanup the Wrapper and make sure that it is possible to use it
>locally in activities.
>
> Yep, the wrapper can already be used locally in activities, see
Bibliography activity [1] and physics activity [2].

However, I do believe that the fact that activities are using a wrapper
doesn't stop up from also having it in sugar3.  As you noted, it is
repeated code in activities.  It is easier to change the sugar3 code later
as needed than to change the wrapper code in every activity.  Therefore, I
believe that we should have a try/except clause to preference the sugar3
wrapper, but fallback to the local one.



> *Other improvements that we could land now:*
>
>1. Give more flexibility to activities to use file transfer channels
>without having the shell messing with them. [3]
>
> As a note, the wrapper makes heavy use of file transfers (eg. for init)
currently.  This does result in shell notifications on older Sugars,
although the activities can still collaborate.

Good write up by the way.

Thanks,
Sam

[1] https://github.com/samdroid-apps/bibliography-activity/tree/collab
[2] https://github.com/walterbender/physics/pull/10


> *Conclusions:*
>
> If we don't do something about this, next Sugar releases will still be
> broken for collaboration, for more scenarios than necessary.
>
>
> Let me know what you guys think,
> Martin.
>
> *Refs:*
> [1] https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/270
> [2]
> https://github.com/tchx84/sugar-toolkit-gtk3/commit/bed0ac5f4259ff1669323db26acb27f5d9c8ed1f
> [3] https://github.com/sugarlabs/sugar/pull/621
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Current status of collaboration work

[Sam P.]

Hi Tony,

On Thu, Dec 24, 2015 at 5:35 PM, Tony Anderson <tony_ander...@usa.net>
wrote:

> Hi,
>
> It would really be helpful for us to get an explanation when working
> activities are deliberately broken ('deprecated') as in this case. What is
> the new means to implement collaboration? What advantage does it offer to
> the 'tubes' method we have been using from the beginning? Is this another
> example of Fedora run amok?
>

Ok, so there is a feature page which gives some background on all of this:
http://wiki.sugarlabs.org/go/Features/Fixing_Collab_(Tubes)

Activities were not deliberately broken, that is quite strong language to
be using about telepathy apis anyway.

Telepathy has channels, which activities can use to communicate.  There are
text channels, file transfer channels, and even tubes channels.  However
tubes had an interesting (read, bad) design that it re-invented the channel
negotiation (requesting a new channel, etc.) inside a channel!  What a
crazy design.  The telepathy developers manual also says that it was
deprecated because it lacked extendibility.

Either way, upstream (telepathy in this case) deprecated the api.  This
happened around 7 years ago.  (At least, there are 7 year old or so tickets
in BSLO noting the deprecation).  Anyway, for 7 years the api remained in
telepathy and nobody was too bothered.  But recently (whatever telepathy
version made it into fedora 22) the api was removed, which breaks sugar and
sugar activities ability to collaborate.  This is a very reasonable
deprecation timeframe in my opinion, and telepathy had all right to remove
the api.  Importantly, this is not fedora running amok.

>
> As you say, the traditional way to handle this particular case would be to
> re-write the 'tubes' api using whatever the new method is so that the
> existing
> applications do not have to be modified. This, after all, was the purpose
> of 'object programming'.
>

Well, that would be very painful.  The 'tubes' api is not an api provided
by sugar, it is provided by telepathy.

Some of the tubes api concepts (eg. multiple tubes within 1 channel), don't
map very well at all to the modern telepathy ideas.  It would be pretty
messy.

Every activity that uses tubes also has 160 lines of code dedicated to
negotiating the tubes, all of which are subtly different in annoying ways
(like copy, paste, change code reuse).  It would be a testing nightmare to
get this crazy tubes wrapper to work on all the activities.

>
> It is really frustrating when one is trying to provide new capabilities
> for the XO to have to spend almost all of the time re-implementing
> activities that have stopped working in the newer releases.
>

Well, this won't effect XOs unless somebody gets fedora 22+ running on them
(most run f18, there is alpha image of f20 for XO4).  As Martin proposed,
we can keep the old behaviour and the old activities will still run, on
older systems.

While it is annoying to have to port activities to a new, simple
abstraction, in the end it makes it easier for you to provide new
capabilities for XOs.  Adding collaboration will not require copy-and-pray
coding with 100s of lines of boilerplate.  Instead you can use a simple,
document api:
http://people.sugarlabs.org/sam/docs-collab-wrapper-try2/sugar3.presence.wrapper.html

Thanks,
Sam


>
> Tony
>
>
>
>
> On 12/24/2015 12:34 AM, Sam P. wrote:
>
> Hi Martin,
>
> On Thu, Dec 24, 2015 at 6:52 AM, Martin Abente <
> martin.abente.lah...@gmail.com> wrote:
>
>> Hello everyone,
>>
>> I have been reviewing the current state of the collaboration proposals
>> and I am afraid it is still too early for merging it. We need to explore
>> more use cases, and this will only happens when we start porting more
>> Activities that actually use TUBES. Therefore, i want to share some
>> thoughts on this.
>>
>> *Opinions:*
>>
>>1. There haven't been enough changes in the Activities regarding
>>Tubes deprecation.
>>2. Dropping the Tubes support from Sugar without changing all the
>>activities that depend on Tubes means that we will break collaboration for
>>those activities anyway, and there wont be much gain by just doing that.
>>3. Making changes in the Sugar API without proper testing with more
>>activities (and scenarios) is simply not a good idea.
>>4. But, making changes in the Activities can be easily handled since
>>they are self contained.
>>5. Most of our users still use Fedora 18 through OLPC deployments,
>>where Tubes is available.
>>
>> *Suggestions:*
>>
>>1. Lets make Sugar handle the Tubes deprecation better so it doesn't
>>break, but lets not remove the support for TUBES yet.
>>2. Instead, we can start chan

Re: [Sugar-devel] sugar-build on F23

[Sam P.]

Hi,

Broot is disabled by default on fedora these days.

Did adding the folder fix that?

Thanks,
Sam

On Tue, Dec 8, 2015, 2:24 AM Walter Bender  wrote:

> Yes. I didn't disable broot. I'll test again and try to get you a log file.
>
> -walter
>
> On Mon, Dec 7, 2015 at 10:19 AM, Martin Abente <
> martin.abente.lah...@gmail.com> wrote:
>
>> Hi Walter,
>>
>> Are you using broot (default)? I only tested with broot disabled and I
>> didn't get that error...
>>
>> Can you paste the log here to see what exactly is asking for that file?
>>
>> Regards,
>> Martin.
>>
>> On Mon, Dec 7, 2015 at 12:30 AM, Walter Bender 
>> wrote:
>>
>>> FYI, I finally upgraded to F23 and made a fresh sugar-build. Ran into
>>> one problem:
>>>
>>> /home/walter/sugar-build/build/out/install/etc/gconf was not created, so
>>> build failed. Adding the directory by hand and all was well.
>>>
>>> Also, I managed to break Turtle Blocks in v212. Patch coming ASAP.
>>>
>>> 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
>>>
>>>
>>
>
>
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
> ___
> 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] [IAEP] Membership deadline.

[Sam P.]

Hi James,

On Tue, Dec 1, 2015 at 9:17 AM, James Cameron  wrote:

> On Mon, Nov 30, 2015 at 10:34:11PM +0300, Dan Tenason wrote:
> > [...]  Secondly there are six candidates for seven open positions on
> > the oversight board.  [...]
>
> I can't find good evidence of that.  I perceive three candidates.
>
> Wiki page said "copied over from last year".  Can also be edited by
> anybody, not just the board.
>
> Looking at the edit history, the three candidates are;
>
> - Adam Holt (self edit, 4th November),
>
> - Walter Bender (self edit, 11th November), and;
>
> - Sam Parkinson (self edit, 1st December).
>
> But not Gonzalo Odiard (edited out by himself on 14th November, but
> reverted by Sam on 29th November).
>

I believe that was a mistake that I reverted Gonzalo's commit.  I'm am very
confused by media wiki in general.

Ignacio will also be nominating, however he currently is having issues
logging into the wiki.

Thanks,
Sam


>
> So I've moved the "copied over" tag accordingly.
>
> > In a quick search, I could not find any participation by at least
> > one of the candidates on any of the SugarLabs communication channels
> > since 2013. This opens a few options: Postpone the filing deadline
> > and subsequent election.  Appoint the the current candidate list
> > leaving one slot open. Reduce the size of the board to fire members
> > and hold the election as scheduled.
>
> I agree; if the candidates are less than the seats, then there is no
> election.  Good news; as elections are expensive.
>
> > Or, one might seek to understand why interest in Sugar and Sugarlabs
> > continues to decline.
>
> No, the governance of an organisation should not be distracted by
> such matters.
>
> --
> James Cameron
> http://quozl.netrek.org/
> ___
> IAEP -- It's An Education Project (not a laptop project!)
> i...@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/iaep
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [Announcing] UNSTABLE 0.107.0 release

[Sam P.]

Hi Peter,

For porting browse activity, we need upstream changes.  Part of them are
written, but not the bindings.  We need a new api to save and restore
state.  I should chase that up at some point.

Otherwise, the port will be very easy.

I'm not sure why we ship webkit2 though, because I'm not sure anyone uses
it.

Thanks,
Sam

On Fri, Nov 27, 2015, 8:47 PM Peter Robinson  wrote:

> > As an official kick-off for the 0.108 development cycle [1], we have
> > released a new UNSTABLE version of Sugar. This first 0.107.x release
> > includes a fair amount of changes and fixes, so please help us testing
> it!
> >
> > Tarballs:
> >
> http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.107.0.tar.xz
> >
> http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.107.0.tar.xz
> >
> http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.107.0.tar.xz
> >
> http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.107.0.tar.xz
> >
> http://download.sugarlabs.org/sources/sucrose/glucose/sugar-runner/sugar-runner-0.107.0.tar.xz
>
> This is now in Fedora 24, sorry for the delay in pushing this.
>
> > The major goal for the final 0.108 release is to get collaboration fixed,
> > but we just recently got some progress thanks to Sam and Walter,
> therefore I
> > have updated the roadmap [1] with new deadlines to make sure we have
> time to
> > work on this. Note that the work needed to reach this goal is not
> trivial,
> > therefore, I am willing to be flexible with our deadlines for this cycle,
> > depending on the progress.
>
> I see "Catch up with more Gtk changes." as a goal too, the changes for
> WebKit2 would be useful in this list, this affects only Browse but it
> means we end up shipping two WebKit stacks which are LARGE! It might
> be as simple as just detecting new bindings and doing "if v2 import X
> else import y" for the bindings, I don't know webkit though :)
>
> Peter
> ___
> 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] ./osbuild shell not valid command

[Sam P.]

Hi Jerry,

A COPR would be amazing!  I think that it would be amazing to have a set of
rpms for the master branch automatically built.

But I think there is still a role for sugar-build for like building and
developing :)  It's very bad for testing though.

Re the test suite:  good idea.  I have no idea why it doesn't run now and I
don't have the time to dive into it now.

Thanks,
Sam

On Tue, Nov 24, 2015 at 7:07 PM, Jerry Vonau <m...@jvonau.ca> wrote:

> Sam/others who might chime in.
>
> There has to be a better way than that, in the past there was automatic
> testing that replied on COPR(a web based rpm build system for Fedora)
> building the rpms. What is missing from git for packaging is a rpm spec.in
> for Fedora and whatever Debain uses that could be set via the Makefile,
> officially blessed by SugarLabs for other developers. Fedora has their spec
> file under git control for their release purposes, same holds true at OLPC
> where rpms are created for the XO's use but there is no reason not to have
> the packaging files freely available anyway, with that in place generating
> rpm out of git becomes so much easier. This will greatly help with testing
> as then anybody can now point COPR at their own git repo to generate a
> snapshot and build the rpms to test without having to roll the source rpm
> first. All you need to do is dnf enable your own copr repo and dnf update
> and test away like how I tested the issues with F23. Now making things
> easier for everybody should help trying to make sugar better, that is the
> objective right? It opens the possibility that someone can resurrect the
> automatic test suite that was in place in the past working again.
>
> Jerry
>
> > On November 23, 2015 at 8:33 PM Free Dom <freedompop123...@gmail.com>
> > wrote:
> >
> >
> > Is there an alternative since I am on Fedora 23?
> >
> > On Mon, Nov 23, 2015 at 8:32 PM, Free Dom <freedompop123...@gmail.com>
> > wrote:
> >
> > > I am on Fedora 23.
> > >
> > > ./osbuild shell
> > >
> > >
> > > On Mon, Nov 23, 2015 at 8:28 PM, Sam P. <sam@sam.today> wrote:
> > >
> > >> Hi,
> > >>
> > >> What distribution are you on?  I don't know if osbuild shell works on
> > >> fedora because broot is not used.
> > >>
> > >> You should be able to not use the shell though.  Eg. ./osbuild run,
> > >> ./osbuild pull, ./osbuild build, etc.
> > >>
> > >> Thanks,
> > >> Sam
> > >>
> > >> On Tue, Nov 24, 2015, 1:25 PM Free Dom <freedompop123...@gmail.com>
> > >> wrote:
> > >>
> > >>> I am getting this error every time I attempt to run ./osbuild shell
> > >>> from
> > >>> the guide at https://developer.sugarlabs.org/dev-environment.md.html
> > >>>
> > >>>
> > >>> Is there a dependency I am missing?
> > >>> ___
> > >>> 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] AbiWord 3.next release plans

[Sam P.]

Hi Hubert,

I cloned the abiword repository (r35148) and built abiword with the
following options:

./configure --enable-collab-backend-sugar --enable-plugins="collab"

This triggers no compilation errors, only deprecation warnings about Gtk.
The gtk deprecations are from the zebra striping
(gtk_tree_view_set_rules_hint), which has been removed from gtk so it
doesn't want that hint any more.  (Removing the zebra striping needed like
a massive announcement, but it didn't seem to get any).  You can remove
those 2 calls to gtk_tree_view_set_rules_hint in the collab code and it
still runs fine.

Only the "service" backend depends on GNU tls.  I believe that this is the
abicollab.net backend, but I'm not sure.

This seems to indicate that the sugar backend is ok for now, and that's the
backed that bothers me.

Thanks,
Sam

On Mon, Nov 23, 2015 at 2:36 PM, Hubert Figuière 
wrote:

> On 22/11/15 06:25 PM, Martin Edmund Sevior wrote:
>
> > Sorry for not responding sooner. In general Hub I agree with your
> > plans for abiword-3.1 however I would vote against depreciating the
> > abicollab plugin. The abicollab.net service is up and running though
> > I don’t know how much longer Marc Maurer will maintain it.
>
> Now I have another problem about that service: I don't even have the
> possibility to install a server, even to test.
> So maybe there need to be a plan for that.
>
> > I didn't realise the gnutls API had changed. I don’t know if I'll get
> > the time to fit it for GNUtls > 3.4 but I'd like to see if get it
> > running again.
>
> They have changed for quite a while. We got compilation warnings for a
> bit. Like the collab plugin trigger a good bunch of Gtk deprecation
> warnings that needs to be fixed...
>
>
> Hub
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] ./osbuild shell not valid command

[Sam P.]

Yes.  To build and run Sugar, use:

./osbuild run

To run the tests, use:

./osbuild test

On Tue, Nov 24, 2015, 1:33 PM Free Dom <freedompop123...@gmail.com> wrote:

> Is there an alternative since I am on Fedora 23?
>
> On Mon, Nov 23, 2015 at 8:32 PM, Free Dom <freedompop123...@gmail.com>
> wrote:
>
>> I am on Fedora 23.
>>
>> ./osbuild shell
>>
>>
>> On Mon, Nov 23, 2015 at 8:28 PM, Sam P. <sam@sam.today> wrote:
>>
>>> Hi,
>>>
>>> What distribution are you on?  I don't know if osbuild shell works on
>>> fedora because broot is not used.
>>>
>>> You should be able to not use the shell though.  Eg. ./osbuild run,
>>> ./osbuild pull, ./osbuild build, etc.
>>>
>>> Thanks,
>>> Sam
>>>
>>> On Tue, Nov 24, 2015, 1:25 PM Free Dom <freedompop123...@gmail.com>
>>> wrote:
>>>
>>>> I am getting this error every time I attempt to run ./osbuild shell
>>>> from the guide at
>>>> https://developer.sugarlabs.org/dev-environment.md.html
>>>>
>>>>
>>>> Is there a dependency I am missing?
>>>> ___
>>>> 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] ./osbuild shell not valid command

[Sam P.]

Hi,

What distribution are you on?  I don't know if osbuild shell works on
fedora because broot is not used.

You should be able to not use the shell though.  Eg. ./osbuild run,
./osbuild pull, ./osbuild build, etc.

Thanks,
Sam

On Tue, Nov 24, 2015, 1:25 PM Free Dom  wrote:

> I am getting this error every time I attempt to run ./osbuild shell from
> the guide at https://developer.sugarlabs.org/dev-environment.md.html
>
>
> Is there a dependency I am missing?
> ___
> 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] ./osbuild shell not valid command

[Sam P.]

Please file a bug describing how you encountered that issue.

For a quick fix "rm .lock .lock*"

On Tue, Nov 24, 2015, 1:36 PM Free Dom <freedompop123...@gmail.com> wrote:

> What if another osbuild instance is running?
>
> On Mon, Nov 23, 2015 at 8:35 PM, Sam P. <sam@sam.today> wrote:
>
>> Yes.  To build and run Sugar, use:
>>
>> ./osbuild run
>>
>> To run the tests, use:
>>
>> ./osbuild test
>>
>> On Tue, Nov 24, 2015, 1:33 PM Free Dom <freedompop123...@gmail.com>
>> wrote:
>>
>>> Is there an alternative since I am on Fedora 23?
>>>
>>> On Mon, Nov 23, 2015 at 8:32 PM, Free Dom <freedompop123...@gmail.com>
>>> wrote:
>>>
>>>> I am on Fedora 23.
>>>>
>>>> ./osbuild shell
>>>>
>>>>
>>>> On Mon, Nov 23, 2015 at 8:28 PM, Sam P. <sam@sam.today> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> What distribution are you on?  I don't know if osbuild shell works on
>>>>> fedora because broot is not used.
>>>>>
>>>>> You should be able to not use the shell though.  Eg. ./osbuild run,
>>>>> ./osbuild pull, ./osbuild build, etc.
>>>>>
>>>>> Thanks,
>>>>> Sam
>>>>>
>>>>> On Tue, Nov 24, 2015, 1:25 PM Free Dom <freedompop123...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> I am getting this error every time I attempt to run ./osbuild shell
>>>>>> from the guide at
>>>>>> https://developer.sugarlabs.org/dev-environment.md.html
>>>>>>
>>>>>>
>>>>>> Is there a dependency I am missing?
>>>>>> ___
>>>>>> 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] AbiWord 3.next release plans

[Sam P.]

Hello Hubert,

(Sorry about the reply formatting, I saw this post on the archive and I
suppose this is how to reply to things)

>  Proposal:
>  -I'd like to deprecate the collab plugin: for AbiCollab, we don't have
the server. For the other protocol, we can't maintain them. Deprecation
would go by only allowing explicitely building it. I already had to disable
the code based on GNUtls api breakage.

I contribute downstream to Sugar and we use AbiWord in sugar because of the
awesome AbiCollab plugin.  Specifically, we use the sugar backend (which
uses dbus), and then manage all the dbus over telepathy things from our
side.

It seems to work great, so I suppose that is a testimony to your good
maintainership.  If it's needed, I'm interested in getting involved to make
sure that this plugin stays on.

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

Re: [Sugar-devel] System alerts ui in sugar [DESIGN]

[Sam P.]

Hi James,

On Mon, Nov 2, 2015 at 9:58 AM, James Cameron <qu...@laptop.org> wrote:

> Summary: counter proposal, use modal alerts.  +Subject-tag [DESIGN].
>
> On Sun, Nov 01, 2015 at 02:59:46PM +1100, Sam P. wrote:
> > In sugar, some subsystems need to show an alert to the user
> > wherevever they are.  Right now, we have 2 systems; the max
> > activities limit and Quozl's force power off alerts.
>
> For readers who haven't seen this feature yet, think of it as a logout
> failure alert, caused by an activity not responding to session
> manager.
>
> It is rare enough that I'm fine with it disappearing if the user
> changes view.  They can change back to see it again.
>
> The maximum activities limit isn't generally used, so I'm not worried
> about it either.
>
> > Currently these are alerts that show in some places but not others.
> > They are not system wide alerts, so the user may not always see
> > them.   Plus there is too much code to make sure they are visible in
> > many places.  We also have a completely different implantation for
> > the full journal alert, which takes up the whole screen.
>
> Yes, this ModalAlert is different because the journal activity starts
> without explicit user action, and by the time it does this the focus
> may have moved away from the home view.
>
> It is the only alert that isn't triggered by the learner, and the
> problem of full journal really does stop the learner, so I'm fine
> with it being entirely different.
>
> > It is a mess IMO.
>
> Yes, but not a DESIGN issue, it's a code issue.  See below.
>
> > I think that if we come up with a ui for this, then we can hopefully
> > get rid of duplicated code!
>
> It is both the duplicated code and the inconsistent methods by which
> alerts are displayed.  Some view classes have inconsistent alert
> handling.
>
> But that isn't actually a learner problem.  It's a messy code problem.
>
> There are also alerts that do not need to be global;
>

Yeah I agree.  I don't think that we should change those alerts :)


>
> - journal, to confirm entry erase,
>
> - journal, to confirm batch operations, and report progress,
>
> - home view list, to confirm activity erase,
>
> - control panel accept, to restart,
>
> - school server registration,
>
> - journal, volume errors, caused by copying errors,
>
> - downgrading an activity,
>
> - view source, to confirm duplicating, and report progress,
>
> - view source, duplicating already duplicated activity,
>
> - activities, such as Chat join, and Browse downloads.
>
> > To get the conversation started, what about a simple idea.  Maybe we
> > could just have the alert (as in the long ones with buttons on the
> > end) pop up along the top of the screen and disable the frame.  We
> > could give it a red border of a massive shadow (like metacity loves)
> > or something.  This would block the user from accessing their
> > activity toolbar, which would probably make them look at it :)  See
> > [1]
>
> Thanks, but no, I dislike the idea.
>
> Here's what I think should be done;
>
> - generalise the ModalAlert; at the moment it is journal specific,
>
> - use the ModalAlert for the maximum activities limit; this will
>   fix your concern in opening paragraph,
>
> - extend the ModalAlert to include a timeout, as a TimeoutModalAlert,
>   in a similar fashion to how TimeoutAlert is implemented,
>
> - use the TimeoutModalALert for the logout failure message; this will
>   fix your concern in opening paragraph,
>
> - extend the maximum activities limit to show a list of activities and
>   let the learner close one,


Yes, that sounds like a great idea.


>
> - simplify the non-modal alert calls and UI object marshalling.
>

That seems kind of separate to me.  What do you mean?

Thanks,
Sam


>
> What do you think?
>
> --
> James Cameron
> http://quozl.linux.org.au/
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] System alerts ui in sugar

[Sam P.]

Hi All,

In sugar, some subsystems need to show an alert to the user wherevever they
are.  Right now, we have 2 systems; the max activities limit and Quozl's
force power off alerts.  Currently these are alerts that show in some
places but not others.  They are not system wide alerts, so the user may
not always see them.  Plus there is too much code to make sure they are
visible in many places.  We also have a completely different implantation
for the full journal alert, which takes up the whole screen.  It is a mess
IMO.

I think that if we come up with a ui for this, then we can hopefully get
rid of duplicated code!

To get the conversation started, what about a simple idea.  Maybe we could
just have the alert (as in the long ones with buttons on the end) pop up
along the top of the screen and disable the frame.  We could give it a red
border of a massive shadow (like metacity loves) or something.  This would
block the user from accessing their activity toolbar, which would probably
make them look at it :)  See [1]

Thanks,
Sam

[1]:  http://people.sugarlabs.org/sam/sys-alert-idea.png
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Issue setting up sugar-labs dev-env

[Sam P.]

org', 'python.org', 'pypi.python.org', 'docs.python.org', '
> testpypi.python.org', 'bugs.python.org', 'wiki.python.org', 'hg.python.org',
> 'mail.python.org', 'packaging.python.org', 'pythonhosted.org', '
> www.pythonhosted.org', 'test.pythonhosted.org', 'us.pycon.org', '
> id.python.org'
>   Will skip URL https://pypi.python.org/simple/plog/0.16 when looking for
> download links for plog==0.16 (from osbuild==0.33)
>   Getting page https://pypi.python.org/simple/plog/
>   Could not fetch URL https://pypi.python.org/simple/plog/: connection
> error: hostname 'proxy.iiit.ac.in' doesn't match either of 'www.python.org',
> 'python.org', 'pypi.python.org', 'docs.python.org', 'testpypi.python.org',
> 'bugs.python.org', 'wiki.python.org', 'hg.python.org', 'mail.python.org',
> 'packaging.python.org', 'pythonhosted.org', 'www.pythonhosted.org', '
> test.pythonhosted.org', 'us.pycon.org', 'id.python.org'
>   Will skip URL https://pypi.python.org/simple/plog/ when looking for
> download links for plog==0.16 (from osbuild==0.33)
>   Could not find any downloads that satisfy the requirement plog==0.16
> (from osbuild==0.33)
> Cleaning up...
>   Removing temporary dir
> /home/mayukuse/sugarlabs/sugar-build/build/out/sandbox-host/install/build...
> No distributions at all found for plog==0.16 (from osbuild==0.33)
> Exception information:
> Traceback (most recent call last):
>   File
> "/home/mayukuse/sugarlabs/sugar-build/build/out/sandbox-host/install/local/lib/python2.7/site-packages/pip/basecommand.py",
> line 122, in main
> status = self.run(options, args)
>   File
> "/home/mayukuse/sugarlabs/sugar-build/build/out/sandbox-host/install/local/lib/python2.7/site-packages/pip/commands/install.py",
> line 278, in run
> requirement_set.prepare_files(finder, force_root_egg_info=self.bundle,
> bundle=self.bundle)
>   File
> "/home/mayukuse/sugarlabs/sugar-build/build/out/sandbox-host/install/local/lib/python2.7/site-packages/pip/req.py",
> line 1177, in prepare_files
> url = finder.find_requirement(req_to_install, upgrade=self.upgrade)
>   File
> "/home/mayukuse/sugarlabs/sugar-build/build/out/sandbox-host/install/local/lib/python2.7/site-packages/pip/index.py",
> line 277, in find_requirement
> raise DistributionNotFound('No distributions at all found for %s' %
> req)
> DistributionNotFound: No distributions at all found for plog==0.16 (from
> osbuild==0.33)
>
> I am behind a proxy but the git and the pip proxy both are working.
>
>
>
>
> On Monday, 26 October 2015 3:22 PM, Tummala Dhanvi <dhanvi...@gmail.com>
> wrote:
>
>
>
>
> On Mon, Oct 26, 2015 at 2:37 AM, Sam P. <sam@sam.today> wrote:
>
> Hi,
> Are you running behind a proxy?
> What did the pip debug log say?
> Thanks,
> Sam
>
> On Sun, Oct 25, 2015, 9:24 PM vinay khandelwal <vinayp...@yahoo.co.in>
> wrote:
>
> I was trying to setup the developer environment following instructions
> from https://developer.sugarlabs.org/dev-environment.md.html . However
> when i do ./osbuild pull the following error comes up :-
>
> = Setup the host build system =
>
> * Create the python virtualenv
> * Install python packages
>   Cannot fetch index base URL https://pypi.python.org/simple/
>   Could not find any downloads that satisfy the requirement plog==0.16
> (from osbuild==0.33)
> No distributions at all found for plog==0.16 (from osbuild==0.33)
> Storing debug log for failure in /tmp/tmpsi4eBE
> Traceback (most recent call last):
>   File "./osbuild", line 488, in 
> if not main():
>   File "./osbuild", line 467, in main
> if not setup(options.command):
>   File "./osbuild", line 305, in setup
> raise e
> subprocess.CalledProcessError: Command
> '['/home/mayukuse/sugarlabs/sugar-build/build/out/sandbox-host/install/bin/pip',
> '-q', 'install', 'git+https://github.com/dnarvaez/osbuild', 'git+
> https://github.com/dnarvaez/broot']' returned non-zero exit status 1
>
> ​In my experience this doesn't work if you are under some proxy or if you
> are under restricted internet (firewall) or if you are under a WiFi which
> needs you to install their custom certificates.
>
>
> I am running this on UBUNTU 15.04 .
>
> ​Developers here use Fedora, but the process should work on any Linux
> distribution.
>
> Try doing it in a Fedora VM  it takes very less time to build even in a VM
> ​
>
> ​PS: Attach the pip debug log which will help the developers to identify a
> issue if it exists ​
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.o

Re: [Sugar-devel] Issue setting up sugar-labs dev-env

[Sam P.]

Hi,

Are you running behind a proxy?

What did the pip debug log say?

Thanks,
Sam

On Sun, Oct 25, 2015, 9:24 PM vinay khandelwal 
wrote:

> I was trying to setup the developer environment following instructions
> from https://developer.sugarlabs.org/dev-environment.md.html . However
> when i do ./osbuild pull the following error comes up :-
>
> = Setup the host build system =
>
> * Create the python virtualenv
> * Install python packages
>   Cannot fetch index base URL https://pypi.python.org/simple/
>   Could not find any downloads that satisfy the requirement plog==0.16
> (from osbuild==0.33)
> No distributions at all found for plog==0.16 (from osbuild==0.33)
> Storing debug log for failure in /tmp/tmpsi4eBE
> Traceback (most recent call last):
>   File "./osbuild", line 488, in 
> if not main():
>   File "./osbuild", line 467, in main
> if not setup(options.command):
>   File "./osbuild", line 305, in setup
> raise e
> subprocess.CalledProcessError: Command
> '['/home/mayukuse/sugarlabs/sugar-build/build/out/sandbox-host/install/bin/pip',
> '-q', 'install', 'git+https://github.com/dnarvaez/osbuild', 'git+
> https://github.com/dnarvaez/broot']' returned non-zero exit status 1
>
>
> I am running this on UBUNTU 15.04 .
> ___
> 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] Error while Setting up development environment

[Sam P.]

Hi Vinay,

What distribution are you running?

If you're running Fedora, you can use MODE NONE.  Try applying this patch:
https://github.com/sugarlabs/sugar-build/pull/31

Thanks,
Sam

On Fri, Oct 23, 2015 at 6:24 AM, vinay khandelwal 
wrote:

> I was following the instructions provided in
> https://developer.sugarlabs.org/dev-environment.md.html
>
> However at the step "./osbuild pull" the following error throws up :-
>
> = Setup the host build system =
>
> * Create the python virtualenv
> * Install python packages
> * Pull latest sugar-build
> * Setup the build root
>
> $ sudo broot setup
> Failed to download http://sugarlabs.org/~buildbot/broot/last-x86_64-master
> Traceback (most recent call last):
> File
> "/home/mayukuse/sugarlabs/sugar-build/build/out/sandbox-host/install/bin/broot",
> line 5, in 
> main.main()
> File
> "/home/mayukuse/sugarlabs/sugar-build/build/out/sandbox-host/install/local/lib/python2.7/site-packages/broot/main.py",
> line 80, in main
> if not cmd_function(options, other_args):
> File
> "/home/mayukuse/sugarlabs/sugar-build/build/out/sandbox-host/install/local/lib/python2.7/site-packages/broot/main.py",
> line 40, in cmd_setup
> return root.setup()
> File
> "/home/mayukuse/sugarlabs/sugar-build/build/out/sandbox-host/install/local/lib/python2.7/site-packages/broot/root.py",
> line 240, in setup
> if not self._download():
> File
> "/home/mayukuse/sugarlabs/sugar-build/build/out/sandbox-host/install/local/lib/python2.7/site-packages/broot/root.py",
> line 281, in _download
> last = urllib2.urlopen(last_url).read().strip()
> File "/usr/lib/python2.7/urllib2.py", line 154, in urlopen
> return opener.open(url, data, timeout)
> File "/usr/lib/python2.7/urllib2.py", line 437, in open
> response = meth(req, response)
> File "/usr/lib/python2.7/urllib2.py", line 550, in http_response
> 'http', request, response, code, msg, hdrs)
> File "/usr/lib/python2.7/urllib2.py", line 469, in error
> result = self._call_chain(*args)
> File "/usr/lib/python2.7/urllib2.py", line 409, in _call_chain
> result = func(*args)
> File "/usr/lib/python2.7/urllib2.py", line 656, in http_error_302
> return self.parent.open(new, timeout=req.timeout)
> File "/usr/lib/python2.7/urllib2.py", line 437, in open
> response = meth(req, response)
> File "/usr/lib/python2.7/urllib2.py", line 550, in http_response
> 'http', request, response, code, msg, hdrs)
> File "/usr/lib/python2.7/urllib2.py", line 475, in error
> return self._call_chain(*args)
> File "/usr/lib/python2.7/urllib2.py", line 409, in _call_chain
> result = func(*args)
> File "/usr/lib/python2.7/urllib2.py", line 558, in http_error_default
> raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
> urllib2.HTTPError: HTTP Error 404: Not Found
>
>
> Could someone help resolve this error?
> ___
> 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] Error while Setting up development environment

[Sam P.]

Oh, I found where those files where living.  I'm copying them across now.
It should be working again soon.

On Fri, Oct 23, 2015 at 7:53 AM, Sam P. <sam@sam.today> wrote:

> Hi Vinay,
>
> What distribution are you running?
>
> If you're running Fedora, you can use MODE NONE.  Try applying this patch:
>  https://github.com/sugarlabs/sugar-build/pull/31
>
> Thanks,
> Sam
>
> On Fri, Oct 23, 2015 at 6:24 AM, vinay khandelwal <vinayp...@yahoo.co.in>
> wrote:
>
>> I was following the instructions provided in
>> https://developer.sugarlabs.org/dev-environment.md.html
>>
>> However at the step "./osbuild pull" the following error throws up :-
>>
>> = Setup the host build system =
>>
>> * Create the python virtualenv
>> * Install python packages
>> * Pull latest sugar-build
>> * Setup the build root
>>
>> $ sudo broot setup
>> Failed to download
>> http://sugarlabs.org/~buildbot/broot/last-x86_64-master
>> Traceback (most recent call last):
>> File
>> "/home/mayukuse/sugarlabs/sugar-build/build/out/sandbox-host/install/bin/broot",
>> line 5, in 
>> main.main()
>> File
>> "/home/mayukuse/sugarlabs/sugar-build/build/out/sandbox-host/install/local/lib/python2.7/site-packages/broot/main.py",
>> line 80, in main
>> if not cmd_function(options, other_args):
>> File
>> "/home/mayukuse/sugarlabs/sugar-build/build/out/sandbox-host/install/local/lib/python2.7/site-packages/broot/main.py",
>> line 40, in cmd_setup
>> return root.setup()
>> File
>> "/home/mayukuse/sugarlabs/sugar-build/build/out/sandbox-host/install/local/lib/python2.7/site-packages/broot/root.py",
>> line 240, in setup
>> if not self._download():
>> File
>> "/home/mayukuse/sugarlabs/sugar-build/build/out/sandbox-host/install/local/lib/python2.7/site-packages/broot/root.py",
>> line 281, in _download
>> last = urllib2.urlopen(last_url).read().strip()
>> File "/usr/lib/python2.7/urllib2.py", line 154, in urlopen
>> return opener.open(url, data, timeout)
>> File "/usr/lib/python2.7/urllib2.py", line 437, in open
>> response = meth(req, response)
>> File "/usr/lib/python2.7/urllib2.py", line 550, in http_response
>> 'http', request, response, code, msg, hdrs)
>> File "/usr/lib/python2.7/urllib2.py", line 469, in error
>> result = self._call_chain(*args)
>> File "/usr/lib/python2.7/urllib2.py", line 409, in _call_chain
>> result = func(*args)
>> File "/usr/lib/python2.7/urllib2.py", line 656, in http_error_302
>> return self.parent.open(new, timeout=req.timeout)
>> File "/usr/lib/python2.7/urllib2.py", line 437, in open
>> response = meth(req, response)
>> File "/usr/lib/python2.7/urllib2.py", line 550, in http_response
>> 'http', request, response, code, msg, hdrs)
>> File "/usr/lib/python2.7/urllib2.py", line 475, in error
>> return self._call_chain(*args)
>> File "/usr/lib/python2.7/urllib2.py", line 409, in _call_chain
>> result = func(*args)
>> File "/usr/lib/python2.7/urllib2.py", line 558, in http_error_default
>> raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
>> urllib2.HTTPError: HTTP Error 404: Not Found
>>
>>
>> Could someone help resolve this error?
>> ___
>> 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] Add more components to bugs.sl.org

[Sam P.]

Hi Ignacio,


I think that BSLO isn't just for developers - users need to write reports
and users shouldn't need to understand the barriers between the components.

What is the use case for them anyway?

Thanks,
Sam


On Sun, 11 Oct 2015 1:00 pm Ignacio Rodríguez  wrote:

Can some admin add components like
"sugar-artwork", "sugar-toolkit", "sugar-toolkit-gtk3".
There is "design" but for developers it's not the same as

sugar-artwork


--
Ignacio Rodríguez
SugarLabs at Facebook

___
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] [DESIGN] Super key as frame key

[Sam P.]

Hi All,

Sugar makes no use of the super key for any short cuts.  This makes sense
in the context of the XO, because of the lack of the key.  However, on
normal computers with SoaS, the super key is often in a more convenient
spot than the function keys, epically on computers than require the Fn
modifier.

In my opinion, the frame is a very important short cut in sugar.  Pressing
the super key would be eaiser than F6, or moving the mouse sometimes.
Maybe the super key could trigger the frame.  This would be similar to
GNOME, where the super key opens the overview.

Should the super key be mapped to the frame or something else?

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

[Sugar-devel] How bad is Sugar (software)?

[Sam P.]

Hi All,

I'm running an annon. survey about Sugar, and I am interested in hearing
everyone's perspective.

It will only take a minute or so to complete.

"How bad is Sugar (software)?"
https://docs.google.com/forms/d/1MFs8qXpMP2udjuPdFa13DamkijNk_3_KwrtTgshD1Bg/viewform

I will use your responses to help improve Sugar.  I also plan to share an
analysis of the responses with the community.

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

Re: [Sugar-devel] [SoaS] SOAS

[Sam P.]

Yeah, collaboration is broken in newer (20+? IDK) fedora versions.  That is
because of telepathy api changes.  We will attempt to fix this in the
coming release (0.108/1.0?).  That seems to the the consensus about the
coming release.

Thanks,
Sam

On Tue, 8 Sep 2015 7:04 pm Peter Robinson  wrote:

> Hi David,
>
> Sorry, this seem to have fallen through the cracks.
>
> > Iain referred me to a Fedora community where LinuxliveUSB installer was
> recommended and it works just fine. It also installs a Linux emulator for
> Windows Virtualbox and I found I could run SOAS beautifully in that way.
> That is very convenient for my purposes (a quick lead in to Sugar). I also
> found few problems booting USB sticks and SD cards installed using
> LinuxLiveUSB, on one machine it seems to hang but others it is fine. So it
> seems the installer was my issue.
>
> I've never seen or heard of the above, I've also never used
> VirtualBox, glad it works for you.
>
> > Regarding collaboration, if we have a few PC computers on the same WLAN
> running SOAS, can we expect them to see each other and collaborate in
> neighbourhood view, without a server (ie. in the same fashion as XOs on an
> ad-hoc network)? I seem to recall doing that with early versions of SOAS.
> If not, is there a simple/light way to enable collaboration/presence
> service on a local server sufficient to allow a few local SOAS machines to
> collaborate?. I am familiar with XS developments (up to 0.7) but in the
> schools in Vanuatu we'll be using gateway servers we have developed
> ourselves based on Debian (Jessie 8).
>
> I believe there's an issue with recent versions on collaboration, I
> don't remember the exact issues, maybe one of the sugar devs can
> answer the reasons and when it's expected it can be fixed.
>
> Peter
>
> > Best,
> >
> > David Leeming
> > Solomon Islands
> >
> > -Original Message-
> > From: sugar-devel-boun...@lists.sugarlabs.org [mailto:
> sugar-devel-boun...@lists.sugarlabs.org] On Behalf Of Peter Robinson
> > Sent: Wednesday, 22 July 2015 10:58 a.m.
> > To: Development of live Sugar distributions
> > Cc: Sugar-dev Devel; Iain Brown Douglas
> > Subject: Re: [Sugar-devel] [SoaS] SOAS
> >
> > Hi David,
> >
> > I'm the SoaS maintainer.
> >
> >> I want to demonstrate SOAS to teachers in Vanuatu. I would like to be
> more useful, but actually don't have the luxury of time to research these
> arcane technical issues in which I am not an expert. I just want to know,
> is there a version of SOAS that is properly tested and known to work? I
> have used SOAS many times before (years ago) without any problems. Which
> version is stable and will boot without errors and not hang on use?
> >
> > The lastest stable version is available here:
> > https://spins.fedoraproject.org/en/soas/
> >
> >> Could be hardware? I will try with another flashdrive. Is 2GB of
> persistent storage too little/too much?
> >
> > 2Gb should be fine.
> >
> > Ask here on the SoaS list if you've got any other queries or issues.
> >
> > Peter
> >
> >> David Leeming
> >> Solomon Islands
> >>
> >>
> >> -Original Message-
> >> From: sugar-devel-boun...@lists.sugarlabs.org [mailto:
> sugar-devel-boun...@lists.sugarlabs.org] On Behalf Of Iain Brown Douglas
> >> Sent: Tuesday, 21 July 2015 7:52 p.m.
> >> To: David Leeming
> >> Cc: 'Sugar-dev Devel'
> >> Subject: Re: [Sugar-devel] SOAS
> >>
> >> Hi David,
> >>
> >> From what you say, you already did a search for your error message.
> >>
> >> Does this Fedora forum answer cover your issue?
> >> http://forums.fedoraforum.org/showthread.php?t=301945
> >>
> >> I have been working with the script livecd-iso-to-disk and it works
> >> fine.
> >>
> >> I am working on SoaS Loader, here is a link to the work in progress.
> >>
> >> http://soas-loader.readthedocs.org/
> >>
> >> Good luck, and thanks for putting time in trying to demonstrate SoaS :)
> >>
> >> Iain
> >>
> >>
> >>
> >>
> >> On Tue, 2015-07-21 at 10:51 +1100, David Leeming wrote:
> >>> Hello,
> >>>
> >>>
> >>>
> >>> I have familiarity with Sugar since working with OLPC from 2008, but I
> >>> haven’t been active in these communities for some time. I’m just
> >>> refreshing myself on current status of Sugar with a view to
> >>> introducing teachers to it in a forthcoming workshop in Vanuatu. We’ll
> >>> be using tablets as well as PCs so I have familiarised myself with
> >>> Sugarizer. I then intended to introduce the wider world of Sugar
> >>> conveniently with SOAS.
> >>>
> >>>
> >>>
> >>> So I have downloaded both the 32-bit and 64-bit iso files and verified
> >>> their hashes. I also download the latest version of USB Live
> >>> Installer. I formatted a fairly new 16GB USB with FAT32 and installed
> >>> SOAS on it leaving 2000Mb of persistent memory. The USB stick is a
> >>> “SanDisk Cruzer Facet 16GB”.
> >>>
> >>>
> >>>
> >>> Immediately I run into problems. When booting (on a fairly recent
> >>> Toshiba i7 laptop) it stops with 

Re: [Sugar-devel] Bug 1240354 - SoaS live x86_64 20150706 does not login from live system user

[Sam P.]

Hi James,

On Fri, Sep 4, 2015 at 8:44 AM James Cameron  wrote:

> @All, what is main.py and where are lines 1818 and 2637?
>
> src/jarabe/main.py is much smaller, only 425 lines.
>

That is the only main.py there is :)  Maybe it is an issue with gir?  It
isn't something that seems out of the ordinary anyway.


>
> Some other diagnosis methods to suggest:
>

I am running fedora rawhide (24).  I reinstalled the packages (dnf
reinstall sugar sugar-toolkit-gtk3) and they were reinstalled.  Rawhide
uses the fc23 packages for sugar, so hopefully this is relevant.

Sugar-runner gives the logs:

   ...
   ** (main.py:9674): WARNING **: Failed to load shared library
'libsugarext.so.0' referenced by the typelib: /lib64/libsugarext.so.0:
undefined symbol: sugar_event_controller_get_state
   ...
   GLib.Error: g-invoke-error-quark: Could not locate acme_volume_alsa_new:
'acme_volume_alsa_new': /lib64/libsugar-eventcontroller.so.0: undefined
symbol: acme_volume_alsa_new (1)

Interestingly it is trying to import the volume function from
sugar-eventcontroller.  It is actually in libsugarext.  Maybe that is
related to our issue?


> a.  in a fresh python process, try the relevant imports, e.g.
>
> from jarabe.view import gesturehandler
> from jarabe.model.sound import sound
>

The 1st imports fine.  However, attempting to create a GestureHandler
(hence invoking the functions in the library) cause an exception:
http://fpaste.org/263565/44136633/

The 2nd fails on import with:

g-invoke-error-quark: Could not locate acme_volume_alsa_new:
'acme_volume_alsa_new': /lib64/libsugar-eventcontroller.so.0: undefined
symbol: acme_volume_alsa_new (1)


>
> b.  verify a symlink is present from /usr/lib/libsugarext.so.0 to
> libsugarext.so.0.0.0 (or equivalent functionality, as this is a
> guess from my experience with F18),
>

Yes, it is there.


>
> c.  use strings to check libsugarext.so.0, see if
> sugar_event_controller_get_state is present,
>
> strings /usr/lib/libsugarext.so.0 | \
> grep sugar_event_controller_get_state
>

Yes, that works cool.  The volume function is also in the libsugarext as
expected.

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

Re: [Sugar-devel] Bug 1240354 - SoaS live x86_64 20150706 does not login from live system user

[Sam P.]

Hi James,

On Thu, 3 Sep 2015 4:34 pm James Cameron  wrote:

On Thu, Sep 03, 2015 at 01:21:19AM -0500, Jerry Vonau wrote:
>
>
> > On September 3, 2015 at 12:38 AM James Cameron  wrote:
> >
> >
> > On Thu, Sep 03, 2015 at 12:11:38AM -0500, Jerry Vonau wrote:
> > > F22 upgrades clean to 106, feels pretty zippy in a VM. Back to
> > > figuring out what is now different in the dependencies given the
> > > logs[1] for the builds look more or less the same F21 <-> F23. There
> > > has to be a rpm package with a library that was split somewhere,
> > > sugar's toolkit wants to use something but is left unsatisfied.
> >
> > It might be interesting to see if the F23 build of 0.104.1 also has
> > the problem on F23.  As further proof that it isn't anything Sugar did.
> >
> I can get to a cmdline via the bootprompt using the F23 iso, so I'll do
the
> 104 on F23 test, just not tonight.
>
> It's not what sugar did, but didn't do yet, adapt to the new build
> environment for F23. Is the current recommended sugar development
> still sugar-build at EOL'd F20?

Good question.  Don't know.  Hopefully someone from Sugar Labs can
tell us.

I'm pretty sure it is.  But most of the maintainers disable broot and just
run in natively in Fedora.

Although sugar-build hides all these kinds of problems by building on
the target system instead of packaging.

sugar-build is not used when deploying, so it seems unwise to use it
for development.  ;-)

Works fine if you disable broot.  Maybe we should change defaults (no broot
for Fedora ever).

Otherwise there is really nothing wrong with a bunch of build scripts and
package install scripts IMHO :)

Thanks,
Sam

> > Comparing the logs of 0.104.1 build for x86_64 between F22 and F23,
> > the only interesting change that springs up is;
> >
> > -LDFLAGS='-Wl,-z,relro '
> > +LDFLAGS='-Wl,-z,relro -specs=/usr/lib/rpm/redhat/redhat-hardened-ld'
> >
> > Doesn't seem related to the reported problem, however.
>
> I tend to agree, but I'm not sure of the full effect of the flag. I
> think there is a package that was split and a dependence needed by
> sugar/toolkit moved to a new sub-package and is not in what is
> declared as (Build)Requires anymore. If this is true then the new
> sub-package should now be used in the spec file somewhere, just
> finding the package.

Hmm, doesn't seem related to the sugarext library missing from the
expected directory.  Maybe I've misunderstood the problem.

--
James Cameron
http://quozl.linux.org.au/
___
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] Bug 1240354 - SoaS live x86_64 20150706 does not login from live system user

[Sam P.]

No, that is exactly the same issue.  If you open the log attached <
https://bugzilla.redhat.com/attachment.cgi?id=1048658> you'll see
"GLib.Error: g-invoke-error-quark: Could not locate acme_volume_alsa_new:
'acme_volume_alsa_new': /lib64/libsugar-eventcontroller.so.0: undefined
symbol: acme_volume_alsa_new (1)"

As noted on , this bug
is very weird because it works 100% if you copy the libs compiled by
sugar-build.

On Wed, 2 Sep 2015 1:04 am Jerry Vonau  wrote:

>
>
> > On September 1, 2015 at 9:05 AM Peter Robinson 
> > wrote:
> >
> >
> > On Tue, Sep 1, 2015 at 2:54 PM, Gonzalo Odiard 
> wrote:
> > > GLib.Error: g-invoke-error-quark: Could not locate
> > > acme_volume_alsa_new:
> > > 'acme_volume_alsa_new': /lib/libsugar-eventcontroller.so.0: undefined
> > > symbol: acme_volume_alsa_new (1)
> > >
>
> Look above that I noted:
>
> "Failed to load shared library 'libsugarext.so.0' referenced by the
> typelib: /lib/libsugarext.so.0: undefined"
>
> Is that not the same issue Peter noted in comment 2 of:
> https://bugzilla.redhat.com/show_bug.cgi?id=1240147
>
> Jerry
> ___
> 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] Spell checker, Grammar checker for Write

[Sam P.]

Hi Lionel,

I think it is an abiword config thing.  On my Fedora laptop, both abiword
and Write Activity have a spell checker.  I don't think you need a plugin.

Thanks,
Sam

On Sun, Aug 30, 2015 at 5:44 PM Lionel Laské lio...@olpc-france.org wrote:

 Hi all,

 An OLPC France teacher working on our small XO-4 deployment asked me if
 it's possible to enhance Write activity with a spell checker, grammar
 checker or a dictionary (all in French).

 I reminded me that Write activity is based on AbiWord and it seems that
 AbiWord allow some sort of plug-ins.

 Do you know if it's possible to enhance Write with AbiWord plugins ?
 Is there someone that experience this sort of thing ?

 Tell me.

 Best regards from France.

Lionel.
 ___
 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-install-bundle in 13.2.5 is slooow

[Sam P.]

Hi Tony,

Do you have the logs of these installs?  Is there anything in the logs?

Looking back at the commit logs, the change in 0.104 was to use the bundle
registry to install bundles if sugar is running [1].  Maybe that has done
something or maybe it is a different change down the line!

Thanks,
Sam

[1]
https://github.com/sugarlabs/sugar/commit/64b4b2fba1c37a9ad92ed30eb669b68552b62415

On Sat, Aug 29, 2015 at 8:13 PM Tony Anderson tony_ander...@usa.net wrote:

 I use sugar-install-bundle to update the configuration of Sugar
 activities when preparing laptops at deployments. With 13.2.5, this
 script is taking 3-4 times as long
 as with previous releases.

 I can only speculate on the difference in times since I have 13.2.5 on
 all the available XOs and apparently can't flash back.

 Specifically,

 Browse (some custom modifications)  Test 1: 23 minutes 34 seconds Test
 2: 5 minutes 21 seconds
 Jukebox (v26 - need gstream 0.1) Test 1: 19 minutes 26 seconds Test 2: 7
 minutes 39 seconds
 Quiz  Test 1 6 minutes 52 seconds Test 2 3 minutes 18 seconds

 My recollection is that the install on 13.2.1 took less than 10 minutes
 overall (including a number of other installs such as codecs, flash,
 libre office, gcompris ) with
 installation of these three activities taking from 2-3 minutes total.

 Tony
 ___
 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-install-bundle in 13.2.5 is slooow

[Sam P.]

Hi Tony,

Should we make disabling install via bundle registry (SUGAR_PROFILE) a flag?

There are use cases when it makes sense to install via bundle registry
(updating the activity list) so it is not good to outright disable it.

Thanks,
Sam

On Sat, 29 Aug 2015 11:51 pm Tony Anderson tony_ander...@usa.net wrote:

 Hi,

 I reran the installs with SUGAR_PROFILE set to False. The install timings:

 Browse: 0.5 seconds
 Jukebox: 0.5 seconds
 Quiz: 0.8 seconds

 I'll just patch sugar-install-bundle not to use the SUGAR_PROFILE path.

 Thanks for the help.

 Tony

 On 08/29/2015 01:41 PM, James Cameron wrote:
  G'day Sam,
 
  My guess is #4849 again and our user hasn't unset the SUGAR_PROFILE
  environment variable as was suggested four months ago.  I never heard
  closure on the suggestion, but as it was off-list I'm not surprised.
  The ticket shows how to reproduce in case you'd like to take a stab at
  it.
 

 ___
 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] [ASLO] Release Flappy Birds-1

[Sam P.]

Quoting Quozl:

Installed on Sugar 0.104 on an OLPC XO-4.  Tested.  Works well.  There
are a few things that I'd want to fix before I added it to a
deployment build:

a.  the activity icon is coloured, it should be in the style of other
activity icons instead, so that the Sugar user colours can be applied,

b.  the game does not scale to the size of the screen, see attached
screenshot,

c.  the animation seems a bit slow, it could be 50% faster,

d.  the scissors could open and close a bit faster,

e.  the touchscreen doesn't work for selecting a scissor cut,

f.  slipping with a cut, such that the cursor is on the home icon when
the mouse is released, caused the home icon to trigger; the home icon
should only trigger if both a mouse button down _and_ mouse button up
event are seen within the icon borders.

g.  resuming the activity from the Journal did not resume the same
game state.

 Download Now:

http://activities.sugarlabs.org/downloads/file/29076/buttons_and_scissors-1.xo

Is this in git anywhere?

The source code is set out in a wide screen editor; it would be easier
to read if it was laid out for 80 columns.

The source code would benefit from pep8 and re-indentation, and
removal of blank lines.

There's a file in fonts/ ... is the license for this font compatible
with the license for the activity?

==

You then replied

Yes, the game needs more work, but for first version, it's good.

The git repo is: https
https://github.com/iamutkarshtiwari/Buttons-and-Scissors://
https://github.com/iamutkarshtiwari/Buttons-and-Scissorsgithub.com
https://github.com/iamutkarshtiwari/Buttons-and-Scissors/
https://github.com/iamutkarshtiwari/Buttons-and-Scissorsiamutkarshtiwari
https://github.com/iamutkarshtiwari/Buttons-and-Scissors/
https://github.com/iamutkarshtiwari/Buttons-and-ScissorsButtons-
https://github.com/iamutkarshtiwari/Buttons-and-Scissorsand-Scissors
https://github.com/iamutkarshtiwari/Buttons-and-Scissors

==

To me, that does come across as dismissive - which seems to have been why
Quozl hasn't given comments on flappy birds.

Thanks,
Sam


On Sat, 29 Aug 2015 1:36 pm Alan Jhonn Aguiar Schwyn alan...@hotmail.com
wrote:

 Wich problems do you have with Buttons and Scissors?

  Date: Sat, 29 Aug 2015 08:47:49 +1000
  From: qu...@laptop.org
  To: sugar-devel@lists.sugarlabs.org
  Subject: Re: [Sugar-devel] [ASLO] Release Flappy Birds-1

 
  Reviewed code and tested on XO-4 with Sugar 0.104.1, but as there was
  no response from the developer to my previous post on Buttons and
  Scissors, I don't think it is worth making any observations here.
 
  --
  James Cameron
  http://quozl.linux.org.au/
  ___
  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] Speech synthesizer in sugar web

[Sam P.]

Hello Yander,

Sugar uses webkit to run web activities.  On sugar-build it is via WebKit2
(same as GNOME Web/Ephipany, Apple Safari) and WebKit(1) on XO.  Neither of
these platforms support the speech api, infact neither of them support many
of the flashy new stuff :)

Sugar however has tts built in powered by espeak.  Users can highlight
speech and use a button in the frame to play it back.

Maybe you should look into exposing the tts functions provided by sugar3 to
web activities?  Then you could make an abstraction between the 2 backends.

Of course, you could look into using [FireFox, CEF, Servo] to run sugar web
activities, but that is another thing all together!

Thanks,
Sam

On Sat, Aug 15, 2015 at 10:55 AM Yader Velásquez yajo...@gmail.com wrote:

 Hi everyone, I'm not sure if this is the right place for this kind of
 questions, please let me know where I can ask for support about activity
 development.

 I'm working on an activity based on sugar web, I have to read some text
 from the screen and synthesize them. A quick glance in the web took me to
 the Web Speech API[1], but unfortunately it doesn't work within sugar
 osbuild.

 There are some third party libraries in the web, but I'm not sure what
 would be the best solution. The only requirements are to be supported by
 sugar web and to have spanish support. What do you suggest?

 Thank you.


 1.
 https://developers.google.com/web/updates/2014/01/Web-apps-that-talk---Introduction-to-the-Speech-Synthesis-API?hl=en

 --
 Yader.
 http://yaderv.wordpress.com

 ___
 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] Language Support

[Sam P.]

Hey Tony,

On Wed, Aug 12, 2015 at 9:51 PM Tony Anderson tony_ander...@usa.net wrote:

 Hi, Sam

 My concern is not the execution of the panel, but how we explain it to
 users. Remember our target audience is teachers and students in primary
 school in the
 developing world with little or no prior computer experience. As
 developers, we often see things as simple because we have used many others
 like it. It may not
 be so simple to those who do not have that experience.


Yep.  But we don't have a selector in the intro, so they'd be pretty
amazing to find the language settings if it wasn't configured by their
deployment :)



 However, we probably should think about the dialect/region selection. If I
 have selected Arabic, perhaps the dialect/region list should be in Arabic.


Ticket:  https://bugs.sugarlabs.org/ticket/4449



 We may also want to think about that list - do the entries represent
 countries where the language is spoken or represent dialects? I suspect the
 lists were
 copied from earlier releases.


They're just the system languages, so that is an issue for the distribution.




 Tony


 On 08/12/2015 01:38 PM, Sam P. wrote:

 Hi Tony,

 The control panel is very simple.  The left column is the language and the
 right column is the region/dialect.

 Maybe that should be a column header?

 Also, there is no conflicting + and add buttons.  The dropdown for the
 language selectors in a up or down arrow, while the add a new language
 button is a +.  The hitbox for the expand/contract the dropdown includes
 the button and the label, making it more discoverable.

 Maybe it should use palettes (or modals with search!) to be more
 consistent, but it is actually a very nice ui considering it does a very
 complex job.

 I opened the control panel on the same OLPC OS image that you are running,
 can can not reproduce many (any?) of the issues you're describing.

 Please consider opening separate tickets for the issues.

 Thanks,
 Sam

 On Wed, Aug 12, 2015 at 9:26 PM Tony Anderson tony_ander...@usa.net
 wrote:

 Hi,

 To continue the story. The way it works, you click on the button to the
 left of the language (English) to
 get a list. You click on the language to get a dialect (or region?). You
 click on the dialect to select it. You then click on the
 + button to get it 'really' selected. You then click on the top right
 button to restart as always.

 After restarting the added language (German) is the system language.
 However, when going back to the
 language selection in settings, German is the only language shown. So
 you need to click to open the language
 list, click on English. This opens up the options of Australien and USA.
 Incidentally, that is now the only line, the German
 option has disappeared.

 I tried Arabic. There are 12 regions or dialects available. That list is
 in English. I selected Egypt and was able to
 switch to Arabic. To switch back, I clicked on the button to the left of
 Arabic (only line). It lists alternate languages
 in a mixture of Arabic and Latin alphabets. English is evidently shown
 in Arabic but Spanish is Spanish. I selected
 Spanish getting 21 regional choices all in Arabic except USA. I selected
 USA and switched the system to Spanish.

 I then went back to settings and got a list of languages in Spanish
 (Inglés). I selected that option and got a choice
 of Australia and USA. I was able to get back to the original English,
 USA option.

 Tony


 On 08/12/2015 12:55 PM, Tony Anderson wrote:
  I was surprised and embarrassed yesterday trying to show how easy it
  is to switch
  languages. I was using a 13.2.5 image.
 
  In previous versions, you go to settings and language and get a long
  list of supported
  languages. In 13.2.5, you get a statement: 'Add languages in the order
  you prefer'.
  So I clicked on + to add German. It added another row: English USA + -
 
  In the press of the moment, I couldn't find any other language that
  English USA.
 
  However, today I found that the trick is to click on the button to the
  left of the word English. This
  opens the expected list. Click on German adds a line with dialects:
  Austria, Belgium, Germany, ...
 
  Unfortunately, the use of the word 'add' together with a '+' button at
  least in my case led to confusion.
 
  Tony
  ___
  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] Language Support

[Sam P.]

Hi Tony,

The control panel is very simple.  The left column is the language and the
right column is the region/dialect.

Maybe that should be a column header?

Also, there is no conflicting + and add buttons.  The dropdown for the
language selectors in a up or down arrow, while the add a new language
button is a +.  The hitbox for the expand/contract the dropdown includes
the button and the label, making it more discoverable.

Maybe it should use palettes (or modals with search!) to be more
consistent, but it is actually a very nice ui considering it does a very
complex job.

I opened the control panel on the same OLPC OS image that you are running,
can can not reproduce many (any?) of the issues you're describing.

Please consider opening separate tickets for the issues.

Thanks,
Sam

On Wed, Aug 12, 2015 at 9:26 PM Tony Anderson tony_ander...@usa.net wrote:

 Hi,

 To continue the story. The way it works, you click on the button to the
 left of the language (English) to
 get a list. You click on the language to get a dialect (or region?). You
 click on the dialect to select it. You then click on the
 + button to get it 'really' selected. You then click on the top right
 button to restart as always.

 After restarting the added language (German) is the system language.
 However, when going back to the
 language selection in settings, German is the only language shown. So
 you need to click to open the language
 list, click on English. This opens up the options of Australien and USA.
 Incidentally, that is now the only line, the German
 option has disappeared.

 I tried Arabic. There are 12 regions or dialects available. That list is
 in English. I selected Egypt and was able to
 switch to Arabic. To switch back, I clicked on the button to the left of
 Arabic (only line). It lists alternate languages
 in a mixture of Arabic and Latin alphabets. English is evidently shown
 in Arabic but Spanish is Spanish. I selected
 Spanish getting 21 regional choices all in Arabic except USA. I selected
 USA and switched the system to Spanish.

 I then went back to settings and got a list of languages in Spanish
 (Inglés). I selected that option and got a choice
 of Australia and USA. I was able to get back to the original English,
 USA option.

 Tony


 On 08/12/2015 12:55 PM, Tony Anderson wrote:
  I was surprised and embarrassed yesterday trying to show how easy it
  is to switch
  languages. I was using a 13.2.5 image.
 
  In previous versions, you go to settings and language and get a long
  list of supported
  languages. In 13.2.5, you get a statement: 'Add languages in the order
  you prefer'.
  So I clicked on + to add German. It added another row: English USA + -
 
  In the press of the moment, I couldn't find any other language that
  English USA.
 
  However, today I found that the trick is to click on the button to the
  left of the word English. This
  opens the expected list. Click on German adds a line with dialects:
  Austria, Belgium, Germany, ...
 
  Unfortunately, the use of the word 'add' together with a '+' button at
  least in my case led to confusion.
 
  Tony
  ___
  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] [DESIGN] Background selection in Journal

[Sam P.]

Hi Ignacio,

On Thu, 6 Aug 2015 7:46 am Ignacio Rodríguez igna...@sugarlabs.org wrote:

Hi everyone.

Finally I got time for start to work on the features/patches that I
submitted time ago. (Too much time in school, but well, worth it :) )
In this case I would like to discuss the selection of background in Journal
[1] patch (maybe it’s a Feature)

Does this have a feature page?

The base idea is to add a option to the Copy to journal volume menu, for
make it more easy for new users..

Also move code for background settings to jarabe.model, so the apps would
be able to change the background (Not really needed in apps, but yes in
this patch)

Here [2] is a screenshot of how it

looks

Looks good.

XFCE have a option for set as wallpaper [3]

I don't remember if gnome have one too

Right now it copy the image to “/home/user/Documents” for be able to see it
in Control Panel, but Sam suggested to copy it to somewhere in
“/home/user/.sugar” folder.

I like that idea, I think we can copy it to .sugar/background.[jpg/png]
(Also we can copy the  selected one in controlpanel for avoid problems if
the user remove it in Journal - maybe another patch)

Maybe we could copy it to .sugar/user-backgrounds folder?  Then we could
just add that in the search path in the cpanel and not do to many fancy
things?   Maybe that is less code.

Thanks,
Sam

Comments are gratefully received.

[1] https://github.com/sugarlabs/sugar/pull/466
[2] http://people.sugarlabs.org/ignacio/Set%20as%20wallpaper-Sugar.png
[3] http://people.sugarlabs.org/ignacio/Set%20as%20wallpaper-XFCE.png

Greetings,

Ignacio Rodríguez

SugarLabs at Facebook
https://www.facebook.com/pages/SugarLabs/187845102582

___
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] [Systems] Error on trac reading a bug #4863

[Sam P.]

Hi All,

Sorry about my naivety with the memory limits.  I now see how this is an
issue :)

I'll look into resource monitoring and alerting systems for docker.

The HN article was pretty interesting.  In some respects, many of those
issues are not applicable to us (we use simple images and don't need
secrets at build time).  The article does point out some interesting
avenues (OverlayFS) and highlights the momentum of the docker world.  The
comments were very negative about docker (particularly for HN), but docker
does provide us value in being containerization to un-tangle our services
and the Dockerfile buid system.

Thanks,
Sam

On Wed, 29 Jul 2015 4:10 pm Bernie Innocenti ber...@codewiz.org wrote:

 By the way, found this relevant article today on Hacker News:

http://sirupsen.com/production-docker/

 The comments are also interesting:

https://news.ycombinator.com/item?id=9961537


 On 28/07/15 19:48, Bernie Innocenti wrote:
  On 07/28/2015 09:27 AM, Samuel Cantero wrote:
  Hi All,
 
  On Tue, Jul 28, 2015 at 6:52 AM, Sam P. sam@sam.today
  mailto:sam@sam.today wrote:
 
   Hi Bernie,
 
   On Tue, Jul 28, 2015 at 2:12 PM Bernie Innocenti 
 ber...@codewiz.org
   mailto:ber...@codewiz.org wrote:
 
   1. We need monitoring for containers health with notifications
 when
   parameters go off thresholds. Similar to what Munin does.
 
 
   I'm not sure how that would help us.  A container running out of
   resources doesn't crash - parsoid runs almost using all the
   allocated memory and parsoid+trac+others hit their cpu quotas
   sometimes and just keep running.
 
 
  A container running out of memory dies. By default, the memory limit
  value for the container is set to twice as much as the memory parameter
  we specify while starting a container. The limit value is the sum of
  memory and swap.
 
  We do not have swap accounting enabled yet on freedom, but for sure we
  are going to have it at the next reboot.
 
  In the best Google tradition, freedom doesn't have any swap space at all
 :-)
 
 
  You can test it with the stress image (as we did before for the CPU):
 
  sudo docker run --rm -m 128m --name testmem scg/stress --vm 1 --vm-bytes
  256M
 
  If you allocate over twice the amount of memory we assign you will get
  the following error:
 
  stress: info: [1] dispatching hogs: 0 cpu, 0 io, 1 vm, 0 hdd
  stress: FAIL: [1] (415) -- worker 7 got signal 9
  stress: WARN: [1] (417) now reaping child worker processes
  stress: FAIL: [1] (421) kill error: No such process
  stress: FAIL: [1] (451) failed run completed in 3s
 
  By default, Docker kills processes in a container if an out-of-memory
  (OOM) error occurs. We can change this behaviour on a container but we
  are not doing it now.
 
  See my response to Sam P.: killing the entire container is almost always
  the right response to an OOM.
 
 
   Maybe it would be more useful to monitor client metrics, like can
 we
   reach the service over http?
 
  I guess It would be useful. We can do it with nagios.
 
  Cool, does it support Docker? I used Nagios a long time ago at the FSF
  and it was pretty good. The reason I was using munin at SL is that it
  was easier to setup and I didn't know Nagios back then. Moreover, Munin
  seems a bit of a dead project nowadays, so I'd be happy to switch.
 
  Can we run the Nagios frontend in a container too?
 
 
   That is a feature built into docker.  I've enabled it in
   container.yml (as a global default) and restarted trac with the new
   parameters.
 
  Great. Maybe we need to enable historical resource usage in cadvisor.
  This would help us to understand if a container has crashed because it
  has run out of resources.
 
  Cool, another useful feature I didn't know about. Yes, please, let's
  enable resource graphing. Is there an http frontend to look at the
 numbers?
 
 
   Thanks,
   Sam
 
 
 
   3. Since high-profile services have been deployed using Docker
 for a
   while, software for doing (1) and (2) certainly exists already
 :-)
 
 
   On 27/07/15 22:32, Samuel Cantero wrote:
I didn't shut it down. The trac container was already off
 when
   I checked
it.
   
On Mon, Jul 27, 2015 at 9:40 PM, Sam P. sam@sam.today
mailto:sam@sam.today mailto:sam@sam.today wrote:
   
Did you check the logs before you shut it down?
   
   
On Tue, 28 Jul 2015 9:38 am Samuel Cantero
   s...@sugarlabs.org mailto:s...@sugarlabs.org
mailto:s...@sugarlabs.org mailto:s...@sugarlabs.org
 wrote:
   
Hi Gonzalo,
   
The trac container was down. I just recently turned
 it on.
   
Somebody turned it off for some reason? If it not the
   case,
maybe the container has reached

Re: [Sugar-devel] [Systems] Error on trac reading a bug #4863

[Sam P.]

Hi Bernie,

On Tue, Jul 28, 2015 at 2:12 PM Bernie Innocenti ber...@codewiz.org wrote:

 1. We need monitoring for containers health with notifications when
 parameters go off thresholds. Similar to what Munin does.


I'm not sure how that would help us.  A container running out of resources
doesn't crash - parsoid runs almost using all the allocated memory and
parsoid+trac+others hit their cpu quotas sometimes and just keep running.

Maybe it would be more useful to monitor client metrics, like can we reach
the service over http?



 2. Containers should autorestart if they crash for any reason (with the
 usual measures to deal with services which crash repeatedly).


That is a feature built into docker.  I've enabled it in container.yml (as
a global default) and restarted trac with the new parameters.

Thanks,
Sam



 3. Since high-profile services have been deployed using Docker for a
 while, software for doing (1) and (2) certainly exists already :-)


 On 27/07/15 22:32, Samuel Cantero wrote:
  I didn't shut it down. The trac container was already off when I checked
  it.
 
  On Mon, Jul 27, 2015 at 9:40 PM, Sam P. sam@sam.today
  mailto:sam@sam.today wrote:
 
  Did you check the logs before you shut it down?
 
 
  On Tue, 28 Jul 2015 9:38 am Samuel Cantero s...@sugarlabs.org
  mailto:s...@sugarlabs.org wrote:
 
  Hi Gonzalo,
 
  The trac container was down. I just recently turned it on.
 
  Somebody turned it off for some reason? If it not the case,
  maybe the container has reached its maximum memory or processor
  limit. The docker container stops in that case.
 
  Greetings,
 
 
 
  On Mon, Jul 27, 2015 at 5:01 PM, Gonzalo Odiard
  godi...@sugarlabs.org mailto:godi...@sugarlabs.org wrote:
 
  Today, I get a error
 
  502 Bad Gateway
  nginx/1.8.0
 
  when try access trac.
 
  Gonzalo
 
  On Sat, Jul 25, 2015 at 8:40 PM, Gonzalo Odiard
  godi...@sugarlabs.org mailto:godi...@sugarlabs.org
 wrote:
 
  Thanks Sams :)
 
  On Sat, Jul 25, 2015 at 3:58 PM, Samuel Cantero
  s...@sugarlabs.org mailto:s...@sugarlabs.org wrote:
 
  Hi All,
 
  I just recently check this email. The good news is
  that Sam P already dockerized this service and now
  we have the 1.0.7 Trac version.
 
  Greetings,
 
  On Fri, Jul 24, 2015 at 11:06 AM, Gonzalo Odiard
  godi...@sugarlabs.org
  mailto:godi...@sugarlabs.org wrote:
 
  I am pretty sure dnarvaez updated the trac
  instance a time ago.
 
  On Fri, Jul 24, 2015 at 12:03 PM, Bernie
  Innocenti ber...@codewiz.org
  mailto:ber...@codewiz.org wrote:
 
  On 07/24/2015 10:34 AM, Gonzalo Odiard wrote:
   When try to read bughttp://
 bugs.sugarlabs.org/ticket/4863
   get the following error:Genshi
 UnicodeEncodeError error while rendering
   template (unknown template location)
  
   A quick google search show this bug [1]
  
   The error is originated by simply enter a
 link like this
   http://trac.edgewall.org/
   to a ticket. According to this [2] the bug
 is already solved on Trac 1.0.2
  
   Then:
   Developers: Please don't add links between
  until the error is solved.
   Systems: I don't know what version of trac
 we have running, could be
   possible update?
 
  Who's maintaining Trac these days? The wiki
  points at dnarvaez and me,
  but the former is MIA and the latter has
  installed it in 2008 and not
  touched it ever since:
 
  https://wiki.sugarlabs.org/go/Service/bugs
 
  Perhaps one of the two Sams would like to
  upgrade Trac in-place or move
  it into a docker container?
 
  --
_ // Bernie Innocenti
\X/ http://codewiz.org
 
 
 
 
  --
  Gonzalo Odiard
 
  SugarLabs - Software [for | by] children learning

Re: [Sugar-devel] [Systems] Error on trac reading a bug #4863

[Sam P.]

Did you check the logs before you shut it down?

On Tue, 28 Jul 2015 9:38 am Samuel Cantero s...@sugarlabs.org wrote:

 Hi Gonzalo,

 The trac container was down. I just recently turned it on.

 Somebody turned it off for some reason? If it not the case, maybe the
 container has reached its maximum memory or processor limit. The docker
 container stops in that case.

 Greetings,



 On Mon, Jul 27, 2015 at 5:01 PM, Gonzalo Odiard godi...@sugarlabs.org
 wrote:

 Today, I get a error

 502 Bad Gateway
 nginx/1.8.0

 when try access trac.

 Gonzalo

 On Sat, Jul 25, 2015 at 8:40 PM, Gonzalo Odiard godi...@sugarlabs.org
 wrote:

 Thanks Sams :)

 On Sat, Jul 25, 2015 at 3:58 PM, Samuel Cantero s...@sugarlabs.org
 wrote:

 Hi All,

 I just recently check this email. The good news is that Sam P already
 dockerized this service and now we have the 1.0.7 Trac version.

 Greetings,

 On Fri, Jul 24, 2015 at 11:06 AM, Gonzalo Odiard godi...@sugarlabs.org
  wrote:

 I am pretty sure dnarvaez updated the trac instance a time ago.

 On Fri, Jul 24, 2015 at 12:03 PM, Bernie Innocenti ber...@codewiz.org
  wrote:

 On 07/24/2015 10:34 AM, Gonzalo Odiard wrote:
  When try to read bug http://bugs.sugarlabs.org/ticket/4863
  get the following error:Genshi UnicodeEncodeError error while
 rendering
  template (unknown template location)
 
  A quick google search show this bug [1]
 
  The error is originated by simply enter a link like this
  http://trac.edgewall.org/
  to a ticket. According to this [2] the bug is already solved on
 Trac 1.0.2
 
  Then:
  Developers: Please don't add links between  until the error is
 solved.
  Systems: I don't know what version of trac we have running, could be
  possible update?

 Who's maintaining Trac these days? The wiki points at dnarvaez and me,
 but the former is MIA and the latter has installed it in 2008 and not
 touched it ever since:

   https://wiki.sugarlabs.org/go/Service/bugs

 Perhaps one of the two Sams would like to upgrade Trac in-place or
 move
 it into a docker container?

 --
  _ // Bernie Innocenti
  \X/  http://codewiz.org




 --
 Gonzalo Odiard

 SugarLabs - Software [for | by] children learning

 ___
 Systems mailing list
 syst...@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/systems





 --
 Gonzalo Odiard

 SugarLabs - Software [for | by] children learning




 --
 Gonzalo Odiard

 SugarLabs - Software [for | by] children learning


 ___
 Systems mailing list
 syst...@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/systems

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

Re: [Sugar-devel] [SoaS] SOAS

[Sam P.]

Hi David,

2GB should be an OK size for a soas stick.  I think you'd get 1GB of
journal storage if your lucky.

What operating system are you trying to create the sugar stick on?  If your
on windows, maybe try the win32 disk imager program [1].  If your on Linux,
try using the plan dd command.

Thanks,
Sam

[1] https://wiki.ubuntu.com/Win32DiskImager

On Wed, 22 Jul 2015 6:08 am David Leeming da...@leeming-consulting.com
wrote:

 Hi Ian

 I want to demonstrate SOAS to teachers in Vanuatu. I would like to be more
 useful, but actually don't have the luxury of time to research these arcane
 technical issues in which I am not an expert. I just want to know, is there
 a version of SOAS that is properly tested and known to work? I have used
 SOAS many times before (years ago) without any problems. Which version is
 stable and will boot without errors and not hang on use?

 Could be hardware? I will try with another flashdrive. Is 2GB of
 persistent storage too little/too much?

 David Leeming
 Solomon Islands


 -Original Message-
 From: sugar-devel-boun...@lists.sugarlabs.org [mailto:
 sugar-devel-boun...@lists.sugarlabs.org] On Behalf Of Iain Brown Douglas
 Sent: Tuesday, 21 July 2015 7:52 p.m.
 To: David Leeming
 Cc: 'Sugar-dev Devel'
 Subject: Re: [Sugar-devel] SOAS

 Hi David,

 From what you say, you already did a search for your error message.

 Does this Fedora forum answer cover your issue?
 http://forums.fedoraforum.org/showthread.php?t=301945

 I have been working with the script livecd-iso-to-disk and it works
 fine.

 I am working on SoaS Loader, here is a link to the work in progress.

 http://soas-loader.readthedocs.org/

 Good luck, and thanks for putting time in trying to demonstrate SoaS :)

 Iain




 On Tue, 2015-07-21 at 10:51 +1100, David Leeming wrote:
  Hello,
 
 
 
  I have familiarity with Sugar since working with OLPC from 2008, but I
  haven’t been active in these communities for some time. I’m just
  refreshing myself on current status of Sugar with a view to
  introducing teachers to it in a forthcoming workshop in Vanuatu. We’ll
  be using tablets as well as PCs so I have familiarised myself with
  Sugarizer. I then intended to introduce the wider world of Sugar
  conveniently with SOAS.
 
 
 
  So I have downloaded both the 32-bit and 64-bit iso files and verified
  their hashes. I also download the latest version of USB Live
  Installer. I formatted a fairly new 16GB USB with FAT32 and installed
  SOAS on it leaving 2000Mb of persistent memory. The USB stick is a
  “SanDisk Cruzer Facet 16GB”.
 
 
 
  Immediately I run into problems. When booting (on a fairly recent
  Toshiba i7 laptop) it stops with “vesamenu.c32 not a com32r image”. On
  pressing Tab key I do not see “Live” as an option, but it does start
  with the option linux0. Sugar boots and I can use it for a few
  minutes, I tried Speak and Turtle Art for instance, but within a short
  time it hangs and needs a hard boot.
 
 
 
  I repeated the whole process with the 32-bit (verified) iso file and
  same problem. I’ll give this problem only a few hours as that is all I
  have. But I would like to know what are the requirements for a
  reliable repeatable experience with SOAS, as it says on the website,
  to get Sugar into Vanuatu schools.
 
 
 
 
 
 
 
 
 
 
 
  David Leeming
 
  Solomon Islands
 
 
 
 
  ___
  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



 ___
 SoaS mailing list
 s...@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/soas

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

Re: [Sugar-devel] [Server-devel] 13.2.5 simple tests

[Sam P.]

Hi Tony,

I tested installing slides on Quozl's 106/XO4 build.

* ASLO install works automatically via the journal
* NewASLO zip does not include any html files when installed via the journal
* ASLO and sugar-install-bundle works.  I just wget the download url then
sugar-install-bundle the file.

Maybe you were trying to install the already unzipped folder?  Sugar would
try to install it /home/olpc/Activities/Slides.activity right?

Thanks,
Sam

On Fri, Jul 17, 2015 at 6:06 PM Tony Anderson tony_ander...@usa.net wrote:

 Hi, James

 Sent to wrong list - my typo.

 A df -h shows 1.6G of available store used (you remember it was over 2G
 before you trimmed it).

 slides-2.xo matches size and md5.

 Tony

 On 07/17/2015 08:51 AM, James Cameron wrote:
  On Fri, Jul 17, 2015 at 08:31:23AM +0200, Tony Anderson wrote:
  I have started some testing with 13.2.5 release.
  Thanks.
 
  These results are probably of more interest to users than
  developers.
  Disagree, certainly of interest to developers.  Yet server-devel@?
  Why not sugar-devel@?
 
  1. All of the images installed without problem. This includes XO-1,
  XO-1.5, XO-1.75, XO-4, and XO-1 SD Card.
  2. The image on XO-1.75 shows 1.6G when intially installed.
  What does this mean?
 
  3. Etoys is not installed. No Web activities are installed.
  Correct.  Since 13.2.3.  Etoys-113 from 2009 was last in OLPC OS 13.2.2.
 
  Add your own activity choices with a custom build.
 
  4. Etoys from ASLO installs and runs without problem.
  (sugar-install-bundle from USB and Journal)
  5. Welcome Web, a web activity, from ASLO installs and runs without
  problem (sugar-install-bundle from USB and Journal)
  6. Slides, a web activity, from ASLO installs from Journal without
  problem but not by sugar-install-bundle. The error is:
   'No bundle in '/home/olpc/Activities/Slides.activity' exception
  at line 481 of bundleregistry.py:
  'sugar3.bundle.ZipExtractionException'
  Was it an incomplete download?
  Check size is 1661816 and md5sum
  bb99445a536f8b6ce2d1a2f9fa4c72ef
 

 ___
 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] [road to 0.108] developing team meeting

[Sam P.]

I'm super sorry about missing the meeting.  I will definitely be there on
Monday.

On Sat, 18 Jul 2015 7:41 am Gonzalo Odiard godi...@sugarlabs.org wrote:

About 2)

I will review changes to fix bug in the journal.

The changes to palettes is a feature, and we need discuss and review,

I can work with Sam on that if he agree.


Yeah.  The earlier we start reviewing features the better!

Did you want me to review your journal patches?

Thanks,
Sam


Gonzalo

On Fri, Jul 17, 2015 at 6:30 PM, Martin Abente 
martin.abente.lah...@gmail.com wrote:

We didn't have enough people, so we are moving the meeting to Monday 20. We
discussed a few topics though:

1. We will be merging fixes on master, and if anything serious comes up we
will make a 0.106.1 release from the branch.

2. Gonzalo will review Sam's changes to palettes.

3. I will be reviewing Gonzalo's fixes.

See you on Monday,

Regards,

Martin.

On Tue, Jul 14, 2015 at 10:10 AM, Gonzalo Odiard godi...@sugarlabs.org
wrote:

 +1 from me

On Tue, Jul 14, 2015 at 11:09 AM, Martin Abente 
martin.abente.lah...@gmail.com wrote:

 @Sam: 21 UTC works for me!

Does it work for everybody else?

On Tue, Jul 14, 2015 at 7:56 AM, Sam P. sam@sam.today wrote:

  Hey Martin,

I can't do 14 UTC.  Would 21/22 UTC be ok for you?

Otherwise, I'm always happy to write emails :)

Thanks,
Sam

On Tue, 14 Jul 2015 12:00 am Martin Abente martin.abente.lah...@gmail.com
wrote:

  Hello everyone,

Now that Sugar 0.106 has been released, it is time to think about what has
been done and what needs to be done for Sugar 0.108. Therefore, I proposed
we meet on:

Date: Friday July 17.

Time: 14:00 UTC.

Place: #sugar-meeting - freenode.

Does that time work for you? If not, feel free to propose another time.

Regards,

Martin.


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



-- 

Gonzalo Odiard

SugarLabs - Software [for | by] children learning


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



-- 

Gonzalo Odiard

SugarLabs - Software [for | by] children learning
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [road to 0.108] developing team meeting

[Sam P.]

Hey Martin,

I can't do 14 UTC.  Would 21/22 UTC be ok for you?

Otherwise, I'm always happy to write emails :)

Thanks,
Sam



On Tue, 14 Jul 2015 12:00 am Martin Abente martin.abente.lah...@gmail.com
wrote:

 Hello everyone,

 Now that Sugar 0.106 has been released, it is time to think about what has
 been done and what needs to be done for Sugar 0.108. Therefore, I proposed
 we meet on:

 Date: Friday July 17.
 Time: 14:00 UTC.
 Place: #sugar-meeting - freenode.

 Does that time work for you? If not, feel free to propose another time.

 Regards,
 Martin.



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

Re: [Sugar-devel] Sugar 0.106 Video

[Sam P.]

Sounds like a very good way to do it!

On Wed, Jul 8, 2015 at 7:55 AM James Cameron qu...@laptop.org wrote:

 I cannot speak for the tools that Sam may have, but a method for
 internationalisation is to:

 - write down what Sam said,

 - translate to Spanish,

 - play the video with sound muted,

 - record yourself speaking while watching the video,

 - repeat the recording until you think it is best,

 - send the recordings to Sam _or_ use tools to replace the audio track
   with your recording,

 What do you suggest, Sam?

 On Tue, Jul 07, 2015 at 12:01:11PM -0500, Laura Vargas wrote:
  Great video Sam!
 
  I would love to help with the Spanish version :D
 
  Let me kmow how to proceed.
 
  2015-07-05 18:40 GMT-05:00, James Cameron qu...@laptop.org:
   Reviewed, please merge.  ;-)
  
   --
   James Cameron
   http://quozl.linux.org.au/
   ___
   Sugar-devel mailing list
   Sugar-devel@lists.sugarlabs.org
   http://lists.sugarlabs.org/listinfo/sugar-devel
  
 
 
  --
  Laura V.
  ID SomosAZUCAR.Org
 
  Identi.ca/Skype acaire
  IRC kaametza
 
  Happy Learning!

 --
 James Cameron
 http://quozl.linux.org.au/
 ___
 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] Sugar 0.106 Video

[Sam P.]

Hi,

So the 0.106 release is tomorrow, which is pretty awesome.

I have made a video summarizing the features since we did that last release
and it seems like a good idea:  https://youtu.be/PXFaXAGIw04

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

Re: [Sugar-devel] Change request: Fix open with API

[Sam P.]

Hi Tony,

I think you have misunderstood the capabilities of the api.

The api does not support launching with uris (which is something to look
into for 108) or activity ids.

The api supports bundle ids (open a new terminal activity) and object ids
(open this memorize set).  This allows for many of the use cases you
described although being very simple.

Directly using sugar-launch from activity processes is suboptimal, as
activities should not launch child processes (Rainbow security model).
This was discussed when the feature was being implemented.

I do not see why a feature that has some use cases and does not destabilise
the rest of the system should be dropped so late in the cycle.

Thanks,
Sam

On Fri, 3 Jul 2015 3:15 pm Tony Anderson tony_ander...@usa.net wrote:

  As I understand it, the release of 0.106 is to be made on Monday. This
 does not seem to warrant a delay in that release. Moving a capability from
 sugar or sugar3 to the toolkit doesn't imply a visible change to the api as
 seen by an activity developer.

 I don't understand the assumption that downloading a file in Browse to the
 Journal implies that the user wants to access it immediately. For example,
 if I download 'War and Peace', I may want to read it when I get the laptop
 home, not in class. For use with the schoolserver, it was necessary to
 patch Browse to download a pdf to the Journal and not load it into a new
 window. I need to do this also for txt books from Rachel. Fortunately,
 Browse downlaods epub directly to the Journal (the format of the Gutenberg
 books in Internet in a Box).

 Browse itself is a problem in this scenario. It (along with the Terminal
 activity) is an exception by providing tabs. It would be useful if the
 launch facility would open a new tab and not launch a new instance of
 Browse when it is already running.

 Launching activities based on mime_type is already a problem. How is one
 activity to know whether Browse or Etoys or ImageViewer or Paint  wiil
 respond to a
 launch request for an image.

  How is one activity going to determine the activity id (The activity id
 (e.g., 6f7f3acacca87886332f50bdd522d805f0abbf1f) of type STRING as passed
 on the command line
 http://wiki.sugarlabs.org/go/Development_Team/Low-level_Activity_API#Command_Line_Arguments)
 of another activity?

 Originally, sugar-launch was to pass through options -u (uri) and -o
 (object_id). The version I use does this, so the following code in an
 activity displays an svg:

 sugar-launch -u 'file:///home/olpc/Documents/my.svg'
 org.laptop.WebActivity

 Similarly, an activity can use the datastore class to get an object_id and
 use the -o option to, in effect, resume an activity from the Journal.

 The only 'trick' is to run sugar-launch from the activity. However, this
 works:

 from subprocess import call

 call('sugar-launch -u 'file:///home/olpc/Documents/my.svg'
 org.laptop.WebActivity', shell=True)

 In the context of the GSOC project, it is important that the Web Confusion
 activity be able to pass a specific html file to Browse for use with the
 interactive javascript shell. This capability is satisfied by sugar-launch
 with the -u option. However, sugar-launch uses optparse which is deprecated
 in Python 2.7 so the version I am using now has been modified it to use
 argparse.

 Using datastore, an activity can launch, for example, Memorize with a
 specific 'game'. So, for example, a teacher is introducing Roman numerals.
 The 'lesson' activity could resume Memorize from the Journal with a game on
 Roman numerals (previously downloaded from the school server).

 It would seem appropriate to keep the release schedule and do some
 rethinking in the use cases for this feature. Sugar-launch launches the
 activity by the command line and so uses Sugar to perform the launch. It
 would be easy to provide this mechanism to an activity avoiding the
 'subprocess' call (although that is hardly a difficult interface). This new
 feature should at least provide the functionality of sugar-launch.


 Tony




 On 07/02/2015 09:33 PM, Gonzalo Odiard wrote:

 I found a problem in the implementation of
 Start_activity_from_another_activity feature [1]
 Usually, when the programmer want start one activity from another,
 need display in the user interface information about the activity,
 like the name or the icon.
 One example of the use is in Browse activity [2]

  The problem with this is that we are using
  jarabe.journal.bundlelauncher.get_bundle()
 and that is part of sugar, not the sugar-toolkit.
 We should not use that code in the activities, because is internal to
 Sugar,
 and we don't have any warranty of stability.

 I know is very late in the release cycle, but I think is a error ship a
 release
 with a broken API. After that, activity developers need keep compatibility
 with the api provided in the broken release for ever.
 While the developer can add another try catch, is a source of errors,
 and usually difficult to understand 

Re: [Sugar-devel] adding gtk as a dependency on sugar-artwork

[Sam P.]

Hi Gonzalo,

Testing without your patch it appears that the journal background didn't
get broken - so most of the breakage must have been fixed later in the Gtk+
3.17 cycle!

Using your patch (the 1st one), it fixes the log tree view and the journal
still works fine.  I will send a patch.

Next time I'll try to be more up to date with how the Gtk+ release cycle
works so that I'm not submiting sugar patches for Gtk+ bugs!

Thanks,
Sam

On Thu, Jul 2, 2015 at 5:02 AM Gonzalo Odiard godi...@sugarlabs.org wrote:

 If that don't work, should be good test:

 diff --git a/gtk3/theme/gtk-widgets.css.em b/gtk3/theme/gtk-widgets.css.em
 index 67e4e48..af87900 100644
 --- a/gtk3/theme/gtk-widgets.css.em
 +++ b/gtk3/theme/gtk-widgets.css.em
 @@ -221,9 +221,18 @@ column-header .button:hover:active {
  border-width: 0px;
  }

 +GtkTreeView row:even {
 +background-color: @row_even;
 +}
 +
  GtkTreeView row:nth-child(even) {
  background-color: @row_even;
  }
 +
 +GtkTreeView row:odd {
 +background-color: @row_odd;
 +}
 +
  GtkTreeView row:nth-child(odd) {
  background-color: @row_odd;
  }

 On Wed, Jul 1, 2015 at 3:15 PM, Gonzalo Odiard godi...@sugarlabs.org
 wrote:

 Sam,
 I don't have rawhide installed to test, can you try adding rules for the
 two new and old ways, like here:

 diff --git a/gtk3/theme/gtk-widgets.css.em b/gtk3/theme/gtk-widgets.css.em
 index 67e4e48..d14bbfb 100644
 --- a/gtk3/theme/gtk-widgets.css.em
 +++ b/gtk3/theme/gtk-widgets.css.em
 @@ -221,10 +221,11 @@ column-header .button:hover:active {
  border-width: 0px;
  }

 -GtkTreeView row:nth-child(even) {
 +GtkTreeView row:even, GtkTreeView row:nth-child(even) {
  background-color: @row_even;
  }
 -GtkTreeView row:nth-child(odd) {
 +
 +GtkTreeView row:odd, GtkTreeView row:nth-child(odd) {
  background-color: @row_odd;
  }

 Works on Gtk 3.16, we need check if works on Gtk 3.18

 Gonzalo

 On Wed, Jul 1, 2015 at 1:29 PM, Martin Abente 
 martin.abente.lah...@gmail.com wrote:

 From the tests I have done, I confirmed it is used in building time,
 therefore I have reverted the patch until we can determine a better
 solution.

 On Wed, Jul 1, 2015 at 12:05 PM, Martin Abente 
 martin.abente.lah...@gmail.com wrote:

 Hello Sam,

 Different people reported an error while building sugar-artwork
 packages. The error is caused by this commit [1] which makes GTK a building
 requirement for sugar-artwork, but:

 a) if GTK version version is really used on building time, then the
 approach used in [1] is wrong, because the css would depend on the GTK
 version on the packager on something that is related to the final user
 runtime environment.

 b) if the GTK version is only used in running time, then we should make
 sure it does not become a building requirement.

 In either case, it does not seems to make sense to make it a dependency.

 Regards,
 Martin.


 Refs:
 1.
 https://github.com/sugarlabs/sugar-artwork/commit/813a2d77d83284b031a4f2bd5775b9f82b12846e





 --
 Gonzalo Odiard

 SugarLabs - Software [for | by] children learning




 --
 Gonzalo Odiard

 SugarLabs - Software [for | by] children learning

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

Re: [Sugar-devel] adding gtk as a dependency on sugar-artwork

[Sam P.]

Patch:  https://github.com/sugarlabs/sugar-artwork/pull/67

On Thu, Jul 2, 2015 at 9:15 PM Gonzalo Odiard godi...@sugarlabs.org wrote:

 Great!

 On Thu, Jul 2, 2015 at 7:05 AM, Sam P. sam@sam.today wrote:

 Hi Gonzalo,

 Testing without your patch it appears that the journal background didn't
 get broken - so most of the breakage must have been fixed later in the Gtk+
 3.17 cycle!

 Using your patch (the 1st one), it fixes the log tree view and the
 journal still works fine.  I will send a patch.

 Next time I'll try to be more up to date with how the Gtk+ release cycle
 works so that I'm not submiting sugar patches for Gtk+ bugs!

 Thanks,
 Sam

 On Thu, Jul 2, 2015 at 5:02 AM Gonzalo Odiard godi...@sugarlabs.org
 wrote:

 If that don't work, should be good test:

 diff --git a/gtk3/theme/gtk-widgets.css.em
 b/gtk3/theme/gtk-widgets.css.em
 index 67e4e48..af87900 100644
 --- a/gtk3/theme/gtk-widgets.css.em
 +++ b/gtk3/theme/gtk-widgets.css.em
 @@ -221,9 +221,18 @@ column-header .button:hover:active {
  border-width: 0px;
  }

 +GtkTreeView row:even {
 +background-color: @row_even;
 +}
 +
  GtkTreeView row:nth-child(even) {
  background-color: @row_even;
  }
 +
 +GtkTreeView row:odd {
 +background-color: @row_odd;
 +}
 +
  GtkTreeView row:nth-child(odd) {
  background-color: @row_odd;
  }

 On Wed, Jul 1, 2015 at 3:15 PM, Gonzalo Odiard godi...@sugarlabs.org
 wrote:

 Sam,
 I don't have rawhide installed to test, can you try adding rules for
 the two new and old ways, like here:

 diff --git a/gtk3/theme/gtk-widgets.css.em
 b/gtk3/theme/gtk-widgets.css.em
 index 67e4e48..d14bbfb 100644
 --- a/gtk3/theme/gtk-widgets.css.em
 +++ b/gtk3/theme/gtk-widgets.css.em
 @@ -221,10 +221,11 @@ column-header .button:hover:active {
  border-width: 0px;
  }

 -GtkTreeView row:nth-child(even) {
 +GtkTreeView row:even, GtkTreeView row:nth-child(even) {
  background-color: @row_even;
  }
 -GtkTreeView row:nth-child(odd) {
 +
 +GtkTreeView row:odd, GtkTreeView row:nth-child(odd) {
  background-color: @row_odd;
  }

 Works on Gtk 3.16, we need check if works on Gtk 3.18

 Gonzalo

 On Wed, Jul 1, 2015 at 1:29 PM, Martin Abente 
 martin.abente.lah...@gmail.com wrote:

 From the tests I have done, I confirmed it is used in building time,
 therefore I have reverted the patch until we can determine a better
 solution.

 On Wed, Jul 1, 2015 at 12:05 PM, Martin Abente 
 martin.abente.lah...@gmail.com wrote:

 Hello Sam,

 Different people reported an error while building sugar-artwork
 packages. The error is caused by this commit [1] which makes GTK a 
 building
 requirement for sugar-artwork, but:

 a) if GTK version version is really used on building time, then the
 approach used in [1] is wrong, because the css would depend on the GTK
 version on the packager on something that is related to the final user
 runtime environment.

 b) if the GTK version is only used in running time, then we should
 make sure it does not become a building requirement.

 In either case, it does not seems to make sense to make it a
 dependency.

 Regards,
 Martin.


 Refs:
 1.
 https://github.com/sugarlabs/sugar-artwork/commit/813a2d77d83284b031a4f2bd5775b9f82b12846e





 --
 Gonzalo Odiard

 SugarLabs - Software [for | by] children learning




 --
 Gonzalo Odiard

 SugarLabs - Software [for | by] children learning




 --
 Gonzalo Odiard

 SugarLabs - Software [for | by] children learning

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

Re: [Sugar-devel] Collaboration

[Sam P.]

Yeah, it looks pretty scammy.  It references CorprateSocialResponsibility,
engaging with youths and is from Facebook not email - making it look like a
mass campaign not somebody targeting sugarlabs.

Maybe we should just say:  SL is a volunteer run, not for profit
organization.  We are always delighted when people are interested in
broadening the reach of out community.  Please contact us via ml
(sugar-de...@lists.sl.o) and we are always happy to discuss how to
represent our vision, product and brand.

I'm betting my money that he won't reply once he figures out we aren't
gonna pay him money :)

On Wed, 1 Jul 2015 6:11 pm James Cameron qu...@laptop.org wrote:

 We've seen this message twice now; something wrong with your mail?

 http://lists.sugarlabs.org/archive/sugar-devel/2015-June/050455.html
 http://lists.sugarlabs.org/archive/sugar-devel/2015-July/050475.html

 Are you sure it isn't spam?  It looks like a form letter, because it
 mentions company, brand, and tries to use a halo effect.  I've not
 found much public info on Esya'15 either, except for
 http://esya.iiitd.edu.in/

 You might also invite Bhavna, by mail, to join the Sugar mailing
 lists.

 --
 James Cameron
 http://quozl.linux.org.au/
 ___
 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] [IAEP] Open issues

[Sam P.]

Hi Walter,

Still integrating them into the site, I'll keep you updated.

Thanks,
Sam

On Sat, Jun 27, 2015 at 12:58 PM Walter Bender walter.ben...@gmail.com
wrote:

 I posted some edits to a few weeks ago with some heavy editing of the
 website content. Not sure where things stand.

 -walter

 On Fri, Jun 26, 2015 at 2:23 PM, Tymon Radzik dwg...@gmail.com wrote:
  Heh, the topic of website was already considered few months ago and we
  couldn't reach consesus about final view - we had two versions: mine and
  Sam's one. We probably need to rethink about expected effect and work on
  already started project :)
 
  pt., 26.06.2015 o 20:05 użytkownik samson goddy samsongo...@hotmail.com
 
  napisał:
 
  Okay, i am done with my exams but i am will resuming Monday. I also i
 will
  work with the new survey, but the problem is that i can get through
 Caryl.
  Do anyone know her status?, if yes please fill me in.
 
  Best
  Samson Goddy
 
  
  From: dan.tena...@mail.ru
  To: sebast...@fuentelibre.org
  Date: Thu, 25 Jun 2015 19:40:17 +0300
  CC: i...@lists.sugarlabs.org; sugar-devel@lists.sugarlabs.org
  Subject: Re: [Sugar-devel] [IAEP] Open issues
 
 
  Wednesday, June 24, 2015 8:48 PM -05:00 from Sebastian Silva
  sebast...@fuentelibre.org:
 
 
  On 24/06/15 03:40, Sam P. wrote:
   IDK about the election but. Hopefully somebody who knows about that
   can respond.
 
  Here's a status report:
 
  I asked the board to appoint me election committee.
 
  Then the board decided we needed to have diversity in the committee.
 
  Now it's hard for Caryl, Samson and I to coincide, as one has been
  traveling, the other has exams, and I am in the process of relocating.
 
  I've setup a surveying system (a couple of months ago), that is pretty
  much ready for voting. I am still waiting for the committee to decide
  how many seats will be available and when to do the election.
 
  I was hoping to use the opportunity to make a wider survey in the
  community that could inform the direction for the Board. I will limit
  myself to be the technical person and make sure the surveying system
  works reliably, while I still wait for the other members of the
  committee to make decisions and try the surveying system.
 
 
  Thanks,
 
  After making you and Ms. Bigenho wait for several weeks to receive
  approval by the board to be added to the election committee and then
 seeing
  Mr. Parkinson receive overnight  approval, things were left somewhat
  unclear.
 
  Dan
 
 
  --
  I+D SomosAzucar.Org
  icarito #somosazucar en Freenode IRC
  Nadie libera a nadie, nadie se libera solo. Los seres humanos se
 liberan
  en comunión - P. Freire
 
 
 
  ___ Sugar-devel mailing list
  Sugar-devel@lists.sugarlabs.org
  http://lists.sugarlabs.org/listinfo/sugar-devel
  ___
  IAEP -- It's An Education Project (not a laptop project!)
  i...@lists.sugarlabs.org
  http://lists.sugarlabs.org/listinfo/iaep
 
 
  ___
  Sugar-devel mailing list
  Sugar-devel@lists.sugarlabs.org
  http://lists.sugarlabs.org/listinfo/sugar-devel
 



 --
 Walter Bender
 Sugar Labs
 http://www.sugarlabs.org
 ___
 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] GCI 2014 Wrapup

[Sam P.]

Hi All,

Ignacio and I recently went to San Fransisco as our GCI 2014 prize [1].
San Francisco was a beautiful city and seeing Google (and a little Mozilla
and Twitter) was a really amazing experience.

But it wasn't just about San Fransisco.  Walter was also in San Fransisco
which was amazing [2].  It was great to be chat sugar in real life with
Walter and Ignacio.  Despite the very fun atmosphere of the trip, we even
managed to hack together on some productive things :)  Walter and I hacked
on the website a little (I'll smooth the edges of that soon so we can push
it), while Ignacio and Walter jammed on turtlejs.

The Google Code In was a great competition and opportunity for me (and
probably many other participants) to become involved with open source.  Of
course, thank you to Google for running it.

But thank you very much to everyone who mentored us during the GCI.  Thank
you to Gonzalo, Tch and Walter who hugely increased their code review
workloads to help teach us all how to participate in open source.  Thank
you to everyone who made it possible that we didn't just make software for
learning children but also a software by learning children, because you
guys teach us so much.

Thanks,
Sam

[1] http://people.sugarlabs.org/sam/gci2014-2.jpeg
[2] http://people.sugarlabs.org/sam/gci2014-1.jpeg
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Open issues

[Sam P.]

Hello Dan,

On Tue, Jun 23, 2015 at 1:44 AM Dan Tenason dan.tena...@mail.ru wrote:

 It was impressive to see how quickly Mr. Innocenti updated the
 infrastructure once he was made aware that the servers had gone down. Some
 other problem areas have not been dealt with as quickly.


We're all volunteers doing this in our own time to the best of my
knowledge.  Any contributions and patches always welcome!



 Sugar Labs has now been operating for six months without an oversight
 board. The early June meeting did not meet quorum and the mid June meeting
 seemed to happen. After appointing a membership committee, no visible
 progress has been made towards holding an election. Is it time to drop the
 Oversight Board as an unnecessary burden?


I'm pretty sure that the oversight board members are still alive and that
they are making productive decisions.  According to the wiki page [1] they
had a meeting 2 months ago which they made decisions relating towards the
Sugar Deployment Survey, Turtle Art Days and GSOC2015.  From my knowledge
they are also in control of the spending and domains and those important
oversight things.

I do not see any reason to drop the oversight board.

IDK about the election but.  Hopefully somebody who knows about that can
respond.



 The claim of 'Sugar’s Activities are used every school day by nearly 3
 million children' is still present as a fact on the Sugar Labs web site.
 That validity fact is in question. There are several example countries were
 current usage is well below 100% which puts the assumption that ever XO
 ever shipped is used daily.


I was chatting with Walter about the new website a while ago and he said
that we should say we have 3 billion users across 270 languages or
something like that.  I think that was just a joke, but you get the point.
I'm sure that 3million is probs legit because of SoaS and sugarizer as well
as XOs.

In my **personal** opinion I do not think that the number on the website is
an important issue.  We have many more bugs and UX bugs that need fixing,
and even in the context of the website there are bigger issues.



 It would be appreciated if someone from Sugar Labs could clarify the
 status of these issues.


Hopefully I did!  I'm just an individual volunteer, so don't count my word.

Thanks,
Sam

[1]  http://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2015-05-04



 --
 Dan Tenason
 ___
 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] libflashplayer.so and WebCam issue

[Sam P.]

Hi,

I doubt that webrtc support (HTML5 camera access api) will come soon.

Firstly, it appears to be a driver issue for Firefox.  Fedora 20 ships with
Firefox 25, and webrtc (getUserMedia) was introduced as early as in Firefox
17.  But Browse does not use Firefox/gecko anymore.

Browse uses WebKitGtk which is does not even support permission requests
for camera.  Epiphany uses WebKitGtk2, which does support camera permission
requests.  However, as of Fedora 23 Rawhide (updated last week), there is
no support for webrtc (aka. actually accessing the camera) in Epiphany
according to my tests.

I have no idea what your flash app is doing, but the path of least
resistance probably involves many hacks on top of Gtk2.  I don't think that
the XO camera works with Gtk3, from memory it is blocking the Gtk3 Record
port.

Thanks,
Sam

On Sun, Jun 14, 2015 at 2:40 PM Gustavo Duarte gus.dua...@gmail.com wrote:

 Hey James,

 I agree with you that the way should be achieve  HTML5 support. I expect
 it be done soon.

 Than you very much.

 Gustavo.
 ___
 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] Collaboration: Server Name change

[Sam P.]

Hello,

Could you please attach the log file?

Thanks,
Sam

On Fri, May 29, 2015 at 8:51 PM tkk...@nurturingasia.com wrote:

 I am running 13.2.4 for XO-1 (build 16) with Sugar 0.104.1.

 When I go My to Settings  Network and try to add a Server name I notice I
 could not save a name of my choice e.g. schoolserver.myserver.com. In the
 past I did have success adding schoolserver.lan

 I notice this when I was testing 13.2.4 for XO-1, Sugar-0.105 (build 2)
 since  I could change the collaboration server name without issue.

 Advice?

 ---
 T.K. Kang



 ___
 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] Docker in Sugar/XO laptop

[Sam P.]

Hi,

I'm not sure why docker is a requirement for developing web applications.

Setting up a docker image requires lots of storage space and lots of
download - docker stores a full os to chroot or whatever into.  Even with
there cool CoW file systems, docker still needs to store a least 1 Linux
distribution image.  XOs do not have the disk space and most people do not
have the internet speed.  (Even with a reasonable residential connection it
is nowhere near fast enough to use docker - I find myself ssh-ing into a
server instead)

I'm also not sure why docker needs a gui.  Docker is not a tool needed by
any beginner programmer of the likes of that.  Docker is mainly a tool for
systems administration or containerizing things.

Maybe an interface to pip as part of Pippy activity would be more helpful
for letting kids make web apps.

Thanks,
Sam

On Sat, May 23, 2015 at 5:00 PM tkk...@nurturingasia.com wrote:


 I'm puzzled as to why you would want an XO laptop to host docker
 applications; thus going slower and having less memory.

 Perhaps some real smart children can start using their XO laptop to learn
 how to host various web applications from docker.

 Asking for Docker to be surrounded by Sugar doesn't make any sense.

 I mean a sugar activity to start/launch docker that is installed.

 This goes against the idea of a personal computer; where all resources
 are shared; files, journal, network, hardware.

 Using the XO laptop which is a personal computer but turning it into a
 server running web applications for their friends under the tree. They are
 sharing/collaborating in a different way.

 Hope it makes sense :-)


 ___
 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