[sugar] the ring
It was terrible to lose the pie chart for resource usage. That was very useful for both developers and kids. The new design makes the loss permanent, while still keeping a visual design that no longer makes any sense. Fixing the old ring doesn't seem so difficult. You can't have a minimum activity size, and you must have an entry for the OS. With those changes, things should work well enough for a visual tool. ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [Its.an.education.project] Sugar on the EEE PC
On 5/6/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Yes I made it work on a EEE PC using a dual boot configuration. Sugar runs, but activities suffer because of the limited screen resolution. Which resolution it has? I can give it a look next week when I get back to a working jhbuild install. Eben, is there a plan with overflowing toolbars? Thanks, Tomeu ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [PATCH] 1-1 Chat (non-Sugar Jabber clients #6298)
Le mercredi 07 mai 2008 à 10:03 +0200, Morgan Collett a écrit : I've attached patches for Sugar and Chat that handle incoming XMPP 1-1 connections, from a non-Sugar Jabber client. It's a bit of a proof of concept, because although it works there are some issues that need improving - so please review and comment... I'm looking for input from Marco/Tomeu, Eben, Daf/Guillaume... * From a Jabber client registered on the Jabber server I initiate a chat with the Buddy. * Presence Service sends private-invitation to sugar.presence and then to the shell. * The signal has the Telepathy channel for this 1-1 connection which needs to get to Chat. * I'm (ab)using activityfactory.create_with_uri to launch Chat with the Telepathy channel in the metadata. * That makes Chat launch magically. That violates the requirement that the user initiate the activity. * I'm using json (probably badly?) to pass the two strings identifying the Telepathy channel. * The first message from the non-Sugar client (which initiates the connection) gets dropped somewhere, and only subsequent messages get through to Chat. I guess you should be able to got this message using channel[CHANNEL_TYPE_TEXT].ListPendingMessages() See http://telepathy.freedesktop.org/spec.html#org.freedesktop.Telepathy.Channel.Type.Text We should probably call it in set_received_callback() Btw, it seems we never acked received messages. Is that intentional? According the spec each message should be acked when they are displayed. * Presence Service sends private-invitation on both CHANNEL_TYPE_TEXT and CHANNEL_TYPE_STREAMED_MEDIA (which should go to video chat eventually). When we have agreed on how to handle Chat I'll figure out how to differentiate them and send the media one to video chat. You can find the type of the channel by calling GetChannelType() on the channel object. Or maybe we could just add the channel type in the signal. It has also been suggested that the incoming chat appear as an invitation. I had a look but couldn't yet figure out how best to represent something that is not an activity, does not have colors, and is not a room on the server. Input appreciated. I agree, displaying an incoming chat as an invitation is much more saner than automatically launch Chat. G. ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [PATCH] 1-1 Chat (non-Sugar Jabber clients #6298)
On Wed, May 7, 2008 at 10:03 AM, Morgan Collett [EMAIL PROTECTED] wrote: * I'm (ab)using activityfactory.create_with_uri to launch Chat with the Telepathy channel in the metadata. * That makes Chat launch magically. That violates the requirement that the user initiate the activity. Perhaps we can expose incoming messages in the UI as an invitation? Marco ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] New Design - problem with Circle of Activities
On 5/7/08, Mikus Grinbergs [EMAIL PROTECTED] wrote: The 'ring' view in Activity Management needs fixing -- when MULTIPLE Activity instances with the same name exist in the system, each instance should be treated (and shown) independently. Yes, this is known and will be fixed hopefully soon. We don't intend to ship so flagrant bugs, we just haven't had time to fix those. Thanks, Tomeu ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Git rebase
A few of us had problems to figure out to submit a coherent set of patches from a random set of commit on a personal tree. Looks like git rebase -i is the answer. http://blogs.gnome.org/markmc/2008/05/07/git-workflow/ Seem to work nicely by my quick tests :) Marco ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] the ring
Hi, Maybe is not necessary to back to the old ring, new designs comes with new features. In this case can be created an activity to show the resources usage by the activities, the only problem with this, is that the activity need to access the /proc filesystem and other files just restricted to root user... cheers. Eduardo On Wed, May 7, 2008 at 2:45 AM, Albert Cahalan [EMAIL PROTECTED] wrote: It was terrible to lose the pie chart for resource usage. That was very useful for both developers and kids. The new design makes the loss permanent, while still keeping a visual design that no longer makes any sense. Fixing the old ring doesn't seem so difficult. You can't have a minimum activity size, and you must have an entry for the OS. With those changes, things should work well enough for a visual tool. ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] the ring
It was terrible to lose the pie chart for resource usage. That was very useful for both developers and kids. Was indication (by the ring) of resource usage actually released to users? My G1G1 showed only fixed-width pie slices. Here is an opportunity for a new user-information Activity. A 'log viewer' already exists; why not a 'resource viewer'? The new design makes the loss permanent, while still keeping a visual design that no longer makes any sense. I like the new design. I can choose which Activity-icons are shown by the ring. That means I have to go into the 'list' view much less often than in the old design I had to scroll its Activity-icons. Also, as others have mentioned, the currently running Activities can be seen (or switched to) anytime by bringing up the Frame -- without having to EXIT the current screen to bring up Home view. mikus p.s. I see that the *order* of the icons in the ring can change when Sugar is restarted. I liked it that in the old design I could manually adjust the ordering of the Activity-icons. pps. The 'list' view appears to not include a Shutdown entry. If my last use of Activity Management was in 'list', F3 takes an extra click (to switch to 'ring') to get to Shutdown. ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] the ring
On Wed, May 7, 2008 at 9:28 AM, Mikus Grinbergs [EMAIL PROTECTED] wrote: It was terrible to lose the pie chart for resource usage. That was very useful for both developers and kids. Was indication (by the ring) of resource usage actually released to users? My G1G1 showed only fixed-width pie slices. It never shipped because the information was never accurate enough to be meaningful. In fact, it was most times confusing. It is unfortunate that we lost this (potential) means of conveying more info, but I think the new designs gain us a lot over the previous version in terms of usability. Here is an opportunity for a new user-information Activity. A 'log viewer' already exists; why not a 'resource viewer'? I think this is what the Analyze activity is supposed to be about...it's a tool for looking at all the technical goings on of the laptop. I think there are a few sections within that activity, and if none of them currently cover this particular resource viewer, we should certainly add it to the list. The new design makes the loss permanent, while still keeping a visual design that no longer makes any sense. I like the new design. I can choose which Activity-icons are shown by the ring. That means I have to go into the 'list' view much less often than in the old design I had to scroll its Activity-icons. Also, as others have mentioned, the currently running Activities can be seen (or switched to) anytime by bringing up the Frame -- without having to EXIT the current screen to bring up Home view. These are both big wins for the new design in my mind, and have made my interactions with Sugar much more pleasant since I've been using the new builds. Two other advantages are the placement of the devices in the Frame for easy at-a-glance access, as well as the new [people, places, objects, and devices] edges of the Frame which will support the forthcoming notification system. p.s. I see that the *order* of the icons in the ring can change when Sugar is restarted. I liked it that in the old design I could manually adjust the ordering of the Activity-icons. Really? File that one in track ASAP, as that's clearly an undesired behavior. The ring should remain fixed so that kids can recall from memory where to find the one they are looking for. Reordering of activities within the ring via drag'n'drop is something I wholly support, but something I doubt will happen in the short term since there are many more important bugs to fix. This actually came up when I discussed the new designs with Jim yesterday, and it was flagged as a great community project, since we have no dependency on it working but would love to see someone take a stab at it! pps. The 'list' view appears to not include a Shutdown entry. If my last use of Activity Management was in 'list', F3 takes an extra click (to switch to 'ring') to get to Shutdown. This is true, but I'm not sure I have a better solution than the extra click at the moment. I do like the association of those machine management controls with the XO, and we couldn't come up with a reasonable way to include the XO in a list view. Of course, we expect that true shutdowns will be limited in practice, so it's not something I'm personally that concerned about at the moment. - Eben ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [PATCH] 1-1 Chat (non-Sugar Jabber clients #6298)
On Wed, May 7, 2008 at 4:57 AM, Marco Pesenti Gritti [EMAIL PROTECTED] wrote: On Wed, May 7, 2008 at 10:03 AM, Morgan Collett [EMAIL PROTECTED] wrote: * I'm (ab)using activityfactory.create_with_uri to launch Chat with the Telepathy channel in the metadata. * That makes Chat launch magically. That violates the requirement that the user initiate the activity. Perhaps we can expose incoming messages in the UI as an invitation? Indeed, the invitation model both makes sense and at the same time makes the launch a user action instead. That absolutely needs to be the way we handle this. It was asked how we might represent the activity in the UI. For starters, I would say that it would be to our benefit to come up with a service (or a part of the presence service) which can generically determine the activity (or activities) capably of handling an incoming request. There might be a couple of chat activities. We might have a distinct video or audio chat activity. In the future, we might have non-XO applications which can collaborate with XO activities as well. That's expanding the scope, but all this to say that ideally we'd have a way to suggest the appropriate activity icon(s) that can handle the incoming invitation. As far as colors go, one interesting option is to try to derive the colors of the sender based on the fact that most IM clients support a color pair (background, text) already. Pulling this off would be really slick. Short of that, I'd suggest simply choosing the receiver's XO color instead, as though they had initiated the conversation themselves, assuming we can't get such info from the sender. - Eben ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Modularizing activities
On Wed, May 7, 2008 at 10:17 PM, Bernie Innocenti [EMAIL PROTECTED] wrote: [cc += sugar] Marco Pesenti Gritti wrote: I like these ideas very much... I'm not sure about the separation of sugar core and activities though. I tend to think we should have a unified release process for them (at least on the short time) and having two different trac would probably make it harder. The Linux kernel keeps all drivers in the tree because this is the only way you can quickly change internal interfaces without the burden of backwards compatibility. Xorg modularized too much, and now every time they refactor the server all drivers break and some remain broken for 6 months or longer. Sugar might be different: there could be very little shared code between the shell and the activities. Communication is mostly dbus based, and protocols are notoriously much easier to keep stable than APIs. I expect API to change quite a bit for a while (in a compatible way). All considered, I think that keeping a core group of activities with the rest of Sugar would be a good idea. This is also what KDE and Gnome do. I agree. Marco ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Resp.: the ring
What about copying the main XO palette to our XO icon in the buddy part of the frame? It isn't used for anything else. Hoboprimate 2008/5/7, Eben Eliason [EMAIL PROTECTED]: On Wed, May 7, 2008 at 9:28 AM, Mikus Grinbergs [EMAIL PROTECTED] wrote: It was terrible to lose the pie chart for resource usage. That was very useful for both developers and kids. Was indication (by the ring) of resource usage actually released to users? My G1G1 showed only fixed-width pie slices. It never shipped because the information was never accurate enough to be meaningful. In fact, it was most times confusing. It is unfortunate that we lost this (potential) means of conveying more info, but I think the new designs gain us a lot over the previous version in terms of usability. Here is an opportunity for a new user-information Activity. A 'log viewer' already exists; why not a 'resource viewer'? I think this is what the Analyze activity is supposed to be about...it's a tool for looking at all the technical goings on of the laptop. I think there are a few sections within that activity, and if none of them currently cover this particular resource viewer, we should certainly add it to the list. The new design makes the loss permanent, while still keeping a visual design that no longer makes any sense. I like the new design. I can choose which Activity-icons are shown by the ring. That means I have to go into the 'list' view much less often than in the old design I had to scroll its Activity-icons. Also, as others have mentioned, the currently running Activities can be seen (or switched to) anytime by bringing up the Frame -- without having to EXIT the current screen to bring up Home view. These are both big wins for the new design in my mind, and have made my interactions with Sugar much more pleasant since I've been using the new builds. Two other advantages are the placement of the devices in the Frame for easy at-a-glance access, as well as the new [people, places, objects, and devices] edges of the Frame which will support the forthcoming notification system. p.s. I see that the *order* of the icons in the ring can change when Sugar is restarted. I liked it that in the old design I could manually adjust the ordering of the Activity-icons. Really? File that one in track ASAP, as that's clearly an undesired behavior. The ring should remain fixed so that kids can recall from memory where to find the one they are looking for. Reordering of activities within the ring via drag'n'drop is something I wholly support, but something I doubt will happen in the short term since there are many more important bugs to fix. This actually came up when I discussed the new designs with Jim yesterday, and it was flagged as a great community project, since we have no dependency on it working but would love to see someone take a stab at it! pps. The 'list' view appears to not include a Shutdown entry. If my last use of Activity Management was in 'list', F3 takes an extra click (to switch to 'ring') to get to Shutdown. This is true, but I'm not sure I have a better solution than the extra click at the moment. I do like the association of those machine management controls with the XO, and we couldn't come up with a reasonable way to include the XO in a list view. Of course, we expect that true shutdowns will be limited in practice, so it's not something I'm personally that concerned about at the moment. - Eben ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [Its.an.education.project] Sugar on the EEE PC
Tomeu Vizoso wrote: Which resolution it has? I can give it a look next week when I get back to a working jhbuild install. 800x480. -- \___/ _| o | Bernie Innocenti - http://www.codewiz.org/ \|_X_| It's an education project, not a laptop project! ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [OLPC library] Fw: Get involved - Measure Activity on the XO
Ray, Thanks for your email, As I see it I wasn't on cc on your reply so I am only seeing your message now when I am reading the mailing lists email, sorry for that. As a start I've put together this page (still needs more work) that details on the Measure Activity what it is...etc http://wiki.laptop.org/go/Measure And the code work in progress is here http://dev.laptop.org/git?p=projects/measure;a=tree;f=measure_stable;h=561325f7dc5e3ebdbe537bce54d062782e303cd9;hb=HEAD The last release was made from here http://dev.laptop.org/git?p=projects/measure;a=tree;f=measure_stable;h=be7ff4b83e543ab228eb62401bbd7a1a19215bfb;hb=854b9ef766670ea036554a46a0a7b21bd2eeb967 Some things I am aiming for the next release are here -- http://wiki.laptop.org/go/Measure/Plans Please feel free to let me know what you think would be other useful additions to Measure. I get a little free 17th May onwards and I will continue to spend a few cycles on taking forward the work then, but in the meanwhile I'd be glad to answer any questions you may have. regards Arjun On Thu, May 1, 2008 at 4:48 AM, Ray Phoenix [EMAIL PROTECTED] wrote: Linda, Thanks for sending this on to me. I forgot I sent it from your email... :-) Arjun, I'm in the Seattle area, and would love to work with you on the OLPC. I have worked with python and unix, so I might be of some help. Let me know how we can best work together. Thanks, Ray [EMAIL PROTECTED] 206-708-1604 619-961-7390 On Tue, Apr 29, 2008 at 1:11 PM, Linda Hill [EMAIL PROTECTED] wrote: - Original Message - From: Arjun Sarwal [EMAIL PROTECTED] To: Linda Hill [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; edward baafi [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Tuesday, April 29, 2008 11:17 AM Subject: Re: [OLPC library] Get involved - Measure Activity on the XO Ray, Thanks for your message. As I understand, that you wish to connect multiple sensors to the USB based sensor board and from the UI of your activity/application select which sensor to read from. Edward Baafi, cced here might be able to comment better on that since he's been most deeply involved in the programming of the USB based sensor board. It would be a matter of writing a simple python script that would involve making use of the pyusb python libraries. I would like to point out at this point that USB based sensor board support hasn't yet been incorporated into Measure yet, though I do have plans of doing that. Any help by anyone in this regard would be greatly welcome as I develop Measure from whatever free time I get from school studies. many thanks Arjun On Sat, Apr 19, 2008 at 3:51 PM, Linda Hill [EMAIL PROTECTED] wrote: Arjun, I'm just getting started working with my XO, and I built a temperature sensor with an LM35 chip. My intention is to have multiple sensors around the house, and read each of them separately. I am puzzling over how best to output a binary code to select which sensor I wish to read. I know that the USB port and the USB card that is being designed (and produced?) will allow me to communicate out from the XO, but is there some other way that I'm not thinking of that could be used? I like it that I can get analog data into the XO so easily. Now I'd like to know how to get digital data out effectively. Thanks, Ray Phoenix ___ Library mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/library -- Arjun Sarwal Intern, One Laptop per Child Email: [EMAIL PROTECTED] IRC: arjs on irc.freenode.net in #olpc, #olpc-health, #sugar ___ Library mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/library -- Arjun Sarwal http://dev.laptop.org/~arjs ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
