Blackbird - Open Source JavaScript Logging Utility
gscottolson.com
Blackbird - Open Source JavaScript Logging Utility
1–10 of 12 posts
Re: Blackbird - Open Source JavaScript Logging Utility
#2Re: Blackbird - Open Source JavaScript Logging Utility
#3Besides the different logging levels, I don't think this brings much improvement over console.log. I think I'll stick with that.
Re: Blackbird - Open Source JavaScript Logging Utility
#4Re: Blackbird - Open Source JavaScript Logging Utility
#5Re: Blackbird - Open Source JavaScript Logging Utility
#6On a side note, I've wondered how useful/practical server-side logging of js running client-side would be. For keeping track of what your users are doing, errors thrown etc.
Re: Blackbird - Open Source JavaScript Logging Utility
#7Isn't this what Tapestry uses for client side error messaging? It's actually pretty useful for including in web-app frameworks: you can alert the developer to framework errors which might go un-noticed if just written to console.log. Of course you can disable in production. On a side note, I've wondered how useful/practical server-side logging of js running client-side would be. For keeping track of what your users a…
- It would need to be asynchronous
- It would be nice to collect a log locally and send it centrally under specific circumstances (e.g. an error occurs send everything that has been logged so far)
- Using some kind of local storage option might be nice (e.g. the interface to SQLite that WebKit-based browsers have).
Re: Blackbird - Open Source JavaScript Logging Utility
#8You have 2 options: 1 - modify your styles 2 - modify blackbird styles + code
I'll stick to console.log as well but a great tool nevertheless.
Re: Blackbird - Open Source JavaScript Logging Utility
#9Re: Blackbird - Open Source JavaScript Logging Utility
#10Isn't this what Tapestry uses for client side error messaging? It's actually pretty useful for including in web-app frameworks: you can alert the developer to framework errors which might go un-noticed if just written to console.log. Of course you can disable in production. On a side note, I've wondered how useful/practical server-side logging of js running client-side would be. For keeping track of what your users a…
That's not a bad idea. Some suggestions/ideas: - It would need to be asynchronous - It would be nice to collect a log locally and send it centrally under specific circumstances (e.g. an error occurs send everything that has been logged so far) - Using some kind of local storage option might be nice (e.g. the interface to SQLite that WebKit-based browsers have).