0001642: Automation of Scan-Load-check operations

(0000979)
poutnikg (reporter)
2012-07-22 19:09

typo: .....at update checks.

(0001125)
poutnikg (reporter)
2012-08-17 12:18

E.g. by implementation of these optional startup items offers,
done in given order :

- SUMO update check at startup ( offered download and closing, later even autoupdate )
- Scan at startup
- Load at startup
- Check at startup

(0001126)
Kyle_Katarn (administrator)
2012-08-17 14:11

OK

(0001130)
bytehead (updater)
2012-08-17 20:38
edited on: 2012-08-18 01:07

Thanks poutnikg, I wanted to propose the same thing long time ago.

In general, all SUMo algorithms should be optimized and made faster, and not redundant at the very least. Combining Load/Check and Scan/Check pairs into single step operations is the first thing that should be done in this respect.

I also propose to add some command line flags that override default settings at start-up. I'd like to be able to configure 2 different shortcuts for SUMo:

1) to quickly load and check previously scanned items on start-up (if local DB is empty, do full rescan first in the user-set default mode);
2) to force full *rescan* and then check everything on start-up (with different flags for quick/thorough/custom scanning modes).

(0001313)
poutnikg (reporter)
2012-11-02 11:12

Related to 0001583: SUMO silent mode until updated list is ready
http://www.kcsoftwares.com/bugs/view.php?id=1583 [^]

Issue History
Date Modified	Username	Field	Change
2012-07-22 19:07	poutnikg	New Issue
2012-07-22 19:09	poutnikg	Note Added: 0000979
2012-07-22 22:15	Kyle_Katarn	Assigned To	=> Kyle_Katarn
2012-07-22 22:15	Kyle_Katarn	Status	new => acknowledged
2012-07-28 12:11	bytehead	Tag Attached: UX
2012-08-17 12:18	poutnikg	Note Added: 0001125
2012-08-17 14:11	Kyle_Katarn	Note Added: 0001126
2012-08-17 20:38	bytehead	Note Added: 0001130
2012-08-18 01:07	bytehead	Note Edited: 0001130	View Revisions
2012-10-20 12:58	bytehead	Relationship added	related to 0000809
2012-10-20 13:53	bytehead	Priority	normal => high
2012-11-01 16:38	Kyle_Katarn	Relationship added	related to 0001619
2012-11-02 11:12	poutnikg	Note Added: 0001313
2012-11-02 22:37	bytehead	Relationship added	related to 0001583
2012-12-29 19:14	Kyle_Katarn	Relationship added	related to 0001881
2013-01-07 01:05	bytehead	Relationship added	related to 0001565
2013-01-13 00:26	Kyle_Katarn	Status	acknowledged => resolved
2013-01-13 00:26	Kyle_Katarn	Fixed in Version	=> 3.5
2013-01-13 00:26	Kyle_Katarn	Resolution	open => fixed
2013-01-13 00:28	Kyle_Katarn	Relationship deleted	related to 0001619

Notes
(0000979) poutnikg (reporter) 2012-07-22 19:09	typo: .....at update checks.

(0001125) poutnikg (reporter) 2012-08-17 12:18	E.g. by implementation of these optional startup items offers, done in given order : - SUMO update check at startup ( offered download and closing, later even autoupdate ) - Scan at startup - Load at startup - Check at startup

(0001126) Kyle_Katarn (administrator) 2012-08-17 14:11	OK

(0001130) bytehead (updater) 2012-08-17 20:38 edited on: 2012-08-18 01:07	Thanks poutnikg, I wanted to propose the same thing long time ago. In general, all SUMo algorithms should be optimized and made faster, and not redundant at the very least. Combining Load/Check and Scan/Check pairs into single step operations is the first thing that should be done in this respect. I also propose to add some command line flags that override default settings at start-up. I'd like to be able to configure 2 different shortcuts for SUMo: 1) to quickly load and check previously scanned items on start-up (if local DB is empty, do full rescan first in the user-set default mode); 2) to force full rescan and then check everything on start-up (with different flags for quick/thorough/custom scanning modes).

(0001313) poutnikg (reporter) 2012-11-02 11:12	Related to 0001583: SUMO silent mode until updated list is ready http://www.kcsoftwares.com/bugs/view.php?id=1583 [^]