sfsdfd
Joined: 02 Sep 2011
Posts: 3
|
 Posted: Fri Sep 02, 2011 1:43 pm Post subject: Better VVScheduler user interface? |
 |
|
VVScheduler is an extremely handy tool. However, its user interface could use a lot of work.
For example:
1) VVScheduler shows the results of a job as a pop-up window with a report. Unfortunately, this behavior is more suited for a user-facing application than a daemon that's supposed to run in the background and do its job. It would probably be helpful to use the notification area / system tray to indicate that VVScheduler has something to say, rather than spontaneously popping up a report.
2) The reported information is... well... kind of ugly. The reporting window is just a text dump, and the application log is LITERALLY a text dump.
Of course, ViceVersa, like many apps of its nature, records a lot of information. Most apps therefore feature event logs with a lot of filtering options: show results by date, by task, etc.
3) VVScheduler include a pretty nice set of options to specify the conditions under which a task should be executed - at a certain frequency and time of day, when the machine is idle, when the machine is on A/C power, etc. However, when VVScheduler doesn't run a task, it doesn't report or record anything! It just remains totally silent.
Things that VVScheduler should probably do when a task doesn't execute:
a) Alert a user when a job didn't run. (Again, a notification area icon is a great mechanism for this.)
b) Alert the user more pointedly when a periodic job has failed to execute several times in a row (e.g., "the last (x) attempts to execute this task failed...") - better still, allow the user to specify the value of (x).
c) Tell the user WHY the job didn't run (e.g., because CPU utilization was high, or because user input had been recently received).
d) Give the user the option of retrying the task, tweaking the settings of the task or profile, or just disabling the task altogether. |
|
ViceVersa HOME 
Forum FAQ
Search Forum
Register
Profile
Log in
