Opened 13 years ago
Closed 12 years ago
#2915 closed enhancement (fixed)
Log: reorganize toolbar
| Reported by: | godiard | Owned by: | garycmartin |
|---|---|---|---|
| Priority: | Unspecified by Maintainer | Milestone: | Unspecified |
| Component: | Log | Version: | 0.92.x |
| Severity: | Unspecified | Keywords: | |
| Cc: | Distribution/OS: | Unspecified | |
| Bug Status: | Unconfirmed |
Description
Log need reorganize the toolbar and improve the UI.
The Copy button in the main toolbar, and the delete log in the Remove button in the Custom subtoolbar must be moved to a new Edit toolbar.
The Log collector must be moved to the activity subtoolbar, probably with a export icon, the loupe is for zoom. The Custom (gear) icon must be removed.
Change History (5)
comment:1 follow-up: ↓ 2 Changed 13 years ago by garycmartin
- Owner changed from wadeb to garycmartin
- Status changed from new to assigned
comment:2 in reply to: ↑ 1 ; follow-up: ↓ 3 Changed 13 years ago by godiard
Replying to garycmartin:
Thanks, yes good, long overdue, suggestions.
The Log collector needs more thought/work as the backend server was taken offline a long time ago. We might decide to re-instigate the backend server (php script I think) on Sugar Labs infrastructure (and agree some way to manage/process all the potential data); or perhaps switch to a low tec solution could be a simple 'export log as text' option so you can quickly put a single log into the Journal were you can easily reference it later if needed (real logs files are removed when you re-boot), or attach it to an email or bug ticket using the ObjectChooser.
Right now, thee send of information to the server is disabled, and a zip file with the logs information (and information about the system) is created in the Log. Later the user can attach this file to a mail/ticket, etc.
comment:3 in reply to: ↑ 2 ; follow-up: ↓ 4 Changed 13 years ago by garycmartin
Replying to godiard:
Right now, thee send of information to the server is disabled, and a zip file with the logs information (and information about the system) is created in the Log. Later the user can attach this file to a mail/ticket, etc.
It does? What version of Log are you using? Log-24 as found on ASLO or a private fork? Does this match with the v24 rep in http://git.sugarlabs.org/log I see your merge request but don't think it is officially in mainline.
comment:4 in reply to: ↑ 3 Changed 13 years ago by godiard
Replying to garycmartin:
Replying to godiard:
Right now, thee send of information to the server is disabled, and a zip file with the logs information (and information about the system) is created in the Log. Later the user can attach this file to a mail/ticket, etc.
It does? What version of Log are you using? Log-24 as found on ASLO or a private fork? Does this match with the v24 rep in http://git.sugarlabs.org/log I see your merge request but don't think it is officially in mainline.
I have merged in master the changes from James. This changes are only in git now, we need release them.
comment:5 Changed 12 years ago by godiard
- Resolution set to fixed
- Status changed from assigned to closed
Already reorganized in version 27
Thanks, yes good, long overdue, suggestions.
The Log collector needs more thought/work as the backend server was taken offline a long time ago. We might decide to re-instigate the backend server (php script I think) on Sugar Labs infrastructure (and agree some way to manage/process all the potential data); or perhaps switch to a low tec solution could be a simple 'export log as text' option so you can quickly put a single log into the Journal were you can easily reference it later if needed (real logs files are removed when you re-boot), or attach it to an email or bug ticket using the ObjectChooser.