[request] message concept for stdout/stderr --- use 1.1.4+
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SikuliX |
Fix Released
|
Undecided
|
RaiMan |
Bug Description
1.1.0: many improvements, but ongoing effort
1.2. new logging concept
-------
Sikuli X all platforms
Especially when running Sikuli scripts in a way, that you have access to stdout/stderr (e.g. using sikuli-script.jar standalone) you find differently styled messages.
This is an example:
Sikuli vision engine loaded.
Text Recgonizer inited.
Mac OS X utilities loaded.
VDictProxy loaded.
EventManager loaded.
[safarihelpers log] imported
PyramidTemplate
[log] highlight Match[4,26 61x13] score=0,72, target=center for 2.0 secs
2011-01-05 09:34:48.682 java[35565:d07] bringWindowToFront: <CocoaAppWindow: 0x10018c230>
PyramidTemplate
[log] highlight Match[4,26 61x13] score=0,72, target=center for 2.0 secs
2011-01-05 09:34:50.873 java[35565:d07] bringWindowToFront: <CocoaAppWindow: 0x1006718b0>
[debug] close all ScreenHighlighter
The only user generated message is [safarihelpers log] imported
proposal:
every Sikuli generated message look like
[sikuli type] time-stamp generating-source message
where "type" signals the severity (log, debug, info, warning, error, ...)
time-stamp and generating-source only when needed for whatever purpose
advantages:
- sikuli messages could be filtered out (find messages not starting with [sikuli)
- a user could adopt the systematic and have e.g. a filter for errors (e.g. find error messages with regex ^.*?error\])
- even in the IDE message area it would be easier to identify simple user generated print output
BTW:
the stderr message
PyramidTemplate
does not really "talk" to a user ;-)
see https:/
Changed in sikuli: | |
importance: | Undecided → Wishlist |
Changed in sikuli: | |
status: | New → In Progress |
milestone: | none → x1.0-rc2 |
Changed in sikuli: | |
status: | In Progress → Fix Committed |
Changed in sikuli: | |
importance: | Wishlist → Low |
assignee: | nobody → RaiMan (raimund-hocke) |
milestone: | x1.0-rc3 → x1.0 |
tags: | added: general |
Changed in sikuli: | |
status: | Fix Committed → In Progress |
milestone: | x1.0 → none |
importance: | Low → Medium |
importance: | Medium → Wishlist |
Changed in sikuli: | |
importance: | Wishlist → High |
milestone: | none → x1.1 |
Changed in sikuli: | |
status: | In Progress → Fix Committed |
Changed in sikuli: | |
milestone: | 1.1.0 → 1.2.0 |
description: | updated |
Changed in sikuli: | |
milestone: | 2.0.0 → none |
importance: | High → Undecided |
status: | Fix Committed → Won't Fix |
status: | Won't Fix → Fix Released |
summary: |
- [request] message concept for stdout/sterr + [request] message concept for stdout/sterr --- use 1.1.4+ |
summary: |
- [request] message concept for stdout/sterr --- use 1.1.4+ + [request] message concept for stdout/stderr --- use 1.1.4+ |
In RC2, most messages have a prefix that can be turned off. Some low-level messages in the vision engine will be removed in RC3.