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
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
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
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
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
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
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
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
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
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,
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,
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
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
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
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
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
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
17 matches
Mail list logo
