sikuli-driver team mailing list archive

[RaiMan <rmhdevelop@xxxxxx>]

** Changed in: sikuli
    Milestone: 1.1.0 => 1.2.0

** Description changed:

+ 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
  PyramidTemplateMatcher: source is smaller than the target
  [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>
  PyramidTemplateMatcher: source is smaller than the target
  [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, ...) 
+ 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
  PyramidTemplateMatcher: source is smaller than the target
  does not really "talk" to a user ;-)
  see https://answers.launchpad.net/sikuli/+question/140198

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/697604

Title:
  [request] message concept for stdout/sterr

Status in Sikuli:
  Fix Committed

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
  PyramidTemplateMatcher: source is smaller than the target
  [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>
  PyramidTemplateMatcher: source is smaller than the target
  [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
  PyramidTemplateMatcher: source is smaller than the target
  does not really "talk" to a user ;-)
  see https://answers.launchpad.net/sikuli/+question/140198

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/697604/+subscriptions