Olog

Olog 1.2 is released

Posted in Adobe Flash, Olog on September 8th, 2010 by Øyvind – Be the first to comment

Since the last update, I’ve slowed down on the public updates and let each change sink in an mature a bit to make sure it works as expected. That explains the jump from version 1.1 to version 1.2. Download/checkout here.

New in version 1.2:

Features:

  • Added shorthand function otrace()
  • Added utility function breakPoint() for logging virtual break points
  • Added utility function nullFunction for use in yet to be assigned callback situations
  • Added utility fucntion getCallee() for returning the string of a point in the call stack
  • Added utility function noMethodBodyWarning() for indicating an empty method and its position
  • Log messages from Olog itself now have a proper origin
  • More thorough introspection when using describe method. More properties found.
  • Added automatic regular trace output via property enableRegularTraceOutput
  • Added memory usage display in title bar
  • Update check is off by default
  • Describe robustness
  • More info when tracing runtime info
  • Added line wrapping preference
Fixes:
  • Resolved issue where prefs pane would stay open after minimizing
  • Resolved issue with filtering on log level
  • General stability fixes
  • More compressed log statements with IOErrorEvents
  • Resolved text coloring and object name bug with describe

Olog – finally.

Posted in AILogger, Adobe Flash, Olog on March 8th, 2010 by Øyvind – Be the first to comment

Olog (formerly, AILogger formerly OKtrace, formerly text field on stage..) is a logging utility I have been using since the early days. The previous version, AILogger has been the most feature rich to date. But over the years a need to rewrite the whole thing has been growing more and more urgent. It actually started life as an AS1 text field on stage, and was then made into an AS2 class which was then refactored for AS3. But after a while it became evident that it had been patched up too many times to do new things and was in desperate need of some overhaulin’.

It’s about time it took its name from its father as well, so I’m abandoning the scheme of naming it after my employer. (OKTrace = Okular, AILogger = Allegro Interaktiv). It has always been my pet project, so I’m taking it with me everywhere I go from now on. I also wanted a short name, seeing as I’ll be typing it a lot, so Olog it is (the “O” from Oyvind).

So this time it’ll be different, I promise! Olog 0.9 is actually AILogger 1.2 and then some in terms of features, but the first step in making it was “File > New”. It’s completely rewritten, and no copy-paste this time. It has been tagging along during my latest project and so it has seen plenty of action already. I’ve tested it quite thoroughly, but it’s hard to say what happens when you try to live on your own for the first time. That’s why I have humbly versioned it 0.9b for now.

New features

Here are some new things you might like:

  • Full featured window interface. Minimize/maximize/close buttons, double click on title bar to minimize. Moveable and resizable.
  • Selective line numbers, time-since-movie start and clock time for each line. These can all be turned of or off during run time.
  • Filtering of log levels. Pressing number keys 0-5 filters the log to show only those severity levels (color). Esc to escape.
  • Automatic update check. Olog will check for a new version once a week if you let it and notify you if there’s a newer version.
  • Save log to text/XML.
  • Persistent window state. Position, size, minimized/maximized state is remembered so you don’t have to keep moving it out of the way each time you compile.
  • Run time markers. Set a new named point-in-time marker, which you can later complete to display load/execution times.
  • Support for AILoggerEvents, but Olog has it’s own OlogEvent as well for loosely coupled logging.
  • Stacking of repeated messages.
  • Full ASDoc documentation.

The olog page on my blog has all the links you need, direct ZIP download, SVN repo access, asdoc documentation, Google Code homepage and even a simple demo. I’ll love to hear it if you have feedback!