Re: [Sugar-devel] Sugarizer flatpak package
2017-04-14 2:00 GMT-03:00 Tony Anderson : > I apparently misunderstood. I had thought you were working on Sugar. Does > this address any current problem with installing Sugarizer? > Does this flatpak option apply to Sugar? No Tony, just Sugarizer. > On 04/14/2017 12:51 PM, Dave Crossland wrote: > > Hi > > Great work :) > > On Apr 13, 2017 12:41 PM, "Manuel Quiñones" > wrote: >> >> Hi, >> >> I'm working on a flatpak package for Sugarizer. >> >> Flatpak http://flatpak.org/ is the new way to distribute applications >> in GNU/Linux. Is great for many reasons. One reason is that the same >> package works for any modern Linux distribution like Fedora, Debian, >> Arch, Ubuntu. I made the package targetting Endless OS which is >> leading the development of flatpak. But again, any modern distro will >> benefit with this. >> >> My original post is here: >> https://community.endlessm.com/t/sugarizer-in-endless/2097 >> >> My current state: I have a repository with the toolchain and >> instructions for building a Linux64 package >> https://github.com/manuq/sugarizer-electron >> >> I was wondering where to upload the package. I think the Sugarlabs >> infrastructure would be the best option to store it. Here are >> instructions on how to start a remote flatpak repository in a >> webserver: >> https://blogs.gnome.org/alexl/2017/02/10/maintaining-a-flatpak-repository/ >> >> The first release will be a big download, but flatpak is supposed to >> download the delta between versions. >> >> I will update the Sugarizer wiki page once I manage to log into the SL >> wiki again. >> >> -- >> .. manuq .. >> ___ >> 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 > -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Sugarizer flatpak package
Hi, I'm working on a flatpak package for Sugarizer. Flatpak http://flatpak.org/ is the new way to distribute applications in GNU/Linux. Is great for many reasons. One reason is that the same package works for any modern Linux distribution like Fedora, Debian, Arch, Ubuntu. I made the package targetting Endless OS which is leading the development of flatpak. But again, any modern distro will benefit with this. My original post is here: https://community.endlessm.com/t/sugarizer-in-endless/2097 My current state: I have a repository with the toolchain and instructions for building a Linux64 package https://github.com/manuq/sugarizer-electron I was wondering where to upload the package. I think the Sugarlabs infrastructure would be the best option to store it. Here are instructions on how to start a remote flatpak repository in a webserver: https://blogs.gnome.org/alexl/2017/02/10/maintaining-a-flatpak-repository/ The first release will be a big download, but flatpak is supposed to download the delta between versions. I will update the Sugarizer wiki page once I manage to log into the SL wiki again. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Browse activity and FTP sites support
2014-04-22 10:33 GMT-03:00 Gustavo Duarte : > Here you can see responses from Webkit-gtk list, seems like, this feature > isn't supported yet. > > https://lists.webkit.org/pipermail/webkit-gtk/2014-April/001877.html OK, another weakness of WebKitGTK.. Thanks for reporting back. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] olpc-france, my summary
Lionel gave a nice demo of Sugarizer in progress, with Journal items shared through a server. I presented Sugar development process and how to get involved. Also talked about Sugar Web. Jon Nettleton presented Open WebOS via hangout. Is an interesting platform, and the UI very much like Sugar. Christoph Derndorfer and Bastien Guerry raised the question "how will Sugar be in 2021?". I think is up to the people getting involved. Devs, deploys, pedagogues. There were also good talks about learning (Teachers engagement in technology). Also enjoyed the Semantic Web talk. I tried to hack as much as possible. Worked with Hiou and Loic in a web activity that talks with Hiou's translation AI library. Helped Tony Anderson to get Flash installed in XO-1. Gave a Sugar intro to youngers that are going to work in Madagascar deploy. Thanks a lot to the organizers, and to Loic for hosting me :) Cheers, -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Browse activity and FTP sites support
2014-04-16 9:45 GMT-03:00 Gustavo Duarte : > Hi Manuel, > > I installed Web 3.4.1 and going to > ftp://descargas.ceibal.edu.uy/espacio_tecnico/actividades/dx4/base/arm/Read-106.1.xo > > Following error is showed. > > Oops! It was not possible to show this website > > The website > atftp://descargas.ceibal.edu.uy/espacio_tecnico/actividades/dx4/base/arm/Read-106.1.xo > seems to be unavailable. The precise error was: > > URL cannot be shown > > It could be temporarily switched off or moved to a new address. Don't forget > to check that your internet connection is working correctly. Ouch. > So what could be the next step on this research? You can try writting to WebKitGTK mailing list. They should be able to tell you if it is a bug or is on purpose. There are special applications for navigating FTP so one option is that they discourage ftp navigation in the browser. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Browse activity and FTP sites support
2014-04-14 9:05 GMT-03:00 Gustavo Duarte :
> Hi folks,
>
> I'm having problems browsing on FTP sites in Browse activity.
>
> I'm using Browse activity version 156, I guess that is the last, right ?
>
>
> When I went to ftp, url like: ftp://debian.netcologne.de/debian-cd, a page
> error was showed saying:
>
> "This wep page couldn't be loaded"
> Try again.
>
>
> I added on browse.py file a log on line 736, like this:
>
> logging.warning('load_eror_cb, uri: ' + uri + ' | web error code: '+
> str(web_error.code))
>
>
> The line showed when running Browse activity is:
>
> 1397314748.301408 WARNING root: load_eror_cb, uri:
> ftp://debian.netcologne.de/debian-cd | web error code: 101
>
>
> So the Web error code reporting by Webkit is 101, what means ?
The WebkitGTK docs are weak here, but I think is a Soup status code:
https://developer.gnome.org/libsoup/unstable/libsoup-2.4-soup-status.html
>
> Has Webkit support for browsing on FTP sites ?
Have you tried Epiphany? If it works there, I would look at their source code.
>
> Thanks in advance.
>
> Gustavo.
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
--
.. manuq ..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] web and data-binding, promises
Here at Cité Des Sciences, Paris, i was motivated to go back to sugar-web development. One of the things I always wanted to try is data-binding and promises in JS. So I tried first with SVG graphics. Currently in the UI we treat SVG as background images, and we have one image per fill/stroke color. And we get them with an html request. but tag can be also embedded in html. Here an example of a pulsing icon: http://manuq.github.io/shell-activity/ I used RactiveJS for this. SVG is treated as a Mustache template, something that we already have inside. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Pull requests + buildbot
2014-04-05 21:51 GMT-03:00 Daniel Narvaez : > Hey, > > I have finally setup integration between pull requests and buildbot. > > When you push a pull request buildbot will trigger a build and update the > github UI to indicate success or failure. The idea is that we should not > normally merge a pull request unless the build was successful. > > You can open the build page by clicking on the "details" link. If the build > failed for reasons which are not related to the patches, you can use the > "Rebuild" button to retry it. > > The integration is done with a very simple node server > https://github.com/sugarlabs/sugar-gitbot/blob/master/app.js > I don't expect it to be particularly solid yet, so if you run into any issue > please let me know! Great work! I see it is running well. So it closes the PR while checking and then if check succeeds reopens it again? -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Moving more modules to github
Hi, 2014-04-04 8:18 GMT-03:00 Daniel Narvaez : > Hello, > > I think we should move more of our modules to github, at least all the ones > we are currently building in sugar-build. > > That will make it easier for contributors because they won't have to go > through two different processes to submit patches. Also gitorious lacks pr > notifications which is really bad. > > Finally, it would make it easier to detect changes to the modules in > buildbot without having to poll, which is giving issues to our server (you > could probably do the same on gitorious, but I'm not really looking forward > to write and maintain that for two different services). I'm also planning to > add support for triggering builds on pr submission, so that broken ones can > be marked as such in the UI, and it would be good for all the modules to > benefit from this. > > So here are the modules I would like to move > > sugar This one is already in Github. > sugar-toolkit > browse > write > chat > read > log > terminal > pippy > imageviewer > jukebox > turtleart > > What needs to be done > > 1 Get permission from module maintainers. If you are reading this please > confirm you are fine with this. Yes, this move is welcome for me as well. I need to take care of Browse contributions in Gitorius in order to not lose them in the move. > 2 Mirror the modules on github. I can take care of that. > 3 Update sugar-build. I can take care of that. > 4 Update pootle. Gonzalo, did you volunteer? :) > 5 Setup a redirect from git.sugarlabs.org to github.com. Anyone knows > who/how did it for the core modules? I can't remember :( > -- > Daniel Narvaez > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar 0.101.4 (unstable)
2014-04-01 21:46 GMT-03:00 Daniel Narvaez : > Hello, > > this is to announce the release of 0.101.4. We made some terrific progress, > have a look to the extensive release notes (credits to Walter Bender) > > http://wiki.sugarlabs.org/go/0.102/Notes Excellent! Thanks for the release! -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Time spent on activity (was Best time, format for logging?)
2014-03-28 9:44 GMT-03:00 Gonzalo Odiard :
>
>
>
> On Fri, Mar 28, 2014 at 9:38 AM, Tony Anderson
> wrote:
>>
>> It is easier for users to understand shutting down the laptop by pressing
>> the power button twice than to use the shutdown in the XO menu. However,
>> this shutdown does not properly close open activities.
>>
>> When the power light goes red, I would assume it would be possible to
>> perform an orderly shutdown.
>>
>> The record is of an activity session so maintaining a list of session
>> information seems logical.
>>
>> One option is to record the launch time in the stop time at launch so that
>> the metadata shows that a an activity session was started but not properly
>> closed.
>
>
> I like that. Save in zero at start, then every write_file just need replace
> the last value.
what about something like:
{start: 1396011589, stops: [1396011616, 1396045612]}
an activity that was inappropriately closed and never logged a stop:
{start: 1396011589}
>
> Gonzalo
>
>
>>
>>
>> Tony
>>
>>
>> On 03/27/2014 09:45 PM, sugar-devel-requ...@lists.sugarlabs.org wrote:
>>>
>>> I was in doubt for two reasons: 1. because unlike launch_time, this
>>> spent-times metadata will not be saved if the activity does not end
>>> properly: could be a crash, a programming error, end of battery, etc.
>>> So the item N of spent-times will not necessarily correspont to item N
>>> of launch-times.
>>
>>
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
>
>
> --
> Gonzalo Odiard
>
> SugarLabs - Learning Software for children
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
--
.. manuq ..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Time spent on activity (was Best time, format for logging?)
2014-03-28 10:12 GMT-03:00 Gonzalo Odiard :
>>
>> >
>> > I like that. Save in zero at start, then every write_file just need
>> > replace
>> > the last value.
>>
>> what about something like:
>>
>> {start: 1396011589, stops: [1396011616, 1396045612]}
>>
>> an activity that was inappropriately closed and never logged a stop:
>>
>> {start: 1396011589}
>>
>>
>
> IMHO, you want one stop for session. Sugar execute write_file every time
> you switch activities, but you don't want save all of them, just the last.
>
> Right now, you have:
>
> {launch_time: 1396011589, 1396011616, 1396045612}
>
> If you save the accumulated time in zero at start you will have:
>
> {session_time: 23960, 0, 5612}
>
> Where 0 is a session not saved, for any reason.
good point! we could also put 'undefined'. (thinking in JSON format,
as we store a string)
>
> Gonzalo
>
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
--
.. manuq ..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Time spent on activity (was Best time format for logging?)
2014-03-28 8:27 GMT-03:00 Martin Abente : > As long as we don't expect to have a 1-to-1 relation between the new "spent > times per session" and launch times I think it will be fine. > > We have to make sure everyone understand this will not be 100% reliable. We > might loose some of these spent times when the laptop or activity crashes, > activities could be left opened for hours etc, but, I don't think we should > be worried in the practice. As Walter said, is still better than nothing. Yes, we should make this very clear. > I see benefit in both approaches, and I guess they are not mutually > exclusive: > > One Big Sum: it could be interesting to use this information to sort > entries in the journal ie., "sort entries by spent time", so it would be > good to have that info already processed, it could have some value. > > Series: the benefit of having this split as series instead of just one big > sum, is that it could give extra information about the time its being spent > on each "session" individually. Yeah. And from a statistics POV, is a matter of what do you want to know from the data. If the level of detail matters or not. Same thing as with the seconds vs microseconds discussion. > Regarding harvest, we can carefully drop that placeholder, and add a new > table for storing these times, if needed. Yes, I became familiar with the migrate tool already in my "log sessions" branch. > > On Fri, Mar 28, 2014 at 6:53 AM, Walter Bender > wrote: >> >> Sorry for chiming in late. I was indespoised yesterday. >> >> I think there is no harm in gathering the data as a series. If we have >> missing elements due to crashes, etc., it is still better than >> nothing. Originally, I was thinking of adding something in the same >> place where we trigger write_file so that we accumulated data each >> time the activity was in the background or closed (a bit more robust) >> but honestly, I don't think it really matters so much). >> >> >> On Thu, Mar 27, 2014 at 4:02 PM, Gonzalo Odiard >> wrote: >> > >> > >> > >> > On Thu, Mar 27, 2014 at 4:17 PM, Manuel Quiñones >> > wrote: >> >> >> >> 2014-03-27 15:23 GMT-03:00 Gonzalo Odiard : >> >> > Maybe have sense save the spent time as a list too, >> >> > like we do with launch times. >> >> > Looks like a non invasive change, and a good source of information. >> >> >> >> Good point, is the other option I was handling. Is a trivial patch >> >> too: >> >> >> >> https://github.com/manuq/sugar-toolkit-gtk3/pull/8/files >> >> >> >> I think this one is definetely better. >> >> >> >> I was in doubt for two reasons: 1. because unlike launch_time, this >> >> spent-times metadata will not be saved if the activity does not end >> >> properly: could be a crash, a programming error, end of battery, etc. >> >> So the item N of spent-times will not necessarily correspont to item N >> >> of launch-times. >> >> >> > >> > While is true you don't have how much time was spent in every session, >> > the sequence is good data anyway. >> > >> >> >> >> And secondly, because the simpler option satisfies the placeholder >> >> that is currently in Harvest >> >> >> >> >> >> https://github.com/tchx84/harvest-server/blob/master/sql/001-harvest.sql#L24 >> >> >> >> The second one will require a new table in Harvest. But that's an >> >> easy change too. >> > >> > >> > Ok, would be good have tch involved then. >> > >> >> >> >> >> >> Side note: I see we have a horrible mix of styles in metadata, some >> >> names use underscore (title_set_by_user, activity_id) and some use >> >> minus character (share-scope, icon-color, launch-times). Does anyone >> >> know the preferred style? >> >> >> > >> > No idea about that >> >> This has always bothered me, but I am not sure how we address it >> without breaking lots of code. >> >> > >> > Gonzalo >> >> -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 > -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Time spent on activity (was Best time format for logging?)
2014-03-28 7:53 GMT-03:00 Walter Bender : > Sorry for chiming in late. I was indespoised yesterday. > > I think there is no harm in gathering the data as a series. If we have > missing elements due to crashes, etc., it is still better than > nothing. Originally, I was thinking of adding something in the same > place where we trigger write_file so that we accumulated data each > time the activity was in the background or closed (a bit more robust) > but honestly, I don't think it really matters so much). I was thinking about that too: another option is to connect to the window 'active' property [1] to count only the time the user is actually using the activity. And not count when she/he goes for a moment to the Network view or to the Journal, for example. [1] https://developer.gnome.org/gtk3/stable/GtkWindow.html#GtkWindow--is-active > On Thu, Mar 27, 2014 at 4:02 PM, Gonzalo Odiard wrote: >> >> >> >> On Thu, Mar 27, 2014 at 4:17 PM, Manuel Quiñones wrote: >>> >>> 2014-03-27 15:23 GMT-03:00 Gonzalo Odiard : >>> > Maybe have sense save the spent time as a list too, >>> > like we do with launch times. >>> > Looks like a non invasive change, and a good source of information. >>> >>> Good point, is the other option I was handling. Is a trivial patch too: >>> >>> https://github.com/manuq/sugar-toolkit-gtk3/pull/8/files >>> >>> I think this one is definetely better. >>> >>> I was in doubt for two reasons: 1. because unlike launch_time, this >>> spent-times metadata will not be saved if the activity does not end >>> properly: could be a crash, a programming error, end of battery, etc. >>> So the item N of spent-times will not necessarily correspont to item N >>> of launch-times. >>> >> >> While is true you don't have how much time was spent in every session, >> the sequence is good data anyway. >> >>> >>> And secondly, because the simpler option satisfies the placeholder >>> that is currently in Harvest >>> >>> https://github.com/tchx84/harvest-server/blob/master/sql/001-harvest.sql#L24 >>> >>> The second one will require a new table in Harvest. But that's an >>> easy change too. >> >> >> Ok, would be good have tch involved then. >> >>> >>> >>> Side note: I see we have a horrible mix of styles in metadata, some >>> names use underscore (title_set_by_user, activity_id) and some use >>> minus character (share-scope, icon-color, launch-times). Does anyone >>> know the preferred style? >>> >> >> No idea about that > > This has always bothered me, but I am not sure how we address it > without breaking lots of code. Yeah, but I think we should decide what to do or recommend from now on for the toolkit keywords. Activities are able to do whatever they want, of course. >> >> Gonzalo > > -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 -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Time spent on activity (was Best time format for logging?)
2014-03-27 15:23 GMT-03:00 Gonzalo Odiard : > Maybe have sense save the spent time as a list too, > like we do with launch times. > Looks like a non invasive change, and a good source of information. Good point, is the other option I was handling. Is a trivial patch too: https://github.com/manuq/sugar-toolkit-gtk3/pull/8/files I think this one is definetely better. I was in doubt for two reasons: 1. because unlike launch_time, this spent-times metadata will not be saved if the activity does not end properly: could be a crash, a programming error, end of battery, etc. So the item N of spent-times will not necessarily correspont to item N of launch-times. And secondly, because the simpler option satisfies the placeholder that is currently in Harvest https://github.com/tchx84/harvest-server/blob/master/sql/001-harvest.sql#L24 The second one will require a new table in Harvest. But that's an easy change too. Side note: I see we have a horrible mix of styles in metadata, some names use underscore (title_set_by_user, activity_id) and some use minus character (share-scope, icon-color, launch-times). Does anyone know the preferred style? Thanks for the comments. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Time spent on activity (was Best time format for logging?)
Hi Walter, 2014-02-28 11:12 GMT-03:00 Walter Bender : > It seems time on activity is an oft-requested feature. IMHO, we should > maintain those data in the activity instance metadata like we do > launch times et al. Should be a fairly straight-forward patch. what do you think? https://github.com/manuq/sugar-toolkit-gtk3/pull/7/files the PR is against my own repository because github is not giving me a way to compare with sugarlabs toolkit, I need to sort that out. In the meanwhile, I would like to know your opinion. > > (My rationale is that making it part of the activity metadata, it is > accessible to the Sugar user -- part of the effort to "make learning > visible" to the learner, not just the administrator.) > > -walter -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New method for Activity class to send notifications
2014-03-26 19:23 GMT-03:00 Martin Abente : > notify_user sounds good to me :) Same to me, notify_user fits best. I meant to add my comment below that one, sorry. > > > On Wed, Mar 26, 2014 at 5:36 PM, Manuel Quiñones wrote: >> >> 2014-03-26 18:12 GMT-03:00 James Cameron : >> > On Wed, Mar 26, 2014 at 09:40:41AM -0300, Martin Abente wrote: >> >> His work is almost done [2,3,4], but it introduces a new method to >> >> the base Activity class, therefore I wanted your opinions regarding >> >> the name of this method, the current options are [4]: >> > >> >> * send_notification >> >> * add_notification >> >> * shell_notify >> >> * sugar_notify >> > >> > "shell_" and "sugar_" prefixes are superfluous given that the base >> > Activity class is already a part of Sugar, and the Shell isn't the >> > eventual target of the notification; the user is. >> > >> > "_notify" and "_notification" are ambiguous, because they don't say >> > what is being notified; the system, the class instance, or the user. >> > >> > "add_" prefix exposes an implementation detail; that notifications are >> > a list. This exposure is unnecessary. >> > >> > Of the ones you listed, "send_notification" fits best. >> >> I agree. Thanks for the detailed comments on each proposal. >> >> > >> > Of the ones you didn't list, "notify_user" would be best. >> > >> > "sugar_shell_add_notification_and_send_to_user" would be the worst. >> > >> > -- >> > James Cameron >> > http://quozl.linux.org.au/ >> > ___ >> > Sugar-devel mailing list >> > Sugar-devel@lists.sugarlabs.org >> > http://lists.sugarlabs.org/listinfo/sugar-devel >> >> >> >> -- >> .. manuq .. > > > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New method for Activity class to send notifications
2014-03-26 18:12 GMT-03:00 James Cameron : > On Wed, Mar 26, 2014 at 09:40:41AM -0300, Martin Abente wrote: >> His work is almost done [2,3,4], but it introduces a new method to >> the base Activity class, therefore I wanted your opinions regarding >> the name of this method, the current options are [4]: > >> * send_notification >> * add_notification >> * shell_notify >> * sugar_notify > > "shell_" and "sugar_" prefixes are superfluous given that the base > Activity class is already a part of Sugar, and the Shell isn't the > eventual target of the notification; the user is. > > "_notify" and "_notification" are ambiguous, because they don't say > what is being notified; the system, the class instance, or the user. > > "add_" prefix exposes an implementation detail; that notifications are > a list. This exposure is unnecessary. > > Of the ones you listed, "send_notification" fits best. I agree. Thanks for the detailed comments on each proposal. > > Of the ones you didn't list, "notify_user" would be best. > > "sugar_shell_add_notification_and_send_to_user" would be the worst. > > -- > James Cameron > http://quozl.linux.org.au/ > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Several toolbars in a sugar web activity ?
2014-03-22 17:55 GMT-03:00 laurent bernabe : > Hello, > > thank you. So I'll have a look at Palette Activity and try to use palettes > in my code. > > (Where is the ActivityPalette code hosted ? I've looked at > http://wiki.sugarlabs.org/go/Activities, but it has no reference on the > ActivityPalette). https://github.com/sugarlabs/sugar-web/blob/master/graphics/activitypalette.js -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Several toolbars in a sugar web activity ?
hi laurent, lionel and i discussed secondary toolbars a while ago. we agreed in not implement them for web because we think that palettes are more convenient. in web you can easily make any kind of palette. just inherit Palette like ActivityPalette does. also secondary toolbars make the activity main area [1] change its height when it appears and dissapears, and i find that very problematic. [1] named canvas, not to confuse with html tag 2014-03-22 17:28 GMT-03:00 laurent bernabe : > I've just realised that I can do without a 3rd toolbar : > > ___ > Theme_Lesson or Them_Exercice => T1_LEsson, T1_exercice, T2_lesson ... > | > Piece_kind => pawn, knight ... king > ___ > > That way I can save a toolbar :). > > I still have to find what is the best way to handle the second toolbar and > its dynamic content. > > Regards > > > 2014-03-22 21:24 GMT+01:00 laurent bernabe : > >> Hello, >> >> thank you for your answer and your idea. >> >> So I can add, for example, 10 versions of the toolbar overlapping just >> below the main-toolbar, and to show only one toolbar (or zero) at one time. >> Or maybe, my idea is the wrong way to do ? >> >> As for the third dynamic toolbar, I am still wondering why Gonzola Odiard >> said that it is probably a bad idea by design. >> >> Indeed, I would like to split the learning in 4 steps, then in each step, >> there is a kind of piece to choose in the second toolbar : and the third is >> choosing either a lesson or an exercice. >> >> Theme >> | >> Piece >> | >> Lesson or exercice >> >> >> Regards >> >> >> 2014-03-22 21:13 GMT+01:00 Sam Parkinson : >>> >>> Hi, >>> >>> Couldn't you just create another toolbar div and .show and .hide when >>> needed? >>> >>> Sam >>> >>> On Mar 23, 2014 6:01 AM, "laurent bernabe" >>> wrote: Thank you for your answer. So I'll try to do without them. Regards 2014-03-22 19:59 GMT+01:00 Gonzalo Odiard : > > Sugar implement a primary and a secondary toolbar, attached to a > button. > You can't add a third. And by design is probably a bad idea. > I think in the web activities, the secondary toolbars are not > implemented yet. > > Gonzalo > > > On Sat, Mar 22, 2014 at 8:22 AM, laurent bernabe > wrote: >> >> Hello everyone, >> >> I saw that a Python activity, Turtle art, has two toolbars (a main >> toolbar, and a personalized toolbar just below, which content is set by >> the >> selection of the main toolbar). I would like to do something like this >> inside my LearningChess activity : >> >> Is this easy to do in sugar web activity ? >> Can I even go further : I mean use three toolbars instead of 2 (one >> main toolbar, the second rely on the choice of the main toolbar, and the >> third on the choice of the second) ? >> Is my second request suitable for an Android adaptation ? (As I know >> there are experimentations in order to port standard activities to >> Android). >> >> >> Regards >> >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> > > > > -- > Gonzalo Odiard > > SugarLabs - Learning Software for children ___ 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 > -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] mic settings
2014-03-21 14:43 GMT-03:00 Walter Bender : > On Fri, Mar 21, 2014 at 8:14 AM, Manuel Quiñones wrote: >> 2014-03-20 22:45 GMT-03:00 Walter Bender : >>> Gonzalo: what do you think of: >>> http://wiki.sugarlabs.org/go/File:MicLevels.png ? >>> >>> I am not 100% conmvinced about the halo around the mute buttons. Manuq? >> >> please try if you can make it dissapear with: >> >> button.props.relief = Gtk.ReliefStyle.NONE >> button.props.focus_on_click = False >> >> is what Browse does for the Add Tab button. > > Latest is at http://wiki.sugarlabs.org/go/File:MicLevels.png > > The grey line at the bottom seems to be an artifact of sugar-build; it > is on the speech device too. no sugar-build but latest gtk, we have to fix the theme for latest gtk. > Manuq's suggestion (above) removed the halos but they reappear as soon > as I click the buttons. yes, having feedback when you tap or click is a feature. > >> >>> >>> -walter >>> >>> On Thu, Mar 20, 2014 at 8:03 PM, Gonzalo Odiard >>> wrote: >>>> Could be the mute button horizontally aligned with the slider? >>>> Probably the Mute label is not needed. >>>> >>>> Gonzalo >>>> >>>> >>>> On Thu, Mar 20, 2014 at 8:45 PM, Walter Bender >>>> wrote: >>>>> >>>>> OK. I need to do a tiny bit more cleaning up of the patch. Thanks for >>>>> all the feedback. >>>>> >>>>> -walter >>>>> >>>>> On Thu, Mar 20, 2014 at 7:41 PM, Manuel Quiñones wrote: >>>>> > perfect! >>>>> > >>>>> > 2014-03-20 20:32 GMT-03:00 Walter Bender : >>>>> >> Please take a look at http://wiki.sugarlabs.org/go/File:MicLevels.png >>>>> >> (I updated the image) >>>>> >> >>>>> >> -walter >>>>> >> >>>>> >> On Thu, Mar 20, 2014 at 7:00 PM, Walter Bender >>>>> >> wrote: >>>>> >>> Thanks. Looks good. I'll give it a go tonight. >>>>> >>> >>>>> >>> -walter >>>>> >>> >>>>> >>> On Thu, Mar 20, 2014 at 6:58 PM, Manuel Quiñones >>>>> >>> wrote: >>>>> >>>> hey walter, >>>>> >>>> >>>>> >>>> this is what I came up with: >>>>> >>>> >>>>> >>>> http://sugarlabs.org/~manuq/sound.jpg >>>>> >>>> >>>>> >>>> somewhat similar to your current implementation: >>>>> >>>> >>>>> >>>> http://wiki.sugarlabs.org/go/File:MicLevels.png >>>>> >>>> >>>>> >>>> I'm afraid we don't have GtkSwitch widget themed for Sugar so we >>>>> >>>> don't >>>>> >>>> have other option than leave two more rows for each "Mute". >>>>> >>>> >>>>> >>>> - the palette can be larger in width, same width than the Speech >>>>> >>>> palette >>>>> >>>> - if possible, center the titles "Microphone" and "Speaker" like >>>>> >>>> Speech palette does for Tone and Velocity >>>>> >>>> - remove separators between Mute and the GtkScale. >>>>> >>>> >>>>> >>>> -- >>>>> >>>> .. manuq .. >>>>> >>> >>>>> >>> >>>>> >>> >>>>> >>> -- >>>>> >>> Walter Bender >>>>> >>> Sugar Labs >>>>> >>> http://www.sugarlabs.org >>>>> >> >>>>> >> >>>>> >> >>>>> >> -- >>>>> >> Walter Bender >>>>> >> Sugar Labs >>>>> >> http://www.sugarlabs.org >>>>> >> ___ >>>>> >> Sugar-devel mailing list >>>>> >> Sugar-devel@lists.sugarlabs.org >>>>> >> http://lists.sugarlabs.org/listinfo/sugar-devel >>>>> > >>>>> > >>>>> > >>>>> > -- >>>>> > .. manuq .. >>>>> >>>>> >>>>> >>>>> -- >>>>> Walter Bender >>>>> Sugar Labs >>>>> http://www.sugarlabs.org >>>>> ___ >>>>> Sugar-devel mailing list >>>>> Sugar-devel@lists.sugarlabs.org >>>>> http://lists.sugarlabs.org/listinfo/sugar-devel >>>> >>>> >>>> >>>> >>>> -- >>>> Gonzalo Odiard >>>> >>>> SugarLabs - Learning Software for children >>> >>> >>> >>> -- >>> Walter Bender >>> Sugar Labs >>> http://www.sugarlabs.org >>> ___ >>> Sugar-devel mailing list >>> Sugar-devel@lists.sugarlabs.org >>> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> >> >> -- >> .. manuq .. > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] mic settings
2014-03-20 22:45 GMT-03:00 Walter Bender : > Gonzalo: what do you think of: > http://wiki.sugarlabs.org/go/File:MicLevels.png ? > > I am not 100% conmvinced about the halo around the mute buttons. Manuq? please try if you can make it dissapear with: button.props.relief = Gtk.ReliefStyle.NONE button.props.focus_on_click = False is what Browse does for the Add Tab button. > > -walter > > On Thu, Mar 20, 2014 at 8:03 PM, Gonzalo Odiard wrote: >> Could be the mute button horizontally aligned with the slider? >> Probably the Mute label is not needed. >> >> Gonzalo >> >> >> On Thu, Mar 20, 2014 at 8:45 PM, Walter Bender >> wrote: >>> >>> OK. I need to do a tiny bit more cleaning up of the patch. Thanks for >>> all the feedback. >>> >>> -walter >>> >>> On Thu, Mar 20, 2014 at 7:41 PM, Manuel Quiñones wrote: >>> > perfect! >>> > >>> > 2014-03-20 20:32 GMT-03:00 Walter Bender : >>> >> Please take a look at http://wiki.sugarlabs.org/go/File:MicLevels.png >>> >> (I updated the image) >>> >> >>> >> -walter >>> >> >>> >> On Thu, Mar 20, 2014 at 7:00 PM, Walter Bender >>> >> wrote: >>> >>> Thanks. Looks good. I'll give it a go tonight. >>> >>> >>> >>> -walter >>> >>> >>> >>> On Thu, Mar 20, 2014 at 6:58 PM, Manuel Quiñones >>> >>> wrote: >>> >>>> hey walter, >>> >>>> >>> >>>> this is what I came up with: >>> >>>> >>> >>>> http://sugarlabs.org/~manuq/sound.jpg >>> >>>> >>> >>>> somewhat similar to your current implementation: >>> >>>> >>> >>>> http://wiki.sugarlabs.org/go/File:MicLevels.png >>> >>>> >>> >>>> I'm afraid we don't have GtkSwitch widget themed for Sugar so we >>> >>>> don't >>> >>>> have other option than leave two more rows for each "Mute". >>> >>>> >>> >>>> - the palette can be larger in width, same width than the Speech >>> >>>> palette >>> >>>> - if possible, center the titles "Microphone" and "Speaker" like >>> >>>> Speech palette does for Tone and Velocity >>> >>>> - remove separators between Mute and the GtkScale. >>> >>>> >>> >>>> -- >>> >>>> .. manuq .. >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> Walter Bender >>> >>> Sugar Labs >>> >>> http://www.sugarlabs.org >>> >> >>> >> >>> >> >>> >> -- >>> >> Walter Bender >>> >> Sugar Labs >>> >> http://www.sugarlabs.org >>> >> ___ >>> >> Sugar-devel mailing list >>> >> Sugar-devel@lists.sugarlabs.org >>> >> http://lists.sugarlabs.org/listinfo/sugar-devel >>> > >>> > >>> > >>> > -- >>> > .. manuq .. >>> >>> >>> >>> -- >>> Walter Bender >>> Sugar Labs >>> http://www.sugarlabs.org >>> ___ >>> Sugar-devel mailing list >>> Sugar-devel@lists.sugarlabs.org >>> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> >> >> >> -- >> Gonzalo Odiard >> >> SugarLabs - Learning Software for children > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] mic settings
perfect! 2014-03-20 20:32 GMT-03:00 Walter Bender : > Please take a look at http://wiki.sugarlabs.org/go/File:MicLevels.png > (I updated the image) > > -walter > > On Thu, Mar 20, 2014 at 7:00 PM, Walter Bender > wrote: >> Thanks. Looks good. I'll give it a go tonight. >> >> -walter >> >> On Thu, Mar 20, 2014 at 6:58 PM, Manuel Quiñones wrote: >>> hey walter, >>> >>> this is what I came up with: >>> >>> http://sugarlabs.org/~manuq/sound.jpg >>> >>> somewhat similar to your current implementation: >>> >>> http://wiki.sugarlabs.org/go/File:MicLevels.png >>> >>> I'm afraid we don't have GtkSwitch widget themed for Sugar so we don't >>> have other option than leave two more rows for each "Mute". >>> >>> - the palette can be larger in width, same width than the Speech palette >>> - if possible, center the titles "Microphone" and "Speaker" like >>> Speech palette does for Tone and Velocity >>> - remove separators between Mute and the GtkScale. >>> >>> -- >>> .. manuq .. >> >> >> >> -- >> Walter Bender >> Sugar Labs >> http://www.sugarlabs.org > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [DESIGN] mic settings
hey walter, this is what I came up with: http://sugarlabs.org/~manuq/sound.jpg somewhat similar to your current implementation: http://wiki.sugarlabs.org/go/File:MicLevels.png I'm afraid we don't have GtkSwitch widget themed for Sugar so we don't have other option than leave two more rows for each "Mute". - the palette can be larger in width, same width than the Speech palette - if possible, center the titles "Microphone" and "Speaker" like Speech palette does for Tone and Velocity - remove separators between Mute and the GtkScale. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] GSoC'14 Proposal: Turtle Art 3D
hey sam, 2014-03-20 17:07 GMT-03:00 Sam Parkinson : > Hi Manuel, > > Three.is would be nice but GTKWebKit does not yet support it, doesn't it > need webgl? ( Why didn't we just stay with geko Geko even supports > webrtc! ) It says it is work in progress on their home page. yes and no :) 1. threejs has canvas as backend too, so if you are not doing anything too shiny (raytracing, bump mapping), you are fine with canvas 2. i think sugar-web should look forward to work on any standard browser. I saw webgl working in webkitgtk2 http://www.youtube.com/watch?v=pKO5EhVfPi0 > > Sam > > On Mar 21, 2014 4:14 AM, "Manuel Quiñones" wrote: >> >> 2014-03-20 11:48 GMT-03:00 Anubhav Jaiswal : >> > >> > Dear All, >> > >> > I have drafted my GSoC 2014 proposal for the project : Turtle Art 3D >> > >> > http://wiki.sugarlabs.org/go/Summer_of_Code/2014/AnubhavJ/Turtle_Art_3D >> > >> > There's also a prototype that I created implementing the basic functions >> > of Turtle Art 3D: >> > https://github.com/Anubhav-J/TA3D >> > >> > It would be great to hear some feedback and comments on the proposal as >> > well as ideas on improving the prototype from the community. >> >> Great! I had to install PyOpenGL in order to run it (in Fedora, sudo >> yum install PyOpenGL). >> >> I think the prototype can gain a lot if you allow the user to move the >> camera. Maybe make the camera rotate around the center of coordinates >> when the user moves the mouse or does touch&drag on the screen. That >> is called "trackball camera" in some projects like ThreeJS. >> >> i'm very tempted to do a port in JS and ThreeJS :) By the way have >> you considered those technologies plus sugar-web for the project? >> >> -- >> .. manuq .. >> ___ >> 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 > -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [pull request] Re: Better support for running non-sugar apps under Sugar
that's the spirit! looking fine, I just did two minor comments in the PRs that could improve the patch. cheers, 2014-03-20 15:40 GMT-03:00 Sebastian Silva : > Hi > The intention of this email was actually to raise a discussion about ways > that Sugar could better > integrate with the rest of the GNU+Linux ecosystem. > > Anyhow, Walter's answer was: Show me the code, so here it is: > https://github.com/sugarlabs/sugar/pull/283 > https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/122 > > This only covers point (1) in my plan: Try to use X11 window icons for > generic applications in activities tray. > This already makes it quite nice when launching apps from the terminal. > > Implementation-wise, It calculates padding in relation to > style.STANDARD_ICON_SIZE, therefore it works both with SUGAR_SCALING at 100 > and 72. > > Attached is a small png of the result. > > This solves the 1 issue for using X11 apps in Sugar. > Do you think it could make it into 0.102 timeline? > > In the future I hope we will be able to add some sort of .desktop launcher > file support. > > I'm excited that this is my first real contribution to the shell/toolkit > space that I think might get merged, please be gentle when reviewing. :-) > > Regards, > Sebastian > > > El mié, 12 de mar 2014 a las 8:11 AM, Walter Bender > escribió: > > On Tue, Mar 11, 2014 at 7:34 PM, Sebastian Silva > wrote: > > I know this topic has been discussed here more than once. I feel there is a > resistance because of a "purity" of design. > > I feel there is a resistance because no one has written the patch. (Patches > welcome). > > However it's a bit silly that we need to reinvent everything because we have > a thing for simplicity. For instance I'm doing a workshop with children and > I'd have liked to use "aseprite", a pixel art design program that has > everything I need and a simple interface. Paint activity isn't quite apt for > the job. So I guess I can contribute to define what I mean: 1. Support > Freedesktop.Org Icon specification and icon naming conventions for non-sugar > applications, instead of the grey dot in the Frame. 2. Support > Freedesktop.Org Desktop Entry specification for launching non-sugar > applications. Proposal: use ~/.sugar/launchers/ for .desktop files. These > would appear in the Home View, much like Activities do. I know we are in > Feature Freeze but I only want to propose and discuss the merits of the > feature, so maybe I or others can invest the time required to achieve this > for the next release. Regards, Sebastian PS: Extra points for sugarizing > aseprite, it's really cool: http://www.aseprite.org/ . Hints and pointers on > where to begin are also welcome. > ___ 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 > -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] GSoC'14 Proposal: Turtle Art 3D
2014-03-20 11:48 GMT-03:00 Anubhav Jaiswal : > > Dear All, > > I have drafted my GSoC 2014 proposal for the project : Turtle Art 3D > > http://wiki.sugarlabs.org/go/Summer_of_Code/2014/AnubhavJ/Turtle_Art_3D > > There's also a prototype that I created implementing the basic functions of > Turtle Art 3D: > https://github.com/Anubhav-J/TA3D > > It would be great to hear some feedback and comments on the proposal as well > as ideas on improving the prototype from the community. Great! I had to install PyOpenGL in order to run it (in Fedora, sudo yum install PyOpenGL). I think the prototype can gain a lot if you allow the user to move the camera. Maybe make the camera rotate around the center of coordinates when the user moves the mouse or does touch&drag on the screen. That is called "trackball camera" in some projects like ThreeJS. i'm very tempted to do a port in JS and ThreeJS :) By the way have you considered those technologies plus sugar-web for the project? -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] sugar-build, can't perform check
i can confirm that smoketest fails if Sugar is set to Spanish. i set it to English and the test passes now. 2014-03-19 15:45 GMT-03:00 Manuel Quiñones : > attached. > > thanks, > > 2014-03-18 20:19 GMT-03:00 Daniel Narvaez : >> Can you post the logs please? >> >> >> On Tuesday, 18 March 2014, Manuel Quiñones wrote: >>> >>> hi, >>> >>> i created a fresh dev environment today, and after that ./osbuild >>> check fails with the following output: >>> >>> >>> [manuq@localhost sugar-build]$ ./osbuild check >>> >>> $ sudo broot run osbuild check >>> [sudo] password for manuq: >>> >>> = Building = >>> >>> * Building sugar >>> >>> = Check = >>> >>> * Running smoke test >>> >>> 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 >>> Initializing built-in extension GLX >>> screen 0 shmid 11370507 >>> xinit: XFree86_VT property unexpectedly has 0 items instead of 1 >>> Xlib: extension "RANDR" missing on display ":99". >>> 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 >>> xinit: connection to X server lost >>> >>> >>> ! Failed to run command check >>> Killing 10715 >>> >>> ! Failed to run command check >>> [manuq@localhost sugar-build]$ >>> >>> >>> -- >>> .. manuq .. >>> ___ >>> Sugar-devel mailing list >>> Sugar-devel@lists.sugarlabs.org >>> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> >> >> -- >> Daniel Narvaez >> >> >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> > > > > -- > .. manuq .. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] sugar-build, can't perform check
hi, i created a fresh dev environment today, and after that ./osbuild check fails with the following output: [manuq@localhost sugar-build]$ ./osbuild check $ sudo broot run osbuild check [sudo] password for manuq: = Building = * Building sugar = Check = * Running smoke test 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 Initializing built-in extension GLX screen 0 shmid 11370507 xinit: XFree86_VT property unexpectedly has 0 items instead of 1 Xlib: extension "RANDR" missing on display ":99". 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 xinit: connection to X server lost ! Failed to run command check Killing 10715 ! Failed to run command check [manuq@localhost sugar-build]$ -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Feature freeze
in my humble opinion, I would also like to see the feature freeze delayed. several features are almost done. I see our community is still rearranging, and we need to put more effort in reviews. considering the load of PRs, we should embrace pair-reviewing. 2014-03-09 22:25 GMT-03:00 Daniel Narvaez : > On 10 March 2014 01:48, Gonzalo Odiard wrote: >> >> >> >> On Sun, Mar 9, 2014 at 9:40 PM, Daniel Narvaez >> wrote: >>> >>> For what it's worth it would be a -1 from me. I would be fine to delay a >>> bit to fix important bugs, but not to add more features, it seems to go >>> completely against the rationale of time based releases. But that's just my >>> opinion. >>> >> >> Would be against the time based release, if the propose would be postpone >> it indefinitely. > > > I disagree. From https://wiki.gnome.org/ReleasePlanning/TimeBased > > -- > > Although we agree on rough aims for each major release, and attempt to > achieve those aims, GNOME releases are time-based rather than feature-based. > A roughly 6-month release cycle allows us to coordinate development of the > features that have actually been implemented, allowing us to maintain the > quality of the overall release without delaying everything because of one or > two features. If a feature is not ready in time then the developers must not > wait long to put it in the next major release. We have found that this > encourages both high quality and rapid development compared to feature-based > release schedules. > > -- > > IMO delaying feature freeze is very clearly against that definition, in many > ways. > >> >> Many projects working with time based releases, like libreoffice, gnome or >> fedora >> adjust the schedules if they consider worth it. > > > I honestly don't remember any of these projects making a decision to delay > *feature* freeze two weeks after the deadline. I could be wrong of course, I > have not followed every single releases of them. > > More importantly, even if they did, it wouldn't mean their decision was > consistent with the time based release schedule rationale. Sometimes it's > worth to make compromises. > > To articulate my point a bit more > > 1 Delaying feature freeze after the deadline is obviously against time based > release definition and rationale. > 2 I don't see anything special with the current situation that would suggest > we should compromise on our time based approach. > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar 0.101.3 (unstable)
We recently added a Release Notes section in developer.sugarlabs.org :-) http://developer.sugarlabs.org/release-notes/102.md.html We agreed to add the deprecations notes there. 2014-03-09 21:10 GMT-03:00 Walter Bender : > It didn't take me too long to pull together > http://wiki.sugarlabs.org/go/0.102/Notes and I am happy to do the same > again for the other unstable releases. We need to do some more work > for the stable release as per Gonzalo's comments. > > -walter > > On Sun, Mar 9, 2014 at 8:04 PM, Daniel Narvaez wrote: >> The discussion started because Peter would like to have release notes for >> unstable releases. (Though he might be content with those being just the git >> logs). >> >> >> On 10 March 2014 01:01, Gonzalo Odiard wrote: >>> >>> I am not thinking in doing it for every unstable release, just for 0.102. >>> I already did it for 0.100, I can volunteer to do it again in 0.102 >>> >>> Gonzalo >>> >>> >>> On Sun, Mar 9, 2014 at 8:58 PM, Daniel Narvaez >>> wrote: The thing is, I don't have time to do that manually for each unstable release. We either need a volunteer to do it or a way to generate it automatically from the log (which was the goal of my suggestion). On 10 March 2014 00:56, Gonzalo Odiard wrote: > > In the end, we need a summary to the end public, we can prepare it like > in the past, > based in the commit messages. > > Gonzalo > > > On Sun, Mar 9, 2014 at 8:41 PM, Daniel Narvaez > wrote: >> >> On 9 March 2014 22:31, Gaurav Parida wrote: >>> >>> Keeping the commit messages, will help in knowing the changes done in >>> a release. The documentation aspect of a new release will be easily >>> handled. >>> +1 for the idea. >>> >>> On Mon, Mar 10, 2014 at 2:35 AM, Walter Bender >>> wrote: Just as a rough sketch of what pulling the commit messages would look like, I've set up http://wiki.sugarlabs.org/go/0.102/Notes -walter >>> The mockups look good. It would be great if each one them also has the >>> link to the merge request. >>> >>> In my opinion, the commit messages will be more understandable, if we >>> put some guidelines for them. >>> like preappend the commit messages with with [Feature] / [Bug Fix >>> #] / [Defect] / [Upgrade] from now on... >> >> >> We could include in the release notes only the subject of commits >> tagged like that. That would avoid to have too many irrelevant >> implementation details in the notes and also to simply omit commits that >> are >> not relevant (like refactorings etc). >> >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> > > > > -- > Gonzalo Odiard > > SugarLabs - Learning Software for children -- Daniel Narvaez >>> >>> >>> >>> >>> -- >>> Gonzalo Odiard >>> >>> SugarLabs - Learning Software for children >> >> >> >> >> -- >> Daniel Narvaez > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Calling async callbacks always async
2014-03-10 8:18 GMT-03:00 Daniel Narvaez : > Hello, > > Code pointed out a good explanation of why we should be always calling async > callbacks async in sugar-web. We have been doing it, but I was never able to > produce good rationale/example for it :) > > http://blog.osteele.com/posts/2008/04/minimizing-code-paths-in-asychronous-code.html good post. we should also prevent going too deep on callbacks nesting, also known as "callback hell" or "christmas tree". http://callbackhell.com/ this is a library that helps with async handling: https://github.com/caolan/async a very different approach to async is with promises, here is a recent post about them: http://dailyjs.com/2014/02/20/promises-in-detail/ Side note, I am looking at data-binding and observable variables to get inspiration for web UI http://www.ractivejs.org/ http://js.jidesoft.com/ -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] webaccounts panel
Much better! Some feedback: Current label is "configure your web services". I think "web services" is better. "your" seems wrong person, because we use first person in other sections: "about me" "my computer". You should highlight the icon for the selected account. In this case Facebook icon should be highlighted: http://people.sugarlabs.org/walter/Screenshot%20of%20_WebAccounts_.png In Sugar, icons are usually highlighted with a round grey background. 2014-03-08 11:09 GMT-03:00 Walter Bender : > On Sat, Mar 8, 2014 at 8:18 AM, Gonzalo Odiard wrote: >> emptypanel [1] show a white panel with a icon centered, >> a text and a button. Is used in Read or ImageViewer >> when start without a object, and is similar to the journal >> when is empty. > > OK. But there is not an emptypanel method anywhere in the toolkit. > I've added the icon to the panel [2] in the same spirit as emptypanel > in Read and ImageViewer, but I didn't use your code as (1) it is > overly complicated for this purpose, e.g., I don't need an add button; > and (2) we are migrating over to the use of Gtk.Grid. Yeah, I suggest you just try to mimic the look: grey text, centered paragraph. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar Performance testing
2014-03-09 14:46 GMT-03:00 Daniel Narvaez : > On 9 March 2014 17:53, Sebastian Silva wrote: >> >> Hi dear Sugar developers. >> We have participated in the deployment in Peru of Sugar 0.94 (classic) for >> XO1 and XO1.5. It will be ongoing in 2014 and hopefully we will tighten the >> feedback circle and work closer with upstream (master). >> Now we as a team are working in Colombia with XO1.75 and again, the issue >> of performance creeps in, and they are interested in downgrading to Sugar >> 0.94 (classic). >> "that way madness lies", if we stay without updating, we break cohesion. >> It would be best if we could all just work on the same basis. >> >> For us to base our work on 0.101+ (new) Sugar, we have to make sure we >> have solved the performance issues plaguing (new) Sugar and/or OLPC/OS 13.x. > > > Which OLPC version are you comparing with? In the rest of the answer I'll > call that X.x :) > >> >> >> For this I need your advice. >> >> How do I setup an identical environment for (classic) 0.94 Sugar and (new) >> 0.101+ Sugar? Can I use sugar-build for this, or something else...? > > > On which hardware and on which distribution? > > Anyway it's probably not going to be trivial. So let me suggest an easier > first step. You could test 0.94 activities on the top of OLPC 13.x. If they > perform the same as OLPC X.x then we know the issue is the gtk3 toolkit (no > change was made to the gtk2 toolkit). If they are bad as stock 13.x > activities, then we will know it's something in the system. If it's > something in the middle we will have to come up with a more complicated > strategy. But I think the data we get from this initial testing will be > useful to figure out that strategy. > >> >> How do I profile the session (CPU usage, memory consumption, timing)? > > > For memory I would try this > > https://github.com/pixelb/ps_mem > > For CPU top should be fine, but it depends what exactly you want to test. > For timing I usually just print out time.time intervals from the code :) For Python, you can get profiling information with cProfile http://docs.python.org/2/library/profile.html See the treeviews optimization Gonzalo and I been working on http://wiki.sugarlabs.org/go/Features/Optimize_TreeViews > >> >> Do we have some automated GUI testing? Can I make some? > > > See sugar-build/build/tests/shell.py, you could use something like that to > measure startup time I suppose. Anyway you can use the same kind of code to > click around in activities UI etc. > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] replace combo box on language panel
2014-03-05 16:35 GMT-03:00 Walter Bender : > On Wed, Mar 5, 2014 at 2:29 PM, Manuel Quiñones wrote: >> 2014-03-05 15:49 GMT-03:00 Walter Bender : >>> On Wed, Mar 5, 2014 at 8:01 AM, Manuel Quiñones wrote: >>>> 2014-03-05 9:58 GMT-03:00 Walter Bender : >>>>> Maybe I should not use ellipsis at all for this. >>>>> >>>>> Re Manuq's suggestion to use an invoker, I struggled with that: It >>>>> popped the palette up into a separate window that was not selectable >>>>> :P But I agree, some way to better tie the button and palette together >>>>> visually would be good. I'll play around with some ideas. >>>> >>>> otherwise just remove the palette look (black background, white >>>> foreground) and use a grey border as container (like comments in >>>> journal details) >>>> >>> >>> I am mimicking the look and feel of the Journal now [1]. >> >> Looking great. >> >> What was the rationale behind 4 columns for language and 3 for >> country? The list is longer? Just curious. > > I set the max width for the widget to to be screen width / 2. But I > use few columns if I don't need them. Only a few languages have as > many locale variants as Spanish. > > BTW, I think there is a missing translation somewhere. Only Spanish > doesn't seem to get translated. All the other language names do. (This > is when the language is set to Spanish). I don't think this was a bug > I introduced. might be http://bugs.sugarlabs.org/ticket/4449 > Also, note that I do sort the country names alphabetically. It is not > correct in the illustration. excellent! > > regards. > > -walter >> >>> Code available at [2]. >>> >>> regards. >>> >>> -walter >>> >>> [1] http://wiki.sugarlabs.org/images/5/5a/Language-country.png >>> [2] >>> https://github.com/walterbender/sugar/blob/language-2/extensions/cpsection/language/view.py >>> >>>> somehow we'll find a way :) >>>> >>>>> >>>>> On Wed, Mar 5, 2014 at 7:53 AM, Gonzalo Odiard >>>>> wrote: >>>>>> There are more space in the panel, is possible enlarge the paletted to >>>>>> reduce >>>>>> the number of elipsed Languages/Countries. >>>>>> >>>>>> Also, I found elipsing in the middle less useful than in the end, >>>>>> there are any reason to use it? >>>>>> >>>>>> Gonzalo >>>>>> >>>>>> >>>>>> On Wed, Mar 5, 2014 at 9:43 AM, Manuel Quiñones wrote: >>>>>>> >>>>>>> oh, great! >>>>>>> >>>>>>> 2014-03-04 20:50 GMT-03:00 Walter Bender : >>>>>>> > Made a second pass at this (recall last week I submitted a patch to >>>>>>> > break the crazy long combo box into two separate combo boxes: one for >>>>>>> > language and one for country). Now I have replaced the combo boxes >>>>>>> > with palettes, which are arguably more efficient and easier to use on >>>>>>> > touch. >>>>>>> > >>>>>>> > See >>>>>>> > http://wiki.sugarlabs.org/go/Features/Replace_combo_box_in_language_panel >>>>>>> >>>>>>> beware text being cropped: >>>>>>> >>>>>>> http://sugarlabs.org/~manuq/lang1.png >>>>>>> >>>>>>> much better if it looks more like a sugar palette (just rapid mockup >>>>>>> here): >>>>>>> >>>>>>> http://sugarlabs.org/~manuq/lang2.png >>>>>>> >>>>>>> maybe the palette invoker contains the text label too? >>>>>>> >>>>>>> -- >>>>>>> .. manuq .. >>>>>>> ___ >>>>>>> Sugar-devel mailing list >>>>>>> Sugar-devel@lists.sugarlabs.org >>>>>>> http://lists.sugarlabs.org/listinfo/sugar-devel >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Gonzalo Odiard >>>>>> >>>>>> SugarLabs - Learning Software for children >>>>> >>>>> >>>>> >>>>> -- >>>>> Walter Bender >>>>> Sugar Labs >>>>> http://www.sugarlabs.org >>>>> ___ >>>>> Sugar-devel mailing list >>>>> Sugar-devel@lists.sugarlabs.org >>>>> http://lists.sugarlabs.org/listinfo/sugar-devel >>>> >>>> >>>> >>>> -- >>>> .. manuq .. >>> >>> >>> >>> -- >>> Walter Bender >>> Sugar Labs >>> http://www.sugarlabs.org >>> ___ >>> Sugar-devel mailing list >>> Sugar-devel@lists.sugarlabs.org >>> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> >> >> -- >> .. manuq .. > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] replace combo box on language panel
2014-03-05 15:49 GMT-03:00 Walter Bender : > On Wed, Mar 5, 2014 at 8:01 AM, Manuel Quiñones wrote: >> 2014-03-05 9:58 GMT-03:00 Walter Bender : >>> Maybe I should not use ellipsis at all for this. >>> >>> Re Manuq's suggestion to use an invoker, I struggled with that: It >>> popped the palette up into a separate window that was not selectable >>> :P But I agree, some way to better tie the button and palette together >>> visually would be good. I'll play around with some ideas. >> >> otherwise just remove the palette look (black background, white >> foreground) and use a grey border as container (like comments in >> journal details) >> > > I am mimicking the look and feel of the Journal now [1]. Looking great. What was the rationale behind 4 columns for language and 3 for country? The list is longer? Just curious. > Code available at [2]. > > regards. > > -walter > > [1] http://wiki.sugarlabs.org/images/5/5a/Language-country.png > [2] > https://github.com/walterbender/sugar/blob/language-2/extensions/cpsection/language/view.py > >> somehow we'll find a way :) >> >>> >>> On Wed, Mar 5, 2014 at 7:53 AM, Gonzalo Odiard >>> wrote: >>>> There are more space in the panel, is possible enlarge the paletted to >>>> reduce >>>> the number of elipsed Languages/Countries. >>>> >>>> Also, I found elipsing in the middle less useful than in the end, >>>> there are any reason to use it? >>>> >>>> Gonzalo >>>> >>>> >>>> On Wed, Mar 5, 2014 at 9:43 AM, Manuel Quiñones wrote: >>>>> >>>>> oh, great! >>>>> >>>>> 2014-03-04 20:50 GMT-03:00 Walter Bender : >>>>> > Made a second pass at this (recall last week I submitted a patch to >>>>> > break the crazy long combo box into two separate combo boxes: one for >>>>> > language and one for country). Now I have replaced the combo boxes >>>>> > with palettes, which are arguably more efficient and easier to use on >>>>> > touch. >>>>> > >>>>> > See >>>>> > http://wiki.sugarlabs.org/go/Features/Replace_combo_box_in_language_panel >>>>> >>>>> beware text being cropped: >>>>> >>>>> http://sugarlabs.org/~manuq/lang1.png >>>>> >>>>> much better if it looks more like a sugar palette (just rapid mockup >>>>> here): >>>>> >>>>> http://sugarlabs.org/~manuq/lang2.png >>>>> >>>>> maybe the palette invoker contains the text label too? >>>>> >>>>> -- >>>>> .. manuq .. >>>>> ___ >>>>> Sugar-devel mailing list >>>>> Sugar-devel@lists.sugarlabs.org >>>>> http://lists.sugarlabs.org/listinfo/sugar-devel >>>> >>>> >>>> >>>> >>>> -- >>>> Gonzalo Odiard >>>> >>>> SugarLabs - Learning Software for children >>> >>> >>> >>> -- >>> Walter Bender >>> Sugar Labs >>> http://www.sugarlabs.org >>> ___ >>> Sugar-devel mailing list >>> Sugar-devel@lists.sugarlabs.org >>> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> >> >> -- >> .. manuq .. > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] replace combo box on language panel
2014-03-05 9:58 GMT-03:00 Walter Bender : > Maybe I should not use ellipsis at all for this. > > Re Manuq's suggestion to use an invoker, I struggled with that: It > popped the palette up into a separate window that was not selectable > :P But I agree, some way to better tie the button and palette together > visually would be good. I'll play around with some ideas. otherwise just remove the palette look (black background, white foreground) and use a grey border as container (like comments in journal details) somehow we'll find a way :) > > On Wed, Mar 5, 2014 at 7:53 AM, Gonzalo Odiard wrote: >> There are more space in the panel, is possible enlarge the paletted to >> reduce >> the number of elipsed Languages/Countries. >> >> Also, I found elipsing in the middle less useful than in the end, >> there are any reason to use it? >> >> Gonzalo >> >> >> On Wed, Mar 5, 2014 at 9:43 AM, Manuel Quiñones wrote: >>> >>> oh, great! >>> >>> 2014-03-04 20:50 GMT-03:00 Walter Bender : >>> > Made a second pass at this (recall last week I submitted a patch to >>> > break the crazy long combo box into two separate combo boxes: one for >>> > language and one for country). Now I have replaced the combo boxes >>> > with palettes, which are arguably more efficient and easier to use on >>> > touch. >>> > >>> > See >>> > http://wiki.sugarlabs.org/go/Features/Replace_combo_box_in_language_panel >>> >>> beware text being cropped: >>> >>> http://sugarlabs.org/~manuq/lang1.png >>> >>> much better if it looks more like a sugar palette (just rapid mockup >>> here): >>> >>> http://sugarlabs.org/~manuq/lang2.png >>> >>> maybe the palette invoker contains the text label too? >>> >>> -- >>> .. manuq .. >>> ___ >>> Sugar-devel mailing list >>> Sugar-devel@lists.sugarlabs.org >>> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> >> >> >> -- >> Gonzalo Odiard >> >> SugarLabs - Learning Software for children > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] replace combo box on language panel
oh, great! 2014-03-04 20:50 GMT-03:00 Walter Bender : > Made a second pass at this (recall last week I submitted a patch to > break the crazy long combo box into two separate combo boxes: one for > language and one for country). Now I have replaced the combo boxes > with palettes, which are arguably more efficient and easier to use on > touch. > > See http://wiki.sugarlabs.org/go/Features/Replace_combo_box_in_language_panel beware text being cropped: http://sugarlabs.org/~manuq/lang1.png much better if it looks more like a sugar palette (just rapid mockup here): http://sugarlabs.org/~manuq/lang2.png maybe the palette invoker contains the text label too? -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [DESIGN] Design Meeting, Wednesday 5th, 13:00 UTC
See you there! -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Best time format for logging?
2014-02-28 20:30 GMT-03:00 James Cameron : > On Fri, Feb 28, 2014 at 02:39:41PM -0300, Manuel Quiñones wrote: >> date +%s.%N >> 1393609027.074597846 > > Yes, this is adequate, though sometimes the fractional value can be > imprecise as it depends on many factors. > > For response times, it is useful, but care should be taken to record > the value in the most primitive form and do the conversion to text > some other time, otherwise the measurement can affect the result. > > For the case in olpc-utils you change in your patch, use the %s format > character. You don't need higher resolution for that use case. > > The epoch time is the most useful, as it is independent of time zone > configuration on the system. > > In the case of your code, you can optimise it to avoid creating a > process to exec /bin/date, by using printf in bash: > > printf 'START_SUGAR %(%s)T\n' -1 >> $HOME/.olpc-launch-stats > > If you use -2 instead of -1, you will get the time the olpc-session > process started, rather than the current time. Oh, I see, great! Thanks for the valuable information, James. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] language section in control panel
2014-02-28 20:18 GMT-03:00 Walter Bender : > Wednesday is mostly good. Just busy from 15:00-17:00 EST Is that 20 - 22 UTC? Or you are under daylight savings? What about 1 hour meeting starting at 13 UTC? > > -walter > > On Fri, Feb 28, 2014 at 6:15 PM, Manuel Quiñones wrote: >> 2014-02-28 19:30 GMT-03:00 Walter Bender : >>> >>> Just FYI, I've done some refactoring of the language control panel in >>> an attempt to make it a bit easier to navigate [1]. So far, I've >>> pulled out the country into a separate combo box from the language >>> itself. The idea is to search for language and then refine the search >>> by country. This reduces the length of the initial search >>> significantly as many languages have many country-specific codes. >>> However, the language list is still really unwieldy. I am going to >>> replace the combo boxes with palettes in a manner similar to what I >>> did with the journal search filters [2]. Stay tuned. >>> >>> [1] >>> https://github.com/walterbender/sugar/commit/59d09d6dde042dee60c4d744b45b76270f025cba >>> [2] https://github.com/sugarlabs/sugar/pull/265 >> >> Excellent! Let's do a design meeting next week. Monday and Tuesday >> are holidays here for carnival. Is Wednesday fine for you? >> >> -- >> .. manuq .. > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] language section in control panel
2014-02-28 19:30 GMT-03:00 Walter Bender : > > Just FYI, I've done some refactoring of the language control panel in > an attempt to make it a bit easier to navigate [1]. So far, I've > pulled out the country into a separate combo box from the language > itself. The idea is to search for language and then refine the search > by country. This reduces the length of the initial search > significantly as many languages have many country-specific codes. > However, the language list is still really unwieldy. I am going to > replace the combo boxes with palettes in a manner similar to what I > did with the journal search filters [2]. Stay tuned. > > [1] > https://github.com/walterbender/sugar/commit/59d09d6dde042dee60c4d744b45b76270f025cba > [2] https://github.com/sugarlabs/sugar/pull/265 Excellent! Let's do a design meeting next week. Monday and Tuesday are holidays here for carnival. Is Wednesday fine for you? -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Best time format for logging?
Interesting Nagarjuna, 2014-02-28 12:36 GMT-03:00 Nagarjuna G : > On Friday, February 28, 2014 09:12:58 AM Walter Bender wrote: > >> It seems time on activity is an oft-requested feature. IMHO, we should > >> maintain those data in the activity instance metadata like we do > >> launch times et al. Should be a fairly straight-forward patch. > >> > >> (My rationale is that making it part of the activity metadata, it is > >> accessible to the Sugar user -- part of the effort to "make learning > >> visible" to the learner, not just the administrator.) > >> > > > > > > On of the requirements of our work is to have the log time in millisecond, > or microseconds if possible. We would like to measure response times in Chat > activity. Often, multiple responses can be seen within one second when a > group is chatting, which does not allow us to calculate the response times. > We did tweak our local instance of Chat activity to write logs with > microseconds. But it will be good if this feature is available across all > activities. I guess it depends on the data. Nanoseconds can be obtained with command: date +%s.%N 1393609027.074597846 > > > > -- > > GN > > -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Best time format for logging?
2014-02-28 11:04 GMT-03:00 Walter Bender : > We've discussed (in AU) adding something similar to Sugar activities: > a metadata field with the elapsed time that the activity is visible. > We should coordinate all of these changes. Absolutely. I'm trying Martin's Harvest and looking how it can be extended. Thanks for the time format tip. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Best time format for logging?
Hi, this is a general question but related with Sugar. I have made changes in olpc-utils to log the session duration and kind (Sugar or GNOME). This will be used for statistics. https://github.com/manuq/olpc-utils/compare/boot-stats?expand=1 My log format is now: START_SUGAR 27/Feb/2014:17:33:17 END 27/Feb/2014:17:59:47 START_SUGAR 27/Feb/2014:18:00:24 END 27/Feb/2014:18:44:54 START_GNOME 27/Feb/2014:18:45:30 END 27/Feb/2014:18:50:26 START SUGAR 27/Feb/2014:18:51:03 END 27/Feb/2014:18:57:58 But I see that in many places Linux logs times as date +%s, which outputs seconds like: 1393595186 . What is best? -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] HTML 5 chapters for "Make Your Own Sugar Activities!"
Maybe a nice task for GSOC? 2014-02-26 13:45 GMT-03:00 James Simmons : > During the 2012 Google code-in Lionel wrote a nice chapter for MYOSA on > making Activities using HTML 5 and WebKit. I have been slowly and steadily > updating the other chapters in the book to use Sugar 3 and GTK 3. I have not > updated the website with the latest changes because I don't want the book to > be in a half-done state, but I have been making steady progress. > > One thing I have noticed from lurking on this mailing list is that HTML 5 > and Sugar have made a lot of progress since that chapter was written. I get > the impression that what is written there may already be obsolete. I also > feel that I'm not the guy who can fix that. I did a fair amount of Activity > development before writing MYOSA but I've drifted away from it since then. > > I believe that HTML 5 is going to be a big deal for Sugar and that MYOSA > needs to have some new or updated chapters to reflect that. I am hoping that > some of you might contribute this content. > > As for my own updates, some of them might be published in a couple of weeks. > > Working on this book has been a rewarding experience for me. I consider it > part of my own Constructionist education. Since finishing it I have been > involved in writing or publishing many other books. I have transcribed books > for Project Gutenberg and Project Gutenberg Canada. I have scanned a bunch > of books for the Internet Archive, using a scanner I designed and built > myself. I updated a memoir of my days among the Hare Krishnas that had been > on a shelf for 30 years and published it, getting five star reviews on > Amazon. I have formatted for publishing a twelve volume illustrated English > edition of The Mahabharata, the great epic of India. I have written a > science fiction novel and am working on a second one. > > I am not suggesting that contributing HTML 5 chapters to this book will > change your life. However, it definitely changed mine. > > James Simmons > > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Fwd: [b2g] Introducing B2G to x86
2014-02-25 18:56 GMT-03:00 Daniel Narvaez : > This is a very interesting development as a possible base platform for a > future fully html based Sugar. B2G always felt like the perfect platform for > it, if not because it wouldn't (fully) work on a normal Linux distro. Interesting Daniel, thanks. I also think the B2G is very aligned to what we are trying to do. I've been trying Firefox OS with both the Firefox add-on and the b2g binary. It looks promising. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar-web can't find web socket port
Hi Lionel, great to know you are upstreaming sugarizer! 2014-02-25 14:02 GMT-03:00 Lionel Laské : > > > I've tried to analyze more the issue. The problem come from env.js [1], the > env.isStandalone() test return true, so the environment parameter is an empty > object. I'm not sure to understand why this test is need. > What means "Standalone" ? Standalone means http://developer.sugarlabs.org/web-architecture.md.html#web%20activities%20standalone > FYI the method return true because env.getURLScheme() return "http", so the > test condition is false. > Does it mean that the test condition should not be this ? It means you are using WebkitGTK1. We encourage web development in WebkitGTK2. The WK1 is a fallback. > > Any suggestion about this method is welcome. I suggest you do web development on sugar-build. I guess some day XOs will come with latest Fedora. We can't rely in old Webkit because it limits development. > > Lionel. > > > > [1] https://github.com/sugarlabs/sugar-web/blob/master/env.js#L11 > > > > 2014-02-24 23:28 GMT+01:00 Lionel Laské : > >> Hi all, >> >> I'm working to merge Sugarizer and Sugar Web API. >> I've just found an issue that I thought it was related to my work but that >> is not because I've found the same issue in the last version of Maze Web [1]. >> >> The symptom is that the icon don't use buddy color and that the Stop button >> don't answer. >> The trace show that the Sugar Web API don't retrieve correctly the web >> socket port. The port is undefined in bus.js [2]. See the log below - tested >> on last Sugar 0.100 build on XO-4. >> >> I suspect that it come from a recent update of Sugar Web API because the >> problem doesn't appear on the same machine with an older Sugar Web Activity >> like FoodChain [3] - that use an old version of Sugar Web API. >> >> BTW I didn't find why this variable could not be initialized :-( >> >> Any idea ? >> >> Lionel. >> >> >> >> [1] http://activities.sugarlabs.org/en/sugar/addon/4727 >> [2] https://github.com/sugarlabs/sugar-web/blob/master/bus.js#L19 >> [3] http://activities.sugarlabs.org/en/sugar/addon/4612 >> >> >> >> xo-d2-7d-0b.localdomain - - [24/Feb/2014 22:03:02] "GET >> /lib/sugar-web/activity/shortcut.js HTTP/1.1" 200 - >> xo-d2-7d-0b.localdomain - - [24/Feb/2014 22:03:03] "GET >> /lib/sugar-web/bus.js HTTP/1.1" 200 - >> xo-d2-7d-0b.localdomain - - [24/Feb/2014 22:03:03] "GET >> /lib/sugar-web/env.js HTTP/1.1" 200 - >> xo-d2-7d-0b.localdomain - - [24/Feb/2014 22:03:03] "GET >> /lib/sugar-web/datastore.js HTTP/1.1" 200 - >> xo-d2-7d-0b.localdomain - - [24/Feb/2014 22:03:03] "GET >> /lib/sugar-web/graphics/icon.js HTTP/1.1" 200 - >> xo-d2-7d-0b.localdomain - - [24/Feb/2014 22:03:03] "GET >> /lib/sugar-web/graphics/activitypalette.js HTTP/1.1" 200 - >> xo-d2-7d-0b.localdomain - - [24/Feb/2014 22:03:03] "GET /lib/rot.js >> HTTP/1.1" 200 - >> xo-d2-7d-0b.localdomain - - [24/Feb/2014 22:03:03] "GET >> /lib/sugar-web/graphics/palette.js HTTP/1.1" 200 - >> xo-d2-7d-0b.localdomain - - [24/Feb/2014 22:03:03] "GET /lib/text.js >> HTTP/1.1" 200 - >> xo-d2-7d-0b.localdomain - - [24/Feb/2014 22:03:03] "GET >> /lib/sugar-web/graphics/activitypalette.html HTTP/1.1" 200 - >> xo-d2-7d-0b.localdomain - - [24/Feb/2014 22:03:03] "GET /lib/domReady.js >> HTTP/1.1" 200 - >> xo-d2-7d-0b.localdomain - - [24/Feb/2014 22:03:03] "GET >> /lib/sugar-web/graphics/icons/emblems/arrow-down.svg HTTP/1.1" 200 - >> xo-d2-7d-0b.localdomain - - [24/Feb/2014 22:03:03] "GET >> /activity/activity-icon.svg HTTP/1.1" 200 - >> xo-d2-7d-0b.localdomain - - [24/Feb/2014 22:03:03] "GET >> /lib/sugar-web/graphics/icons/emblems/arrow-up.svg HTTP/1.1" 200 - >> ** Message: console message: http://0.0.0.0:36408 @0: Invalid url for >> WebSocket ws://localhost:undefined >> >> ** Message: console message: http://0.0.0.0:36408/lib/sugar-web/bus.js @19: >> SYNTAX_ERR: DOM Exception 12: An invalid or illegal string was specified. >> > > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Report about performance hackaton
2014-02-24 9:04 GMT-03:00 Martin Abente : > Awesome work! Let us know if there a way to help.. Yes please! One way to help us is with reviews and testing. I will be sending the first PRs soon. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Report about performance hackaton
Excellent resume Gonzalo! I have added yours and my thoughts in a feature page: http://wiki.sugarlabs.org/go/Features/Optimize_TreeViews I think this can be handled as a feature. 2014-02-23 23:40 GMT-03:00 Gonzalo Odiard : > The last Thursday and Friday, manuq and I worked together to try to find > the source of a few performance issues in Sugar. > > In particular, we worked in the treeviews, for the activities list > and the Journal. > > We did many, many tests, and learned a few tricks, here is a first summary. > The patches are not ready to push upstream, but we will continue working on > this > in the next weeks. You can look at the branches here [1] and [2] > > Findings: > > * We did test programs to test the treeview and profile it doing: > > python -m cProfile test_treeview.py > profile.txt > > This was very useful. We did tests to profile the scroll and to start the > journal as a new > application in a terminal. [3] > > * The source of the performance issues in the treeview is the > CellRendererIcon, > a treeview without it works ok. > > * The CellRendererIcon do a lot of unneeded work, the render method can be > optimized, > caching values. > > * The CellRendererIcon is connected to many signals, just detaching them > while scrolling > solves part of the problem. To do it, we implemented a ScrollingDetector > class. > > * The CellRendererIcon is not a widget, then, do not receive events when the > mouse > enter or leaves, and all the logic in the CellRendererInvoker is more > complex than > should be. Worst, we had 6 different CellRendererIcons in the > Journal, then we simplified (and solved issues) implementing a > TreeViewInvoker. > The TreeView knows where is every cell. While is much more simple and > responsive, > implementation is not finished yet. > > * The ObjectPalettes was created in the mouse enter callback, then if a user > moved > the mouse cursor over the activity icons., many palettes were created, and > that was > expensive [4]. And worst, it was racy. So you can crash Sugar if you move the mouse over the Journal icons for a while. > > * This changes make the activity list work really fast. The Journal no > longer freeze > if a user move the mouse over the activity icons, but the scroll is still > slowing at one point. > First we thought that was because of the datastore, but we found the journal > request first > 30 records, and later add 10 records more, and caches the last 50. Trying > with a journal > with less than 30 records we still see a moment when the Journal scroll > jumps, > but the datastore is not working. We find a suspicious method > "send_message_with_reply_and_block" doing the profiling, but we didn't found > where is used of is responsible of the problem. > > As you can see, this is only a start. We will prepare a wiki page with the > information > when is more clean, but wanted to share our findings, with the community. > Was really great work together in this issue in the same place, > I wonder if we can find a way to organize virtual hackatons by topics like > this. > > Regards, > > -- > > [1] https://github.com/manuq/sugar-toolkit-gtk3/commits/scrollingdetector > [2] https://github.com/manuq/sugar/commits/treeviews-optimizations > [3] http://blog.ludovf.net/python-profiling-cprofile/ > [4] http://bugs.sugarlabs.org/ticket/4343 > > Gonzalo Odiard > > SugarLabs - Learning Software for children > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Design Meeting, Friday 21th, 13.00 UTC
Sam, 11 UTC works better for you? From doodle.com I can see the others could attend too. 2014-02-19 18:06 GMT-03:00 James Cameron : > Can't speak for Sam, but I'm in the same timezone, and your 11 UTC is > our 22:00, which is a time that I am overly chatty and very frequently > wrong. ;-} > > -- > James Cameron > http://quozl.linux.org.au/ > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Design Meeting, Friday 21th, 13.00 UTC
I see in the comments [1] we are leaving out Samdroid with this schedule, and is a shame because he is doing a lot of UI work. Sam, what time range works for your timzone? [1] http://doodle.com/i4bg3nhxscyzn8qm5kptvt24/admin#cmt116367228 2014-02-19 17:23 GMT-03:00 Walter Bender : > We need to plow through more of the items still in the design queue > from last time (will find the email thread) and also a few new items: > Samdroid's notification, my campaign against combo boxes, etc. > > On Wed, Feb 19, 2014 at 3:07 PM, Manuel Quiñones wrote: >> - Friday 21th >> - 13.00 UTC >> >> Please add the topics you would like to discuss in this thread. Thanks! >> >> -- >> .. manuq .. >> ___ >> 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 -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [DESIGN] Design Meeting, Friday 21th, 13.00 UTC
- Friday 21th - 13.00 UTC Please add the topics you would like to discuss in this thread. Thanks! -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] PyGame/ Sugargame issues with GTK 3
2014-02-19 13:19 GMT-03:00 James Simmons : > Manuel, > > I am aware of the test Activity. I wrote this chapter on using PyGame to > develop Activities: > > http://en.flossmanuals.net/make-your-own-sugar-activities/making-activities-using-pygame/ > > The code changes to sugargame to make it recognize the plus and minus keys > aren't hard to figure out, and I could correct my personal copy of > sugargame. I was a bit surprised to find that while so much has changed in > Sugar since I wrote the book but sugargame still isn't an official part of > the Sugar API. It's been a couple of years now. Personally I don't see any reason to have sugargame inside Sugar. We are few to maintain it so the less code, the better. Sugargame is a module with only two Python files. So there is not much overload. In Sugar Web we opted to bundle the modules inside each activity, and many projects are doing the same. There were long threads in this mailing list about the pros and cons. Cheers, -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Design Meeting, Feb
2014-02-19 9:59 GMT-03:00 Gonzalo Odiard : > A time/date was defined? Only Walter and you confirmed. So let's wait a bit, or do it this friday. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] PyGame/ Sugargame issues with GTK 3
2014-02-19 6:26 GMT-03:00 James Simmons : > It occurs to me to ask if sugargame is still something you need to copy the > code into your activity to use or if it is part of sugar proper. I'm still > taking the latest code and copying it in. Yes, you need to copy sugargame inside your activity. Inside sugargame repository there is a test Activity https://git.sugarlabs.org/sugargame/mainline/trees/master/test It displays a bouncing ball. You should be able to change the ball direction with left and right arrows. Can you test the activity? Note that you should use PyGame events, not GTK+. The demo listens to pygame.KEYDOWN event in pygame.K_LEFT and pygame.K_RIGHT. > > James Simmons > > > > On Wed, Feb 19, 2014 at 2:52 AM, James Simmons wrote: >> >> Alan, >> >> Grabbing focus definitely helped. I get the arrow keys now. However, I >> also use the plus and minus keys and I still don't get them. In the logs I >> see these messages: >> >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Subtract unrecognized >> Key KP_Subtract unrecognized >> Key KP_Subtract unrecognized >> Key KP_Subtract unrecognized >> Key KP_Subtract unrecognized >> Key KP_Subtract unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key Num_Lock unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Subtract unrecognized >> Key KP_Subtract unrecognized >> Key KP_Subtract unrecognized >> Key KP_Subtract unrecognized >> Key KP_Subtract unrecognized >> Key KP_Subtract unrecognized >> Key KP_Subtract unrecognized >> Key KP_Subtract unrecognized >> Key KP_4 unrecognized >> Key KP_4 unrecognized >> Key KP_4 unrecognized >> Key KP_4 unrecognized >> Key KP_4 unrecognized >> Key KP_4 unrecognized >> Key KP_4 unrecognized >> Key KP_4 unrecognized >> Key KP_4 unrecognized >> Key KP_4 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_8 unrecognized >> Key KP_8 unrecognized >> Key KP_8 unrecognized >> Key KP_8 unrecognized >> Key KP_8 unrecognized >> Key KP_8 unrecognized >> Key KP_2 unrecognized >> Key KP_2 unrecognized >> Key KP_2 unrecognized >> Key KP_2 unrecognized >> Key KP_2 unrecognized >> Key KP_2 unrecognized >> Key KP_8 unrecognized >> Key KP_8 unrecognized >> Key KP_8 unrecognized >> Key KP_8 unrecognized >> Key KP_8 unrecognized >> Key KP_8 unrecognized >> Key KP_4 unrecognized >> Key KP_4 unrecognized >> Key KP_4 unrecognized >> Key KP_4 unrecognized >> Key KP_4 unrecognized >> Key KP_4 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_Subtract unrecognized >> Key KP_Subtract unrecognized >> Key KP_Subtract unrecognized >> Key KP_Subtract unrecognized >> Key KP_Subtract unrecognized >> Key KP_Subtract unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key Scroll_Lock unrecognized >> Key Scroll_Lock unrecognized >> Key Scroll_Lock unrecognized >> Key Scroll_Lock unrecognized >> Key KP_8 unrecognized >> Key KP_8 unrecognized >> Key KP_8 unrecognized >> Key KP_8 unrecognized >> Key KP_8 unrecognized >> Key KP_8 unrecognized >> Key KP_8 unrecognized >> Key KP_8 unrecognized >> Key KP_2 unrecognized >> Key KP_2 unrecognized >> Key KP_2 unrecognized >> Key KP_2 unrecognized >> Key KP_2 unrecognized >> Key KP_2 unrecognized >> Key KP_4 unrecognized >> Key KP_4 unrecognized >> Key KP_4 unrecognized >> Key KP_4 unrecognized >> Key KP_4 unrecognized >> Key KP_4 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_6 unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Add unrecognized >> Key KP_Subtract unrecognized >> Key KP_Subtract unrecognized >> Key KP_Subtract unrecognized >> Key KP_Subtract
Re: [Sugar-devel] [DESIGN] Replace combo box in Journal Search
2014-02-18 19:01 GMT-03:00 Walter Bender : > I've hit to roadblocks: > (1) As I mentioned, for some reason, I cannot get ellipsis to work on > the toolbar label (it works elsewhere). Strange. Toolitems should ellipsize if needed. What is the consequence? The items fall outside the toolbar? > (2) It seems that whatever page is attached to the toolbar button is > resized to full screen width. I've not been able to figure out a > workaround. Can you show us the code? > > -walter > > On Tue, Feb 18, 2014 at 12:44 PM, Walter Bender > wrote: >> yes... except that since I switched to using the new approach, >> ellipsis stopped working on the toolbar (works on the palette). >> >> -walter >> >> On Tue, Feb 18, 2014 at 12:26 PM, Gonzalo Odiard >> wrote: >>> What happen with long activity names? Is ellipzed? >>> >>> Gonzalo >>> >>> >>> On Tue, Feb 18, 2014 at 12:45 PM, Walter Bender >>> wrote: I've been working on another feature for 1.02. The idea is to replace the clumsy combo boxes used in Journal search with simple palettes. There are several mock ups on [1]. So far, generally positive feedback from the design team. regards. -walter [1] http://wiki.sugarlabs.org/go/Features/Replace_combo_box_in_journal_search -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel >>> >>> >>> >>> >>> -- >>> Gonzalo Odiard >>> >>> SugarLabs - Learning Software for children >> >> >> >> -- >> Walter Bender >> Sugar Labs >> http://www.sugarlabs.org > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Fwd: Backup/Restore
Forwarding another message from Tony. -- Forwarded message -- From: Tony Anderson Date: 2014-02-17 22:07 GMT-03:00 Subject: Backup/Restore To: ma...@laptop.org Hi, A footnote. I think one easy way to make the nick setting effective is to restart via a three-finger salute. This was a very important capability that we lost after 0.84 (as I recall). Yesterday, I had a student who had (through impatience) started so many activities that the XO was not responding. It was necessary to shut down and do a cold start. The ctl+alt+del would have been a more effective answer. One extra would be to allow a dual-restart, i.e allow the user to restart either desktop after ctl+alt+del. That would be much easier than the current procedure. Tony -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Fwd: Sugar-devel Digest, Vol 64, Issue 36
Forwarding a message from Tony Anderson, because he can't send to the mailing list. -- Forwarded message -- From: Tony Anderson Date: 2014-02-17 21:40 GMT-03:00 Subject: Re: Sugar-devel Digest, Vol 64, Issue 36 To: ma...@laptop.org Hi, Unfortunately my current internet provider doesn't accept mail sent with my regular email address and so I cannot reply to the list. I am trying to implement a backup/restore system that will work with current builds (13 and 21). The environment to be supported is a set of XOs with a sometimes LAN connection to a schoolserver. Further, the set of XOs are shared with multiple users (e.g. grade 1 at 8am, grade 2 at 10am, and so on. The design assumes that there is not enough extra funds to purchase USB sticks and that SOAS is inappropriate because the only computers available to the site are the laptops and server. The design does not take into account the web developments underway. The approach is to make the changes to the Journal activity. The site must supply a roster of students and staff (essentially anyone whose work will be saved). This takes the form of a csv file which can be created from a spreadsheet (e.g. socialcalc). At boot, the user is requested to login. The user clicks on the grade (or role). This provides a list of the names. The user clicks on their name to complete login. This approach avoids the need for very young children to have to enter a name and password on a keyboard. One role is guest. In this role, the user has access to the capabilities of the system but no work will be saved. The volumes toolbar shows the login status. Login updates the computer nick so that collaboration will reflect the actual user. One current problem is that changes to the nick in gconf are not effective until the system is restarted. Hopefully, it will be possible to set up a signal on nick change. At login, the datamanager procedure is run. If the laptop is connected to the school server, the Journal is backed up. The datamanager (using the datastore class) reads all of the datastore. If a Journal object has been saved, the fact is recorded in the object's metadata. If a new item, the datamanager checks whether the object includes a data file. If so the journal object and file are uploaded to the schoolserver by the serial-number as currently. The object is stored as two files in the journal folder in the /library/users/serial-number folder. If the object has no data file, the metadata is uploaded to the log file in /llibrary/users/serial-number/log file. The object is deleted from the local datastore. The datamanager, when connected to the school server, checks space available. Quotas are set based on the XO model (e.g XO-1 is tighter than XO-1+). There need to be quotas for datastore size and the size of the Activities folder. There may be needs to manage other 'growth' such as Gnome or the web persistent store. In the case of the Journal, guest objects are deleted. Data files for Journal objects for users not logged in are deleted LRU as needed. For Sugar activities, they are deleted LRU. This policy needs review since at sites where laptops are rotated through a set of students, this could lead to 'thrashing'. An additional favorite button (probably a circle) is added to the Journal display for each object. If there is a local copy of the file - the circle has the XO color. Otherwise, it is transparent. The user can click on this button to set or clear. if it is clear and the user sets it and the laptop is connected to schoolserver, the file is downloaded. If the button is clear, the corresponding data file is deleted (but still available from the school server). The Journal activity only displays Journal objects 'owned' by the logged in user. If the user logs in from a different laptop and is connected to the school server, the datamanager downloads the metadata for the user's journal objects. If the user logs in from home (i.e. not connected to the school server), the list of users is maintain locally on the XO to enable new journal objects to be associated with the owner. The Journal activity will show only local Journal objects owned by that user - possibly none. A server side procedure run as a cron job reads all the journal objects for all serial-numbers and adds a corresponding entry to a Django database. This database is used to retrieve the metadata for a user logging in. The path to files associated with a Journal object are recorded in the database. The activities.py is modified to record the current value of the nick as the 'owner' of a new Journal object. Note: the nick is actually three entries in gconf: nick, id, and role(grade). The id is the database primary key which can be a site supplied registration number (learner reference number) or the Django PK. This means that information obtained from the school server users folders can be used without revealing personal information (only available from the database). In a
Re: [Sugar-devel] [DESIGN] Backup / Restore feature
> Testing > > - "remote backup" did nothing in my Sugar after pressing Continue. > When is this option valid? Can this option be avoided in that case? Found the reason in a previous email from Gonzalo: """ Right now, only a backend to work with local devices is implemented, the remote backend do nothing, is only to show how the selection of backends is done by the user, but will be deleted before push to master. """ -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [DESIGN] Backup / Restore feature
Sending my comment to the mailing list to open discussion. Feature pages: - http://wiki.sugarlabs.org/go/Features/Backup_and_Restore - http://wiki.sugarlabs.org/go/Features/Backup_and_Restore/Enhancements Pull request - https://github.com/sugarlabs/sugar/pull/176 I think this feature should live in My Settings for the following reasons: - it is a global operation, like My Settings > Software Update - the patch adds a new modal window that is very similar to My Settings. This is very prone to confusion. And we should aim to have only one modal to not complicate the shell. - the code should live in extensions/cpsection. This way is more separated from the shell. The less shell code we maintain, the better. And the less decoupled from the Journal, the better too (I had to solve one conflict to test it already). i can see why is good to have this attached to the Journal, but in my opinion there are more cons than pros going that way. Design feedback - make the background white like any other CP section - the buttons should not have a border, they should be similar to the ones in CP sectino - the buttons should not enlarge to fit the available space - the icons in buttons are too big, they should be the same size as CP section icons (GRID_CELL_SIZE) - the icons should have black stroke, white fill - the combo box should not enlarge too, use a left-aligned layout, like others CP sections - the progress dialog should be similar than the Software Update progress - Journal should be written with capital letter Testing - "remote backup" did nothing in my Sugar after pressing Continue. When is this option valid? Can this option be avoided in that case? References - Sofrware Update progress https://f.cloud.github.com/assets/83944/2188629/176e3154-9809-11e3-8aad-48afa77743dc.png - Combos are too wide: https://f.cloud.github.com/assets/83944/2188634/2d55f1b4-9809-11e3-85a0-e76286357e91.png - Icons too big: https://f.cloud.github.com/assets/83944/2188641/47ec1d5a-9809-11e3-9ae9-ec8a119f84eb.png - Suggested style for buttons: https://f.cloud.github.com/assets/83944/2188681/fad198c8-9809-11e3-9f47-5e836c26844a.png -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Design Meeting, Feb
maybe I wasn't clear enough. Please add your available dates here if you want to participate: http://doodle.com/i4bg3nhxscyzn8qm 2014-02-17 14:44 GMT-03:00 Manuel Quiñones : > Hi, design topics are accumulating. > > So let's meet for one hour this week, here are the time slots I'm available: > > http://doodle.com/i4bg3nhxscyzn8qm > > I'll send a list of topics soon. > > -- > .. manuq .. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [DESIGN] Design Meeting, Feb
Hi, design topics are accumulating. So let's meet for one hour this week, here are the time slots I'm available: http://doodle.com/i4bg3nhxscyzn8qm I'll send a list of topics soon. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Fwd: [IAEP] Set GNU GPL in monospace font
Thanks Ryan,
it certainly looks better, do you miind sending a pull request? I'm
happy to commit this.
2014-02-17 10:07 GMT-03:00 Manuel Quiñones :
> Where is the screenshot?
>
> 2014-02-15 20:16 GMT-03:00 Ignacio Rodríguez :
>> Sorry but +1 for the idea
>>
>> 2014-02-15 21:00 GMT-02:00, Ryan Cunningham :
>>> Here's a screenshot of the changes.
>>>
>>>
>>> On Sat, Feb 15, 2014 at 10:46 AM, Ryan Cunningham
>>> wrote:
>>>
>>>>
>>>>
>>>> Sent from my iPad
>>>>
>>>> Begin forwarded message:
>>>>
>>>> *From:* Daniel Narvaez
>>>> *Date:* February 15, 2014 at 10:44:57 AM PST
>>>> *To:* Ryan Cunningham
>>>> *Cc:* iaep
>>>> *Subject:* *Re: [IAEP] Set GNU GPL in monospace font*
>>>>
>>>> Hi,
>>>>
>>>> the best place to post this is sugar-devel, also put [DESIGN] in the
>>>> title
>>>> to attract design team attention. Thanks!
>>>>
>>>>
>>>> On 15 February 2014 19:43, Ryan Cunningham wrote:
>>>>
>>>>> Are any of you convinced to set the GNU GPL in a monospace font in the
>>>>> 'About My Computer' control panel? If so, here's a patch for it (at the
>>>>> bottom).
>>>>>
>>>>> The GNU GPL text file (v2.0) looks quite bad in a proportional font; but
>>>>> someone over at your GitHub repositories said that proportional fonts
>>>>> are
>>>>> better for dyslexic people.
>>>>>
>>>>> Here, I import an additional standard PyGTK class, "Pango" (from the
>>>>> module "gi.repository"), to handle font switching.
>>>>>
>>>>> ---
>>>>> diff --git a/extensions/cpsection/aboutcomputer/view.py
>>>>> b/extensions/cpsection/aboutcomputer/view.py
>>>>> index 6235e5c..5714145 100644
>>>>> --- a/extensions/cpsection/aboutcomputer/view.py
>>>>> +++ b/extensions/cpsection/aboutcomputer/view.py
>>>>> @@ -18,7 +18,7 @@
>>>>>
>>>>> from gettext import gettext as _
>>>>>
>>>>> -from gi.repository import Gtk
>>>>> +from gi.repository import Gtk, Pango
>>>>> from gi.repository import Gdk
>>>>>
>>>>> from sugar3.graphics import style
>>>>> @@ -206,6 +206,8 @@ def license_expander_cb(self, expander, param_spec):
>>>>> view_license = Gtk.TextView()
>>>>> view_license.set_editable(False)
>>>>>
>>>>> view_license.get_buffer().set_text(self._model.get_license())
>>>>> +fd = Pango.FontDescription('Monospace')
>>>>> +view_license.modify_font(fd)
>>>>> view_license.show()
>>>>> expander.add(view_license)
>>>>> else:
>>>>> ___
>>>>> IAEP -- It's An Education Project (not a laptop project!)
>>>>> i...@lists.sugarlabs.org
>>>>> http://lists.sugarlabs.org/listinfo/iaep
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Daniel Narvaez
>>>>
>>>>
>>>
>>>
>>> --
>>> Ryan Cunningham
>>>
>>
>>
>> --
>> Saludos.
>> Ignacio Rodríguez
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
>
> --
> .. manuq ..
--
.. manuq ..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Fwd: [IAEP] Set GNU GPL in monospace font
Where is the screenshot?
2014-02-15 20:16 GMT-03:00 Ignacio Rodríguez :
> Sorry but +1 for the idea
>
> 2014-02-15 21:00 GMT-02:00, Ryan Cunningham :
>> Here's a screenshot of the changes.
>>
>>
>> On Sat, Feb 15, 2014 at 10:46 AM, Ryan Cunningham
>> wrote:
>>
>>>
>>>
>>> Sent from my iPad
>>>
>>> Begin forwarded message:
>>>
>>> *From:* Daniel Narvaez
>>> *Date:* February 15, 2014 at 10:44:57 AM PST
>>> *To:* Ryan Cunningham
>>> *Cc:* iaep
>>> *Subject:* *Re: [IAEP] Set GNU GPL in monospace font*
>>>
>>> Hi,
>>>
>>> the best place to post this is sugar-devel, also put [DESIGN] in the
>>> title
>>> to attract design team attention. Thanks!
>>>
>>>
>>> On 15 February 2014 19:43, Ryan Cunningham wrote:
>>>
Are any of you convinced to set the GNU GPL in a monospace font in the
'About My Computer' control panel? If so, here's a patch for it (at the
bottom).
The GNU GPL text file (v2.0) looks quite bad in a proportional font; but
someone over at your GitHub repositories said that proportional fonts
are
better for dyslexic people.
Here, I import an additional standard PyGTK class, "Pango" (from the
module "gi.repository"), to handle font switching.
---
diff --git a/extensions/cpsection/aboutcomputer/view.py
b/extensions/cpsection/aboutcomputer/view.py
index 6235e5c..5714145 100644
--- a/extensions/cpsection/aboutcomputer/view.py
+++ b/extensions/cpsection/aboutcomputer/view.py
@@ -18,7 +18,7 @@
from gettext import gettext as _
-from gi.repository import Gtk
+from gi.repository import Gtk, Pango
from gi.repository import Gdk
from sugar3.graphics import style
@@ -206,6 +206,8 @@ def license_expander_cb(self, expander, param_spec):
view_license = Gtk.TextView()
view_license.set_editable(False)
view_license.get_buffer().set_text(self._model.get_license())
+fd = Pango.FontDescription('Monospace')
+view_license.modify_font(fd)
view_license.show()
expander.add(view_license)
else:
___
IAEP -- It's An Education Project (not a laptop project!)
i...@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep
>>>
>>>
>>>
>>> --
>>> Daniel Narvaez
>>>
>>>
>>
>>
>> --
>> Ryan Cunningham
>>
>
>
> --
> Saludos.
> Ignacio Rodríguez
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
--
.. manuq ..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About adding toolkit_type and toolkit_version options to bundles
Hi Ignacio, 2014-02-17 9:35 GMT-03:00 Ignacio Rodríguez : > Sorry, but was about: > import test2 I think importing the module can have unpredictable results. hasattr(test2, "gtk") > True hasattr(test2, "Gtk") > False > > If "Gtk" this return True import test3 hasattr(test3, "gtk") > False hasattr(test3, "Gtk") > True > > > Just a idea > > Saludos. > Ignacio Rodríguez > > > 2014-02-17 10:31 GMT-02:00 Gonzalo Odiard : >> >> This is a reply to @dnarvaez comment >> >> >> https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/104#issuecomment-35170356 >> >> The addition of a field to identify gtk2/gtk3 activities, >> was proposed as a solution to View Source issue [1] >> >> I think there are two other easier ways to solve this particular issue: >> >> * check the setup.py file >> * check the file with the startup class (view source already identify the >> file, see [2] >> >> Making changes to the activity.info file usually take a long time >> to get included in a significant number of activities, >> if we can solve it in the code is better in my opinion. >> >> -- >> Gonzalo Odiard >> >> SugarLabs - Learning Software for children >> >> [1] >> https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/104#issuecomment-35170356 >> [2] >> https://github.com/sugarlabs/sugar/blob/master/src/jarabe/view/viewsource.py#L205 >> >> ___ >> 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 > -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Keep an eye on buildbot
2014-02-14 9:48 GMT-03:00 Daniel Narvaez : > We are currently sending an email to the blame list and notification on irc. > I wasn't sending to the mailing list mainly because buildbot used to be a > bit fragile and I didn't want to spam... but it's pretty solid these days. > I'm happy to turn that on if people are fine with it. I'm fine with it. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Sugar-Devel] Toolkit version in the activity info
2014-01-31 23:14 GMT-03:00 Daniel Narvaez : > On 1 February 2014 03:00, Sam Parkinson wrote: >> >> >> Hi, >> >> Dnarvaez and I were discussing this on the irc; we really need to do >> distinction between the tool kit version in activity.info. >> >> This would be needed to for: >> >> view source >> because now changes to sugar-toolkit-gtk3 can break the gtk2 toolkit (!) >> >> Basically we were thinking to make a new thing: sugar-activity3 to launch >> gtk3 activities. > > It should probably just be a symlink. >> >> It would probably be the same at first, but in the future could be used to >> stop breakage to gtk2 activities. > > I think it was a mistake to not make a sugar-activity3 when we ported. > Though I'm not sure we can undo that now. It would be an API breakage (gtk3 > activities would stop to work unless they changed to sugar-activity3). > > If ever make another parallel installable gtk toolkit it should definately > be sugar-toolkit4 though :) >> >> So yeah, is this going to break everything? Could you think of a better >> way? > > It should not break much actually. Activities that have not switched to > sugar-activity3 will just not get the right sugar toolkit in view source. > > The main issue is probably that activities that change to sugar-activity3 > won't run on old sugar versions. Sigh... wish we had done this when porting > really :/ > > The alternative, as we discussed, is a new "toolkit" property in the info. > That should not break stuff, it's one more thing to remember for activity > authors though. Maybe we can have bundlebuilder warn about it. So, do we agree to have toolkit type and version in the activity.info? We have a pull request on this: https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/104 I'm fine with this. I think we need two versions: minimum and maximum. This is the same activities.sugarlabs.org has. Also see Android manifest as reference: http://developer.android.com/guide/topics/manifest/uses-sdk-element.html -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] text.js missing in Sugar Web Framework ?
Here is a pull request
https://github.com/sugarlabs/sugar-web-template/pull/23
2014-02-11 19:05 GMT-03:00 Manuel Quiñones :
> Hi Lionel,
>
> 2014-02-11 18:27 GMT-03:00 Lionel Laské :
>> Hi all,
>>
>> I'm playing with the last version of Sugar Web Framework [1]
>> At the top of the "sugar-web/graphics/activitypalette.js" [2] file there
>> is:
>>
>>define(["sugar-web/graphics/palette",
>> "text!sugar-web/graphics/activitypalette.html"], function
>> (palette, template) {
>>
>> 'use strict';
>>
>> var activitypalette = {};
>>
>>
>> The line "text!..." means that it use the "text" require.js plug-in [3].
>> However, I don't see any trace of the "text.js" into the activity template
>> [4].
>> When I launch my activity, I've got this issue:
>>
>> xo-74-2e-b8.localdomain - - [09/Feb/2014 14:28:05] "GET
>> /lib/sugar-web/graphics/icon.js HTTP/1.1" 200 -
>> xo-74-2e-b8.localdomain - - [09/Feb/2014 14:28:05] "GET
>> /lib/sugar-web/graphics/activitypalette.js HTTP/1.1" 200 -
>> xo-74-2e-b8.localdomain - - [09/Feb/2014 14:28:05] "GET
>> /lib/sugar-web/graphics/palette.js HTTP/1.1" 200 -
>> 1391956085.501851 ERROR root: file
>> /home/olpc/Activities/TankOp.activity//lib/text.js not found.
>> xo-74-2e-b8.localdomain - - [09/Feb/2014 14:28:05] "GET /lib/text.js
>> HTTP/1.1" 404 -
>> ** Message: console message: http://0.0.0.0:50134/lib/require.js @1765:
>> Error: Script error
>> http://requirejs.org/docs/errors.html#scripterror
>>
>> ** Message: console message: http://0.0.0.0:50134/lib/require.js @1765:
>> Error: Load timeout for modules:
>> text!sugar-web/graphics/activitypalette.html_unnormalized2
>> http://requirejs.org/docs/errors.html#timeout
>>
>> After a bit of exploring I've understood that it's related to the miss of
>> the text plug-in (text.js).
>> When I copy this file in the lib directory, the activity works.
>>
>> Do I miss something ?
>> Where the text.js file should come from ?
>> It should not be into the activity template [4] ?
>
> text.js is a dependency, so it should be listed in package.json, like
> domReady.js is. Then the volo command takes care of pulling deps.
>
> But turns out text.js is not listed in package.json. So it's a bug.
>
> sugar-build must be putting it there in the development environment.
>
>>
>> Thanks for your help.
>>
>> Lionel.
>>
>>
>> [1] https://github.com/sugarlabs/sugar-web
>> [2]
>> https://github.com/sugarlabs/sugar-web/blob/master/graphics/activitypalette.js#L1
>> [3] https://github.com/requirejs/text
>> [4] https://github.com/sugarlabs/sugar-web-template
>>
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>
>
>
> --
> .. manuq ..
--
.. manuq ..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] text.js missing in Sugar Web Framework ?
Hi Lionel,
2014-02-11 18:27 GMT-03:00 Lionel Laské :
> Hi all,
>
> I'm playing with the last version of Sugar Web Framework [1]
> At the top of the "sugar-web/graphics/activitypalette.js" [2] file there
> is:
>
>define(["sugar-web/graphics/palette",
> "text!sugar-web/graphics/activitypalette.html"], function
> (palette, template) {
>
> 'use strict';
>
> var activitypalette = {};
>
>
> The line "text!..." means that it use the "text" require.js plug-in [3].
> However, I don't see any trace of the "text.js" into the activity template
> [4].
> When I launch my activity, I've got this issue:
>
> xo-74-2e-b8.localdomain - - [09/Feb/2014 14:28:05] "GET
> /lib/sugar-web/graphics/icon.js HTTP/1.1" 200 -
> xo-74-2e-b8.localdomain - - [09/Feb/2014 14:28:05] "GET
> /lib/sugar-web/graphics/activitypalette.js HTTP/1.1" 200 -
> xo-74-2e-b8.localdomain - - [09/Feb/2014 14:28:05] "GET
> /lib/sugar-web/graphics/palette.js HTTP/1.1" 200 -
> 1391956085.501851 ERROR root: file
> /home/olpc/Activities/TankOp.activity//lib/text.js not found.
> xo-74-2e-b8.localdomain - - [09/Feb/2014 14:28:05] "GET /lib/text.js
> HTTP/1.1" 404 -
> ** Message: console message: http://0.0.0.0:50134/lib/require.js @1765:
> Error: Script error
> http://requirejs.org/docs/errors.html#scripterror
>
> ** Message: console message: http://0.0.0.0:50134/lib/require.js @1765:
> Error: Load timeout for modules:
> text!sugar-web/graphics/activitypalette.html_unnormalized2
> http://requirejs.org/docs/errors.html#timeout
>
> After a bit of exploring I've understood that it's related to the miss of
> the text plug-in (text.js).
> When I copy this file in the lib directory, the activity works.
>
> Do I miss something ?
> Where the text.js file should come from ?
> It should not be into the activity template [4] ?
text.js is a dependency, so it should be listed in package.json, like
domReady.js is. Then the volo command takes care of pulling deps.
But turns out text.js is not listed in package.json. So it's a bug.
sugar-build must be putting it there in the development environment.
>
> Thanks for your help.
>
> Lionel.
>
>
> [1] https://github.com/sugarlabs/sugar-web
> [2]
> https://github.com/sugarlabs/sugar-web/blob/master/graphics/activitypalette.js#L1
> [3] https://github.com/requirejs/text
> [4] https://github.com/sugarlabs/sugar-web-template
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
--
.. manuq ..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar web activity wait 1 minute at startup
2014-02-04 Gonzalo Odiard : > Probably would be good discuss with the web developers, manuq or dnarvaez? add a "WebKit1 known issues" section somewhere around http://developer.sugarlabs.org/#sugar%20web ? we can also make clear that WebKit1 is used as fallback when WebKit2 is not available, and that the development is focused on the latter. > > Gonzalo > > > On Tue, Feb 4, 2014 at 5:11 PM, Lionel Laské wrote: >> >> >> Sure. Where do you think I could document it ? >> >> Lionel. >> >> >> >> 2014-02-04 Gonzalo Odiard : >> >>> Great. Would be good have this issue documented. >>> >>> Gonzalo >>> >>> > > > > -- > Gonzalo Odiard > > SugarLabs - Learning Software for children > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Notifications
2014-02-04 Gonzalo Odiard : > > IMHO, keep all the notifications in one single place, like here > > http://wiki.sugarlabs.org/go/Design_Team/Proposals/Notifications#Alternative_corner_history_design > > would make easier locate them, instead of needing look in every activity > palette. I would go for one or the other, but not for a mix of the designs. The pros and cons are already depicted in the wiki, and I think the first proposal is more developed and covers all the considerations. And the best of all is that is almost implemented, with Sam and Martin efforts. > If we implement the notifications in the activity palette, we need add a > badge to the activity icon as in > > http://wiki.sugarlabs.org/go/Design_Team/Proposals/Notifications#Notification_badges > > to help the user know about the issue. Yes, the badge is a must for this design. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Notifications
2014-02-03 Martin Abente : > > Just to clarify a bit more, what I previously show could apply for system > events that do not belong to activities or journal. I think your implementation goes well with Gary design here for non-activity notifications http://wiki.sugarlabs.org/go/Design_Team/Proposals/Notifications#School_server_messages The icon you used [!] could be the generic icon, and could be replaced by a more specific icon, like a school graphic in the mockup. > I think Sam proposal is great and we should definitely support it for > activities and any other UI components that already has a iconic > representation in the frame. > > But, for miscellaneous things we could consider having a special icon > somewhere in the frame (permanent or not), to avoid putting it in the wrong > place just because we don't have a "proper" place. I agree with your implementation and Gary design: - top side of the frame, like the notifications for activities - not permanent, all notifications should be dismissable > > > > On Mon, Feb 3, 2014 at 11:45 PM, Martin Abente > wrote: >> >> A video from a few yeara ago: >> http://www.sugarlabs.org/~tch/videos/messages.mpeg >> >> The design itself is not a distraction. The notifications are hidden in the >> frame. Even when the frame activates the messages queue is still hidden in >> the palette. Only when the user activates the palette the messages queue is >> shown. >> >> The messages are not lost since they are kept in the palette queue until >> explicitly removed by the user or when replaced by other when the queue is >> full. >> >> I think that, design wise, complies with both criteria Gonzalo mentions. >> Other details like, should this icon be in that frame section or another, or >> even if the icon should pulse or only show user's color are design details >> can be improved I think. >> >> >> On Thu, Jan 30, 2014 at 11:49 AM, Gonzalo Odiard >> wrote: >>> >>> One problem we have right now with the notifications in Sugar, >>> is than is very easy lose a notification. >>> A common case is when you send a file to a friend. >>> Your friend receive a notification, and need accept it, >>> but the corner icon flash by a short time. >>> Is something difficult to balance, to not distract the user, >>> then need be carefully designed. >>> >>> Gonzalo >>> >>> >>> >>> On Thu, Jan 30, 2014 at 9:46 AM, Daniel Narvaez wrote: Don't forget to add [DESIGN] for this kind of stuff. On 29 January 2014 01:48, Sam Parkinson wrote: > > Hi, > > I was working on a little notification thing as per the designs. You can > download it and test it from here: > https://github.com/SAMdroid-apps/sugar/tree/NotificationWIP and > https://github.com/SAMdroid-apps/sugar-toolkit-gtk3/tree/NotificationsWIP. > You can check out a test activity here: > https://git.sugarlabs.org/~samdroid/hello-world/hello-notification-world. > (To use the test, press notify and wait 3 seconds). > > Here are some pretty pics: > > > (the thing is in the top-left) > > > > You can click on the notifications to close them. They do nothing since > we don't (yet) have an intent system. > > API in sugar3.activity.Activity: > > def notify(self, summary, body, intent): > """ > Display a notification with the given summary and body. > The notification will have the activity's icon as the icon. > **intent currently does nothing, so whatch this space** > """ > > See the example for usage :) > > > Please tell me what you think :) > > > Sam > > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel >>> >>> >>> >>> -- >>> Gonzalo Odiard >>> >>> SugarLabs - Learning Software for children >>> >>> ___ >>> Sugar-devel mailing list >>> Sugar-devel@lists.sugarlabs.org >>> http://lists.sugarlabs.org/listinfo/sugar-devel >>> >> > -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Notifications
2014-01-29 Sam Parkinson : > > Hi, > > Here is a video: https://vidd.me/oJD Great start! We've been discussing this on IRC, and Sam pointed me to the design proposal. Is the first one on this page: http://wiki.sugarlabs.org/go/Design_Team/Proposals/Notifications (Sam, please point to the design you are basing your work next time :-) I think the [!] badge is better than the pulsing icon. Pulsing is used to indicate that the activity is starting. About "system" notifications, the proposal doesn't make a distinction. Disk usage notifications can belong to the Journal, and messages coming from the school server can live in their own icon. The same can be used for any other notification. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] JOURNAL+
2014-02-02 Sam Parkinson : > > Hi > > This changes the journal completely! Now objects are displayed like > sentences, like a real journal. I love it! There are a lot of considerations to make here, so please understand that it can be a long journey implementing without getting regressions. The 90% is easy to implement, the difficulty is in the details (Gonzalo's mantra). Also, it would be great if you can finish the other great stuff you were implementing before trying to eat this big elephant. The replacement of the list view in the home is much appreciated, and the notifications too. Of course is up to you if you want to carry things in parallel, but it will be easier for us all. My time as maintainer is limited, and I have my own tasks. Let me clarify that you are doing a great job and your contributions are much appreciated. Welcome to the design team :) So, for this one: - It seems you are basing your work on the design 01 here: http://wiki.sugarlabs.org/go/Design_Team/Designs/Journal is good to make that explicit, I was aware of the page but others may not know. - The latest changes in the Journal added multiple selection of items, so they can be easy to copy and delete. I think that feature should not be left aside. - In current Journal and in the design 01 there is a list of the friends that have collaborated with you, in case the activity was shared. I like how design 01 display them adding the "with.." to the phrase. - If you start a download in Browse or other activity, or if a file is transferred, the Journal shows a progress bar. This should be considered in the new design. > There is the action text (Logged, Did a, Wrote) which is set like this: (In > activity.info) > > action_text = Watched - good idea! Apart from the action text in activities, there can be Journal entries not tied to activities. This happens for example if you copy a file from a USB stick, or if you download a file from Browse. We should consider those cases. Maybe a general text like "Got a.. [image icon] 2 days ago". > > Then there is the expander thing: > > (Record GTK3 is buggy!) > > This is as simple as: > > mediaObject.metadata['is_child'] = True > > datastore.write(mediaObject) > > activity.add_child(recd.datastoreId) > > Pull request: https://github.com/sugarlabs/sugar/pull/240 > > Thanks, > > Sam -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Sugar-Devel] Toolkit version in the activity info
2014-01-31 Daniel Narvaez : > On 1 February 2014 03:00, Sam Parkinson wrote: >> >> >> Hi, >> >> Dnarvaez and I were discussing this on the irc; we really need to do >> distinction between the tool kit version in activity.info. >> >> This would be needed to for: >> >> view source >> because now changes to sugar-toolkit-gtk3 can break the gtk2 toolkit (!) >> >> Basically we were thinking to make a new thing: sugar-activity3 to launch >> gtk3 activities. > > It should probably just be a symlink. >> >> It would probably be the same at first, but in the future could be used to >> stop breakage to gtk2 activities. > > I think it was a mistake to not make a sugar-activity3 when we ported. > Though I'm not sure we can undo that now. It would be an API breakage (gtk3 > activities would stop to work unless they changed to sugar-activity3). > > If ever make another parallel installable gtk toolkit it should definately > be sugar-toolkit4 though :) >> >> So yeah, is this going to break everything? Could you think of a better >> way? > > It should not break much actually. Activities that have not switched to > sugar-activity3 will just not get the right sugar toolkit in view source. > > The main issue is probably that activities that change to sugar-activity3 > won't run on old sugar versions. Sigh... wish we had done this when porting > really :/ Yeah, is a shame we didn't thought about this. Maybe because we supposed that the move from gtk2 to gtk3 was transitory. > The alternative, as we discussed, is a new "toolkit" property in the info. > That should not break stuff, it's one more thing to remember for activity > authors though. Maybe we can have bundlebuilder warn about it. > > > More ideas welcome! For the View Source issue, the activities py files can be inspected. If they contain gtk3 code, then show toolkit3. Else, show the old toolkit. For example: grep -r --include="*py" "from gi.repository". Not the cleanest option, but works if this is the only issue identifying the proper toolkit for an activity. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New reviewer
Thanks Code! 2014-01-31 Daniel Narvaez : > Hello, > > this is just to let everyone know Code Raguet has kindly accepted to join > the sugar core team of reviewers! Thanks Code! > > -- > Daniel Narvaez > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Start an activity from inside another, take 2
I made a feature page: http://wiki.sugarlabs.org/go/Features/Start_activity_from_another_activity And here is a demo screencast: https://dl.dropboxusercontent.com/u/588753/start.webm Code: http://wiki.sugarlabs.org/go/Features/Start_activity_from_another_activity#How_To_Test I still need to: - make the Journal a user of this - handle exceptions - tests -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Feature proposal: ability to start an activity from inside another
2014-01-22 Manuel Quiñones > > Sam, Martin, > > 2014/1/21 Martin Langhoff : > > On Tue, Jan 21, 2014 at 3:48 PM, Sam Parkinson > > wrote: > >> - Android has a really simple system where you can say go to > >> www.abc.blogs.org in any app that can open it. That opens it in a web > >> browser or in the blogs.org app if installed. This works because the > >> blogs.org app says it can handle these types of links in its manifest. > > > > Yep, we discussed Android's 'intents' machinery, which seems the most > > elegant API design for this, back with Manuq, Gonzalo and dsd in > > Parana a while back. > > > > Manuq -- is building a basic intents API too large a task? Or perhaps > > changing existing activities is the big elephant? > > I'll re-read Android's docs for Intents and tell you. But anyway is > the best reference. http://wiki.sugarlabs.org/go/Features/Start_activity_from_another_activity#Android_Intents_as_reference -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Feature proposal: ability to start an activity from inside another
2014-01-22 Martin Abente : > Does the android API set some sort of constraints for Apps? IE: (a) can open > only one App a the time, (b) can't open it self, and stuff like that.. > > Just curious, I haven't found any general restriction.in their docs. The way Intents work with permissions is like this: your application can send an Intent to capture a picture from the camera The component that can take a picture is launched. The permission to access the camera is in the componet's application, not yours. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] [ANNOUNCEMENT] Sugarizer, a taste of Sugar for any device - v0.3
2014-01-29 Gonzalo Odiard : >> >> I found that the only thing you need to remove is the entry with key >> 'sugar-settings' in LocalStorage. > > > > Do you know how clean only that in chrome? - open inspector (ctrl shift i) - click on tab "resources" - unfold "local storage" in the sidebar - select "http://llaske.github.io/"; - select item with key "sugar_settings" - press delete key, or click on the X at the bottom of the list -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] [ANNOUNCEMENT] Sugarizer, a taste of Sugar for any device - v0.3
Maze Web v2 also missed the train :) 2014-01-29 Manuel Quiñones : > Oh, I just released Gears v6, with a simple but nice improvement, colors: > http://manuq.github.io/gears-activity/ > > Apart from fancy, is a way to identify the gears with the same number of > teeth. > > 2014-01-29 Lionel Laské : >> >> Yes, you could need to delete the cache history to see the new version. > > I found that the only thing you need to remove is the entry with key > 'sugar-settings' in LocalStorage. > > -- > .. manuq .. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] [ANNOUNCEMENT] Sugarizer, a taste of Sugar for any device - v0.3
Oh, I just released Gears v6, with a simple but nice improvement, colors: http://manuq.github.io/gears-activity/ Apart from fancy, is a way to identify the gears with the same number of teeth. 2014-01-29 Lionel Laské : > > Yes, you could need to delete the cache history to see the new version. I found that the only thing you need to remove is the entry with key 'sugar-settings' in LocalStorage. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] The need for a notification system
Hi Sam, 2014-01-27 Sam Parkinson : > Hi, > > I’ve been working on some stuff recently and I really see the need for a > simple notification system. One example of a user of the system is here: > https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/96. The thing is I’m > not sure how we want the system implemented. Maybe it would be good to have > a discussion about this stuff as I think it would be used a lot, both inside > the system and inside activities. for notifications we use GObject signals. And DBus for system - activities notifications. In your special case, I'm not sure about adding a "few space left in the device" in Sugar. See how Browse checks for the available disk space without calling another process: https://git.sugarlabs.org/browse/mainline/blobs/master/downloadmanager.py#line299 -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Less confusing activities list
2014-01-24 Sam Parkinson > > I worked on it for a little longer trying to make the star icons checkable, > but there are lots of issues in doing so. In the end I think that it is very > hard to implement and pretty worthless. Maybe a summary as a tooltip in the > traditional design would be good, I'll try. Anyway, I really think the ticket > is sort of fixed now; we now have check boxes in the journal. Also if you > would like to see a bigger fix you can check out the sentence/expander view > and the thumbnail view for the journal. > > The (very messy and not PEP8) code is here: > https://github.com/SAMdroid-apps/sugar/blob/fb8ec62cf308236fa292dd2635d4071800b3f3e1/src/jarabe/desktop/activitieslist.py, I tried to test your work replacing that file but got errors. Do you have a patch or diff against master? -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Less confusing activities list
2014-01-24 Sam Parkinson > > I worked on it for a little longer trying to make the star icons checkable, > but there are lots of issues in doing so. In the end I think that it is very > hard to implement and pretty worthless. Maybe a summary as a tooltip in the > traditional design would be good, I'll try. Anyway, I really think the ticket > is sort of fixed now; we now have check boxes in the journal. Also if you > would like to see a bigger fix you can check out the sentence/expander view > and the thumbnail view for the journal. Yeah, I think the summary doesn't quite fit this layout. It would be nice as a tooltip, as Alan said. But its a separate topic. Tell us what's the problem with making the star icons checkeable. I would like to see this applied soon, is a great addition to Sugar. > The (very messy and not PEP8) code is here: > https://github.com/SAMdroid-apps/sugar/blob/fb8ec62cf308236fa292dd2635d4071800b3f3e1/src/jarabe/desktop/activitieslist.py, > if you don't believe me. There are some really funny errors that are caused > when you run this :) > > Sam :) > > > On Fri, Jan 24, 2014 at 7:54 AM, Sam Parkinson > wrote: >> >> I've been working on the view for a little while now... >> I've had a big issue with palettes (right click menus) and haven't been able >> to fix it (yet). >> I had this random idea I had... >> >> When you right click on a icon it brings up this popup-ish thing. (This is >> only a work in progress as you can see by the tiny icon). >> I'm not really sure if this is bad or very bad, but I just thought I'd throw >> it out there. Anyway it looks very different to the journal, which fixes the >> bug. >> >> Also the pallet or the popup-ish thing may need to implement the staring >> because the icon view is written in a different way to the tree view. >> >> Sam >> >> >> >> On Tue, Jan 21, 2014 at 10:29 PM, Manuel Quiñones wrote: >>>> >>>> >>>> Hi, >>>> >>>> I was looking at bug #806 (http://bugs.sugarlabs.org/ticket/806), >>>> "Activities list view is very similar to Journal view and users delete >>>> activities instead of journal entries". >>>> >>>> I was thinking we could fix this issue by adopting an icon view for the >>>> activities list. It sort of looks a little tablety, which is good >>>> considering some of the sugar deployments are almost tablets (XO-4). Here >>>> is a prototype: >>> >>> >>> Whoa, this is excellent Sam! A very great improvement. I like Jame's idea >>> about the time. Using the time since the activity was last used is a more >>> useful information, and avoids the odd issue. I'm not sure about the need >>> to change the top right corner icon.. this still looks like a list. But >>> maybe a more specific icon could be an enhaccement. >>> >>> -- >>> .. manuq .. >> >> > -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Less confusing activities list
Hi Sam, 2014-01-23 Sam Parkinson > > I've been working on the view for a little while now... > I've had a big issue with palettes (right click menus) and haven't been able > to fix it (yet). > I had this random idea I had... Tell us the issue you are having with the palettes. > When you right click on a icon it brings up this popup-ish thing. (This is > only a work in progress as you can see by the tiny icon). > I'm not really sure if this is bad or very bad, but I just thought I'd throw > it out there. Anyway it looks very different to the journal, which fixes the > bug. > > Also the pallet or the popup-ish thing may need to implement the staring > because the icon view is written in a different way to the tree view. I think a palette is better in this case. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar web activity wait 1 minute at startup
2014-01-28 James Cameron : > I agree, no host lookups. > > But at the time before the delay, there are several connections open to the > server process, and then after the delay there is a sudden server side > connection reset and a new connection issued by the client side. > > I wish I knew where the server side code was. It is here inside Sugar: https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/src/sugar3/activity/webkit1.py#L61 because Gonzalo confirmed us that Lionel is running an image with the WebKit1 fallback. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] EaselJS+PreloadJS and XHR
2014-01-27 laurent bernabe : > Thank you for your answer. > > In fact, I develop the activity and preview it from inside Brackets IDE. > Previews are shown inside a Chrome browser. > So, when previewing from Brackets IDE, we can say that I am viewing it > locally, in a browser, though it uses a kind of server (adress is for > example : http://127.0.0.1:39643/index.html). > > But I've also tested under osbuild (with run option), but the image does not > appear neither. > > For the links, I am using relative paths. > The repository LearnChess (LearnChess) is up to date : I haven't done any > change locally since. The 'complete' callback is called, I get 'loaded image' logged in the console. https://git.sugarlabs.org/learnchess/learnchess_web/blobs/master/js/activity.js#line40 Seems a programming error. If I log the variable 'image', I get undefined. https://git.sugarlabs.org/learnchess/learnchess_web/blobs/master/js/activity.js#line42 , Let's move to IRC #sugar if you need more help . -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] EaselJS+PreloadJS and XHR
2014-01-27 laurent bernabe : > Hello everyone, > > I am using EaselJS and PreloadJS in one of my web activities (LearnChess) in > order to manage pictures inside a canvas. But I don't manage to show png > files. How are you trying? > According to this post : createjs_forum it can't be done locally without > launching a server like lampp, because CreateJS libraries rely on XHR. > > So does this mean that CreateJS is not well suited for Sugar ? No. Sugar serves the files correctly. Chances are: 1. you are trying your activity locally, directly in a browser from file://...index.html 2. you have added links to file://.../image.png If 1. run your activity from Sugar, or use a local server like "python -m SimpleHTTPServer" If 2. use relative paths to link your images -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] WebActivity : Resizing a canvas object to the screen size ?
2014-01-26 laurent bernabe : > I've solved my problem by integrating JQuery, thanks to the Shim section of > RequireJS, and by calling it in activity.js You also have an example of doing the same without JQuery in Clock web activity. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Translating https://github.com/sugarlabs/sugar-docs ?
Hey Bastien, 2014-01-27 Bastien : > Hi all, > > I'd like to start translating sugar-docs into french. Great! > What method? Adding the pages in a "fr/" subdirectory? That will work. We can also have FR / EN / .. selector in the site header. > Thanks for further directions, all best, > > -- > Bastien > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Programming in Python or as a Web Activity ?
2014/1/24 laurent bernabe > > Thank you, > > The most challenging task that I am facing in my development beginning, is to > get the libraries easel.js and tween.js work as shim dependencies of > require.js. In fact, I think I could read require.js documentation thousands > of times, I won't be able to get started. I have created a bootstrap activity for you: https://github.com/manuq/createjs-activity-bootstrap The bad thing with CreateJS is that they don't support AMD yet. But see https://github.com/CreateJS/EaselJS/wiki/Using-easeljs-and-tweenjs-with-requirejs. What worked for me: ./osbuild shell volo create my-game ./sugar-web-template cd my-game/lib wget http://code.createjs.com/easeljs-0.7.1.min.js mv easeljs-0.7.1.min.js easeljs.js wget http://code.createjs.com/tweenjs-0.5.1.min.js mv tweenjs-0.5.1.min.js tweenjs.js And see the changes I did: https://github.com/manuq/createjs-activity-bootstrap/commit/79f4e4ed730c71cf42bfa0419f109718fb598fcb > The other problem, is that I need to put a real canvas element inside the > ... but I don't know which size I must give to the canvas > in order to fit the sugar Window client area (without the toolbar). CreateJS does that for you. > At last, and for that they are plenty of documentations, Javascript OOP > development is a bit trikier than the Python/Java OOP development I have the feeling that I responded this to you already, no? > So, how can I go further, at least with points 1) and 2) ? > > Regards > > > 2014/1/24 Daniel Narvaez >> >> Try to share the issues you have been having with web activities, someone >> might be able to help. >> >> Android has probably better API and documentation then gtk, but then it >> won't run on Sugar. >> >> On Friday, 24 January 2014, laurent bernabe >> wrote: >>> >>> Hello everyone, >>> >>> I've started a new Web project (ChessLearning), but it seems that Web >>> development is not my best skills. However, before turning it into a Python >>> app, I am wondering whether I should do my best to fit the Web Activity >>> development. >>> >>> For example, I think of an easier Android port, but am I wrong when I say >>> that it is better than Python for that ? >>> >>> On the other side, Python + GTK3 programming is very hard, as the GTK3 >>> library is not so easy to get used to, and Python version is not as well >>> documented as the C one (Gnome developers fault). >>> >>> So, I know that may be more a decision of mine, but, what do you advise me ? >>> >>> Regards, >>> >>> Laurent Bernabé >> >> >> >> -- >> Daniel Narvaez >> > > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Rework the wireless control panel section to respect non-wireless connections
2014/1/21 James Cameron : > On Wed, Jan 22, 2014 at 01:22:39AM +0100, Daniel Narvaez wrote: >> So... I think we need design input here. Would a history list with a >> forget button a la GNOME be a good way handle that use case? > > I like that. Consistent with Gnome, which is a build option for XO. +1 .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Helping people to get started
2014/1/22 Daniel Narvaez : > Hello, > > I've been seeing this a *lot* on the irc channel > > 19:44 -!- moriarty_ [~anubhav@14.139.82.6] has joined #sugar > 19:45 < moriarty_> Hi ! I'm new here and I would like to contribute to your >project. Can someone get me started? > 20:01 -!- moriarty_ [~anubhav@14.139.82.6] has quit [Ping timeout: 272 > seconds] > > There are really a lot of people that would like to contribute. But we have > few good resources to get them started and I have the feeling we are not > doing a good job at pointing them to those. > > developer.sugarlabs.org is the most updated and valuable resource these days > but from a quick look to stats.sugarlabs.org it is very very low in number > of visits. The getting involved page on the wiki is not doing much better. > > Another major issue is that developer.sugarlabs.org does not have a page > about tasks contributors could tackle, which is usually what they ask for in > irc. > > What I would like to do is > > * Decide what should be the entry point for developers. developer.sugarlabs.org I see it is missing the Sugarlabs brand. I can help with that. > * Make sure it's well linked both from the main website and from the wiki, Yes, ideally developer. should be linked from sugarlabs.org homepage. Maybe inside the links in the header? wiki / download / activities / *develop* / donate > which seems to be the most important entry points. > * Put a link in the irc channel subject. Yes! Great idea. > * Add a page on developer.sugarlabs.org on how to find tasks to work on. This is the difficult part. Sam idea of top ten tickets is great. > * Figure out how get these people to talk to someone, if no one is around > when they join irc. I have the feeling subscribing to the mailing list is > too much of a barrier. Maybe the bot could point them to a page with a list > of people they can email directly? I see Gonzalo already volunteers for > that in the wiki, I'm happy to share the workload if necessary. > > About the first point in the list, we probably need an intermediate page > like > > http://wiki.sugarlabs.org/go/Sugar_Labs/Getting_Involved > > but I think clicking on "Developer" should then go directly to > developer.sugarlabs.org. > > Something to keep in consideration is that doing changes to the main website > might be difficult (a full rewrite is planned but currently stuck). Though I > think we should try to at least get a link to Getting_Involved there. > > So this is all a bit random, I'll try to make more concrete proposals later, > but I would really like to hear people thoughts. Most of the times, when I > scroll back my irc screen I see a potential contributor quitting like that > and it's a bit depressing... > > -- > Daniel Narvaez > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Feature proposal: ability to start an activity from inside another
Sam, Martin, 2014/1/21 Martin Langhoff : > On Tue, Jan 21, 2014 at 3:48 PM, Sam Parkinson > wrote: >> - Android has a really simple system where you can say go to >> www.abc.blogs.org in any app that can open it. That opens it in a web >> browser or in the blogs.org app if installed. This works because the >> blogs.org app says it can handle these types of links in its manifest. > > Yep, we discussed Android's 'intents' machinery, which seems the most > elegant API design for this, back with Manuq, Gonzalo and dsd in > Parana a while back. > > Manuq -- is building a basic intents API too large a task? Or perhaps > changing existing activities is the big elephant? I'll re-read Android's docs for Intents and tell you. But anyway is the best reference. We should be able to tell "Sugar, start this object with the best activity you can find", "Sugar, start this object with this specific activity", "Sugar, start this object with the activity it was created" Note that this is the same thing the Journal exposes in the menus "Start", "Start with..." and "Resume". So the code is already there. I'm trying to prevent a change in every activity, and instead use what we already have for the Journal: - the datastore objects metadata - the activities mime_types declaration - the shell registration of available activities I'll see if this suits to Android Intents. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Feature proposal: ability to start an activity from inside another
2014/1/21 Daniel Narvaez : > Without having considered it carefully, I'm a bit concerned about reusing > sugar-launch because it's not quite the same code path normal launching is > going through. Yes, I see it now. We should add a comment in sugar-launch to explain what's the intended usage. The only one I can think of now is tests. > But before getting to implementation details I think it would useful to > consider the Android intents suggestion that has been made. API wise a way > to launch the activity associated to a certain object_id makes a lot of > sense to me. Things would get more complicated if we wanted to launch a new > instance of an activity. Yes, dbus to the rescue. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Feature proposal: ability to start an activity from inside another
Hey Tincho, 2014/1/21 Martin Abente : > A while ago, I submitted a patch [1] to allow opening Browse (or others) > from another activities links. > > Maybe we could do something similar to that :)? > > Refs: > 1.http://marc.info/?l=olpc-sugar&m=129485435106175&w=2 I searched the ML history and found some threads that mentioned your patch, but couldn't find it (got a 404 in patchwork). I thought your patch was only for the URI, wich Daniel N landed, but it seems to have landed for the web effort. This is currently possible: sugar-launch org.laptop.WebActivity --uri http://.../ the site will open in Browse. > -cmd_args = activityfactory.get_command(activity) > +cmd_args = activityfactory.get_command(activity, options.activity_id, > +options.object_id, options.uri) using get_command() directly seems like a shortcut, but skips the Rainbow security that happens in ActivityCreationHandler. sugar-launch is skipping Rainbow. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar-devel Digest, Vol 63, Issue 73
2014/1/22 Tony Anderson :
> Hi,
>
> The original sugar-launch intended to provide this capability. It requires
> only
> a few lines of code.
>
> parser.add_option("-o","--object_id",action="store_true",dest="object_id",
> help="resume activity with object")
> parser.add_option("-u","--object_uri",action="store_true",dest="object_uri",
> help="path to file")
>
> adds the -o and -u option. In practice, I use the -o option.
>
> if options.object_id:
> cmd_args.append("-o")
> cmd_args.append(args[1])
> if options.object_uri:
> cmd_args.append("-u")
> cmd_args.append(args[1])
>
> added after the if options.debug sets the option at launch.
Thanks for the information Tony. This matches Martin Abente's patch.
--
.. manuq ..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Feature proposal: ability to start an activity from inside another
This topic appears once in a while in this mailing list, and as far as I know, each time it happens no one objects. So, time to bring it again. One of Sugar key principles is simplicity. Activities are meant to be simple, and users can make interesting things happen when they interoperate with the activities. They do so by using the Journal and the Clipboard. However, there are cases where you want to start an activity from inside another, thus skipping the step through the Journal. For example, a user wants to download and read a book. The current steps are: - start GetBooks activity - search for the book - download the book (get book) - show book in Journal - start Read activity from the Journal object If activities could start other activities, the steps are simpler: - start GetBooks activity - search for the book - download the book (get book) - start Read activity This limitation (among others) has made Ceibal find a replacement for GetBooks and Read, their own BibliotecaSegura. So I've been investigating a bit, and found that is preety easy to add this feature. In fact it is already possible. I was able to change GetBooks to open Read after a book is downloaded. See: https://github.com/manuq/get-books/compare/open-activity This is a bit hackish, - imports a model from the shell - the bundle_id of the activity is hardcoded I think the more elegant option is to extend sugar-launch to something like: sugar-launch --object_id object_id And reuse the code in the Journal that starts or resumes activities (misc.py). Thoughts? -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
