» home
» bugs
» git

Viewing Issue Simple Details Jump to Notes ] View Advanced ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0000013 [litestep core] core feature always 2006-05-04 15:42 2009-03-12 18:59
Reporter phil View Status public  
Assigned To
Priority none Resolution open  
Status feedback   Product Version CVS-trunk
Summary 0000013: Logging, please!
Description Logging is very handy to diagnose various failures in LS. The ideal logging system would do some of the following :

- Disable message boxes of severity less than or equal to the current logging level. Top logging mode would disable all message boxes.
- Provide similar, more informative error information stemming from RC code issues (e.g. conditionals)
- Export the logging implementation for use by external modules.
Additional Information
Tags No tags attached.
Attached Files

- Relationships
child of 0000092feedback LiteStep 0.26.0 - Release 

-  Notes
(0000023)
jugg (manager)
2006-05-06 20:22

I agree, we need to have better logging support. This is definitely something we are looking to add into the next major release (off of CVS-trunk). However, we need to discuss if there is any level of support we want to add back into the 0.24.x series. Anyone have input?
(0000038)
phil (reporter)
2006-11-11 14:18

Given the general lack of progress on this, and the rather limited community effort for complex themes, maybe this is unwarranted. If more people were developing more heavily engineered themes this would be more of an issue. They aren't; it's probably not worth the developer time to implement logging.
(0000039)
phil (reporter)
2006-11-11 14:19

s/progress/feedback
(0000061)
ilmcuts (manager)
2007-07-23 11:45

A logging API shouldn't show message boxes in the first place.
(0000170)
alur (developer)
2009-01-10 17:58

This is definitively something that would that would improve the overall experience with LiteStep. Some configurations/modules will throw excessive amounts of message boxes when something goes wrong horribly wrong (variables which aren't set, some other module didn't load, the themer failed to include a .rc file, etc...).

However, I still think that there is a need for some message boxes(it should be optional though). For things such as bang commands failing, to notify the user that something they just did failed.

I think a log section in the !about window could be neat, as well as a LiteStep.log in the LiteStep directory.
(0000256)
jugg (manager)
2009-03-12 18:59

The logging facility should not provide a UI. However, another interface may/should be implemented that can be used to monitor the log, and based on some configuration, do something in response to a log event. Such a montior system should be implemented independently, and certainly would not have to be part of the core.

- Issue History
Date Modified Username Field Change
2006-05-04 15:42 phil New Issue
2006-05-06 20:22 jugg Note Added: 0000023
2006-05-06 20:22 jugg Status @10@ => feedback
2006-11-11 14:18 phil Note Added: 0000038
2006-11-11 14:19 phil Note Added: 0000039
2007-07-23 11:45 ilmcuts Note Added: 0000061
2008-04-22 12:51 jugg version CVS-024x => CVS-trunk
2009-01-10 17:58 alur Note Added: 0000170
2009-03-05 15:10 ilmcuts Relationship added child of 0000092
2009-03-12 18:59 jugg Note Added: 0000256


Copyright © 2000 - 2009 Mantis Group
Powered by Mantis Bugtracker