Log: collector UI needs improvement

[godiard]

The UI for the collector is not clear.

The button used to collect the information is in a palette, the user must do click with the secondary button and later do click in this button. This is not intuitive, the user try to collect the information doing click in the collect button, and there are not feeeback.

The button must collect the information when you click (also the loupe icon is not good, is better use a export icon. See #2915)

When the collection is generated the activity must show a alert with a button to see the object in the Journal, like Browse or GetBooks.

[garycmartin]

Log collection attempts to send to a remote server (off line for a long time now), and will just raise an error dilaogue if you click it currently. See ​http://bugs.sugarlabs.org/ticket/2915#comment:1 for an alternative suggestion (export current log file as a text object to the Journal for later use/reference).

Agreed about the current UI design, but think we should agree on how the feature should work before trying to polish.

[godiard]

Update: See update in #2915, the collector is not sending information to a server, is saving to the journal

[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"?

[garycmartin]

Replying to 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.

[godiard]

I have modified Log to open the full palette when the user click the collect button. This solves part of the problem. Also we already changed the icon.

The pending part is add a alert asking confirmation or notifying the user the file was created in the journal. From my point of view, we need check how much time takes generate the entry in the journal, if is slow, ask confirmation, if not a message when finish is ok.

[ignacio]

​http://www.google-melange.com/gci/task/view/google/gci2013/6187250966593536