[IAEP] Concrete feedback

[Gonzalo Odiard]

You are showing one of the more commons problems when we talk about the
Journal.
Many times, bugs in activities are perceived like bugs in the Journal.
If one activity is not well sugarized, is a problem in the activity and must
solved.
And from a long time, the default way wen you open one activity, is open the
last instance.
This is not the right solution, because is not useful for all the
activities,
but solve the issue with Browse, Terminal, etc.
About massive operations, you can see the work from tch about multiple
selection operations.

Gonzalo



> *Concrete Feedback:*
>
> The journal is always full of garbage, hundreds of empty entries:  *is
> there a possibility to "CLEAN" the JOurnal?,* or much better, that the
> programs won't write empty entries?
>
> Empty entry = when a kid opens "Browse", and he closes 10 seconds later, it
> is useless that entry.
>
> If the kid uses "Write" for more than 15 minutes, probably he wrote
> something useful.
>
> For example , If the kid opens "Write" but he don't write anything, that
> entry would not be save on the journal.
>
> ANother example: Programs that are not well "sugarized", they save lots and
> lots of useless entries on the journal.
>
> The problem is not the space, those entries don't occupy nothing. The
> problem is the amount of entries.
> *
> TOO MUCH INFORMATION = NO INFORMATION*
>
> ------------------------------------------------------------------------------------
>
>
> Paolo Benini
> Montevideo
>
>
>
>
> _______________________________________________
> IAEP -- It's An Education Project (not a laptop project!)
> IAEP at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/iaep
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/iaep/attachments/20110615/e9a81c04/attachment.html>