0000083: Implement Textual information about what AoM is doing in the Log View - AniDB Bug Tracker

ID	Project	Category	View Status	Date Submitted	Last Update

0000083	AOM	Feature Request	public	2005-01-24 13:53	2016-09-03 12:14

Reporter	fahrenheit	Assigned To	petriw
Priority	normal	Severity	feature	Reproducibility	N/A
Status	new	Resolution	open

Summary	0000083: Implement Textual information about what AoM is doing in the Log View
Description	This is the current log view: [-] AniDB Status: .....\|- Connection Status: lsStatus [-] Downloads: .....\|- Current Download: XX,xx MB / XX,xx MB downloaded. .....[+] Schedule Downloads: X items remaining. (XXX.xx MB remaining.) Well when there is a big dump file downloading, then parsing, then decrypting then unpacking and then processing. Although there is the info of what the item is doing and the AniDB update bars are growing, i was wondering if it's worty including an extra tree in the log view, like: [-] AniDB Status: .....\|- Connection Status: Disconnected [-] Downloads: .....\|- Current Download: XX,xx MB / XX,xx MB downloaded. .....[+] Schedule Downloads: X items remaining. (XXX.xx MB remaining.) [-] AoM Status: .....\|- lsAOMstatus_item: lsAOMstatus_work (lsAOMstatus_subwork XXX% complete) where, lsAOMstatus_item is a name for the item that is being worked (like AniDB dump file); lsAOMstatus_work is the work type (processing, unpacking, etc); lsAOMstatus_subwork is for when there is a sub item being done an example with names: [-] AoM Status: .....\|- AniDB dump file: Processing (Genres 55% complete) Its redundant information to some extent because most of the info it's all ready there, but the ideia of giving names to what is being done isn't so redundant.. Well, comments on this feature request?
Tags	No tags attached.

Date Modified	Username	Field	Change
2005-01-24 13:53	fahrenheit	New Issue
2005-01-25 03:27	petriw	Assigned To	=> petriw
2005-01-25 03:27	petriw	Status	new => acknowledged
2016-09-03 12:14	DerIdiot	Status	acknowledged => new