Re: [Sugar-devel] Time spent on activity (was Best time format for logging?)
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 godi...@sugarlabs.org wrote: On Thu, Mar 27, 2014 at 4:17 PM, Manuel Quiñones ma...@laptop.org wrote: 2014-03-27 15:23 GMT-03:00 Gonzalo Odiard godi...@sugarlabs.org: 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
Re: [Sugar-devel] Time spent on activity (was Best time format for logging?)
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. 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. Regarding harvest, we can carefully drop that placeholder, and add a new table for storing these times, if needed. On Fri, Mar 28, 2014 at 6:53 AM, Walter Bender walter.ben...@gmail.comwrote: 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 godi...@sugarlabs.org wrote: On Thu, Mar 27, 2014 at 4:17 PM, Manuel Quiñones ma...@laptop.org wrote: 2014-03-27 15:23 GMT-03:00 Gonzalo Odiard godi...@sugarlabs.org: 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
Re: [Sugar-devel] Time spent on activity (was Best time, format for logging?)
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. 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
Re: [Sugar-devel] Time spent on activity (was Best time, format for logging?)
On Fri, Mar 28, 2014 at 9:38 AM, Tony Anderson tony_ander...@usa.netwrote: 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. 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
Re: [Sugar-devel] Time spent on activity (was Best time format for logging?)
2014-03-28 7:53 GMT-03:00 Walter Bender walter.ben...@gmail.com: 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 godi...@sugarlabs.org wrote: On Thu, Mar 27, 2014 at 4:17 PM, Manuel Quiñones ma...@laptop.org wrote: 2014-03-27 15:23 GMT-03:00 Gonzalo Odiard godi...@sugarlabs.org: 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-28 8:27 GMT-03:00 Martin Abente martin.abente.lah...@gmail.com: 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 walter.ben...@gmail.com 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 godi...@sugarlabs.org wrote: On Thu, Mar 27, 2014 at 4:17 PM, Manuel Quiñones ma...@laptop.org wrote: 2014-03-27 15:23 GMT-03:00 Gonzalo Odiard godi...@sugarlabs.org: 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?)
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.
Gonzalo
___
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 godi...@sugarlabs.org:
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?)
Hi Tony, On March 28, 2014 at 7:38 AM Tony Anderson tony_ander...@usa.net 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. Think the students need to learn how to use shutdown option in sugar, wonder how many have lost their work using that method. When the power light goes red, I would assume it would be possible to perform an orderly shutdown. I don't think there is a way for olpc's powerd to inform sugar that the XO is powering down. I'm pretty sure SoaS/sugar desktop is in the same boat, you tell sugar to shutdown the computer and that process uses dbus to tell the OS but nothing in sugar is listening for a dbus shutdown signal from outside of sugar to start an orderly shutdown. Jerry 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. 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 ___ 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?)
If it doesn't close properly, it gets discarded naturally. No complex logic. The only improvement it occurs to me, is that we could commit this time regularly... so even if its laptops shutdown we could still get some not-so-garbage data. Please no. This means write files many times, less battery use, etc. Gonzalo On Fri, Mar 28, 2014 at 11:42 AM, Gonzalo Odiard godi...@sugarlabs.orgwrote: On Fri, Mar 28, 2014 at 12:00 PM, Jerry Vonau m...@jvonau.ca wrote: Hi Tony, On March 28, 2014 at 7:38 AM Tony Anderson tony_ander...@usa.net 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. Think the students need to learn how to use shutdown option in sugar, wonder how many have lost their work using that method. When the power light goes red, I would assume it would be possible to perform an orderly shutdown. I don't think there is a way for olpc's powerd to inform sugar that the XO is powering down. I'm pretty sure SoaS/sugar desktop is in the same boat, you tell sugar to shutdown the computer and that process uses dbus to tell the OS but nothing in sugar is listening for a dbus shutdown signal from outside of sugar to start an orderly shutdown. This is a good point. If is not filled in a ticket, can you fill one? Gonzalo Jerry 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. 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 ___ 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 -- Gonzalo Odiard SugarLabs - Learning Software for children ___ 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 godi...@sugarlabs.org:
On Fri, Mar 28, 2014 at 9:38 AM, Tony Anderson tony_ander...@usa.net
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?)
On Fri, Mar 28, 2014 at 12:00 PM, Jerry Vonau m...@jvonau.ca wrote: Hi Tony, On March 28, 2014 at 7:38 AM Tony Anderson tony_ander...@usa.net 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. Think the students need to learn how to use shutdown option in sugar, wonder how many have lost their work using that method. When the power light goes red, I would assume it would be possible to perform an orderly shutdown. I don't think there is a way for olpc's powerd to inform sugar that the XO is powering down. I'm pretty sure SoaS/sugar desktop is in the same boat, you tell sugar to shutdown the computer and that process uses dbus to tell the OS but nothing in sugar is listening for a dbus shutdown signal from outside of sugar to start an orderly shutdown. This is a good point. If is not filled in a ticket, can you fill one? Gonzalo Jerry 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. 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 ___ 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
Re: [Sugar-devel] Time spent on activity (was Best time, format for logging?)
I was thinking something like:
{session:1396011616, 1396011616}
where at write_file time, the stop time is updated to the current time.
Tony
On 03/28/2014 10:19 AM, Manuel Quiñones wrote:
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: c, 1396011616, 1396045612}
___
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?)
IHMO, we should go for a expect failure approach. If it closes properly, we add a new entry in the spent-time list with the difference between the session started (not from the launches list) and the current time. so it would be: [3600, 1800, 600] In seconds, as we might have gadget-like activities that are only being used shortly. If it doesn't close properly, it gets discarded naturally. No complex logic. The only improvement it occurs to me, is that we could commit this time regularly... so even if its laptops shutdown we could still get some not-so-garbage data. On Fri, Mar 28, 2014 at 11:42 AM, Gonzalo Odiard godi...@sugarlabs.orgwrote: On Fri, Mar 28, 2014 at 12:00 PM, Jerry Vonau m...@jvonau.ca wrote: Hi Tony, On March 28, 2014 at 7:38 AM Tony Anderson tony_ander...@usa.net 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. Think the students need to learn how to use shutdown option in sugar, wonder how many have lost their work using that method. When the power light goes red, I would assume it would be possible to perform an orderly shutdown. I don't think there is a way for olpc's powerd to inform sugar that the XO is powering down. I'm pretty sure SoaS/sugar desktop is in the same boat, you tell sugar to shutdown the computer and that process uses dbus to tell the OS but nothing in sugar is listening for a dbus shutdown signal from outside of sugar to start an orderly shutdown. This is a good point. If is not filled in a ticket, can you fill one? Gonzalo Jerry 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. 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 ___ 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
Re: [Sugar-devel] Time spent on activity (was Best time, format for logging?)
That is just a separate idea, but just to clarify, I am not suggesting doing it each second. But in some sufficiently small interval, in minutes. Quick question, aren't the activities saving metadata regularly now? Anyway, I think the approach I mentioned should work fine, as I don't see why we should try anything too complex when this data is not 100% reliable as is just the time the activity was opened. just my opinion, On Fri, Mar 28, 2014 at 12:10 PM, Gonzalo Odiard godi...@sugarlabs.orgwrote: If it doesn't close properly, it gets discarded naturally. No complex logic. The only improvement it occurs to me, is that we could commit this time regularly... so even if its laptops shutdown we could still get some not-so-garbage data. Please no. This means write files many times, less battery use, etc. Gonzalo On Fri, Mar 28, 2014 at 11:42 AM, Gonzalo Odiard godi...@sugarlabs.orgwrote: On Fri, Mar 28, 2014 at 12:00 PM, Jerry Vonau m...@jvonau.ca wrote: Hi Tony, On March 28, 2014 at 7:38 AM Tony Anderson tony_ander...@usa.net 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. Think the students need to learn how to use shutdown option in sugar, wonder how many have lost their work using that method. When the power light goes red, I would assume it would be possible to perform an orderly shutdown. I don't think there is a way for olpc's powerd to inform sugar that the XO is powering down. I'm pretty sure SoaS/sugar desktop is in the same boat, you tell sugar to shutdown the computer and that process uses dbus to tell the OS but nothing in sugar is listening for a dbus shutdown signal from outside of sugar to start an orderly shutdown. This is a good point. If is not filled in a ticket, can you fill one? Gonzalo Jerry 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. Tony On 03/27/2014 09:45 PM, sugar-devel-request@lists.sugarlabs.orgwrote: 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 ___ 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 -- Gonzalo Odiard SugarLabs - Learning Software for children ___ 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?)
On Fri, Mar 28, 2014 at 12:19 PM, Martin Abente martin.abente.lah...@gmail.com wrote: That is just a separate idea, but just to clarify, I am not suggesting doing it each second. But in some sufficiently small interval, in minutes. Quick question, aren't the activities saving metadata regularly now? Anyway, I think the approach I mentioned should work fine, as I don't see why we should try anything too complex when this data is not 100% reliable as is just the time the activity was opened. Triggering on the events that already trigger write_file would accomplish much the same thing, just not the case where the activity is open and never in the background. just my opinion, On Fri, Mar 28, 2014 at 12:10 PM, Gonzalo Odiard godi...@sugarlabs.org wrote: If it doesn't close properly, it gets discarded naturally. No complex logic. The only improvement it occurs to me, is that we could commit this time regularly... so even if its laptops shutdown we could still get some not-so-garbage data. Please no. This means write files many times, less battery use, etc. Gonzalo On Fri, Mar 28, 2014 at 11:42 AM, Gonzalo Odiard godi...@sugarlabs.org wrote: On Fri, Mar 28, 2014 at 12:00 PM, Jerry Vonau m...@jvonau.ca wrote: Hi Tony, On March 28, 2014 at 7:38 AM Tony Anderson tony_ander...@usa.net 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. Think the students need to learn how to use shutdown option in sugar, wonder how many have lost their work using that method. When the power light goes red, I would assume it would be possible to perform an orderly shutdown. I don't think there is a way for olpc's powerd to inform sugar that the XO is powering down. I'm pretty sure SoaS/sugar desktop is in the same boat, you tell sugar to shutdown the computer and that process uses dbus to tell the OS but nothing in sugar is listening for a dbus shutdown signal from outside of sugar to start an orderly shutdown. This is a good point. If is not filled in a ticket, can you fill one? Gonzalo Jerry 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. 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 ___ 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 -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ASLO] Release Develop-41
Activity Homepage: http://activities.sugarlabs.org/addon/4058 Sugar Platform: 0.96 - 0.100 Download Now: http://activities.sugarlabs.org/downloads/file/28927/develop-41.xo Release notes: Changed skeletons dirs to make clear the sugar version needed Made the view settings permanent by using a config file (Sai Vineet) Fix sugargame template Place the cursor in the source, when select a object Make change font size buttons consistent with other activities Aesthetic changes (Sai Vineet) Fix initialization bug (Sai Vineet) Merge conflict removal (Sai Vineet) Add font size changing (Sai Vineet) Add theme switching to editor (Sai Vineet) Refactored code and divided code into sensible files (Sai Vineet) Add theme switching to editor (Sai Vineet) Refactored code and divided code into sensible files (Sai Vineet) Improve text in welcome screen Uses SUGAR_ACTIVITIES_PATH to find activities (works in sugar-build). (Sebastian Silva) Don't break with corner case exec commands in activity.info Replace the use of simplejson by json Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
