[Bugs] #2917 Log LOW: Log: collector
Sugar Labs Bugs
bugtracker-noreply at sugarlabs.org
Mon May 28 07:59:19 EDT 2012
#2917: Log: collector
----------------------------+-----------------------------------------------
Reporter: godiard | Owner: humitos
Type: enhancement | Status: assigned
Priority: Low | Milestone: Unspecified by Release Team
Component: Log | Version: Unspecified
Severity: Unspecified | Keywords: 12.1.0, easy-hack
Distribution: Unspecified | Status_field: Unconfirmed
----------------------------+-----------------------------------------------
Comment(by garycmartin):
Replying to [comment:7 humitos]:
> I understand the issue here. I'm thinking about how it should works.
Maybe just generate the {{{.zip}}} file when the user click on the export
button (remove the palette at all - but we missed the information text
there)
>
> So, what is the best way to do it? Maybe add that information text after
the generation of the file with a button pointing to the Journal: "See
this entry in the Journal"?
If we go with a standard toolbar button with a primary action when clicked
we have several options: 1) present a standard Sugar alert that says
something like "Capture Log information to Journal entry ((x) Cancel)
((5..1) Continue)" where the log is generated after the time-out or
Continue is clicked, see downloading a file in Browse for similar example;
2) present a standard Sugar alert that says something like "Log
information capture completed (([]) Show in Journal) ((v/) Ok)", after the
log is generated, see Browse for a similar example. If these log Journal
entries are fairly slow or large to generate (my quick test here shows
they are at least quite slow) both alerts can be used as 1) gives the user
a chance to cancel, and 2) lets the user know when it has completed, just
like the existing design in Browse.
--
Ticket URL: <http://bugs.sugarlabs.org/ticket/2917#comment:8>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system
More information about the Bugs
mailing list