Hi All,
I had a productive day of coding and added a nice feature which
justifies a 2.1 release in the coming days. I've added a logging
monitor to Luma which shows critical errors, debugging data and
general information about performed LDAP operations.
Additionally unhandled exceptions, which are coding errors on my side,
are logged, too. Normally a user would only know that such an error
happened by looking at the console. This often meant to restart Luma
and reproduce all the steps needed for the error. With the help of
some Python magic this is no longer needed.
Users can open the logger from the 'Program' menu entry or by clicking
the 'bomb'-icon in the status bar. The icon is only showed, if
critical errors occured. The logger can be placed anywhere inside the
Luma main window by grabbing the handle with the mouse. It is possible
to create a second window by moving the logger outside.
Here's a screenshot how this stuff looks like:
http://home.tu-clausthal.de/~ifwd/luma/screenshots/logger.png
The tarball for this is at
http://home.tu-clausthal.de/~ifwd/luma/luma-2.1pre3.tar.bz2
My plan for the coming months, is to have a faster release cycle. One
option would be, that I do releases without waiting for translations.
Instead I'll do minor releases as translations come in. The bugfix
releases for 2.0 showed that this should be no problem.
But before I do that, I wanted to hear about your opinions on this.
For translators: The updated translation files can be found at
http://home.tu-clausthal.de/~ifwd/luma/translations/ . This time only
6 strings have to be done :)
Happy testing,
Wido
--
Wido Depping
ICQ: 51303067 AIM: wido3379
Jabber: wido@xxxxxxxxxxxxx
Blog: http://widoww.blogspot.com
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
|
