It looks a lot better than previous version and no need to change anything to migrate new version. Congrats pagullo, thanks for sharing and these improvements!
I plan to add some extra functionality soon, including searching & highlighting text in the grid (regular expressions allowed) and remote logging -that will take a bit more time. The idea is to do it all without api changes, as has been the case for transition from 0.9 to 1.0.
It doesn't appear to work in MS-IE (Version 8 at least).
When I have the (latest) log4js-ext-all.js running in my app I get a "console is undefined" error in MS-IE.
Now I know I could load this at run time based on the browser type but it would really be helpful to have some type of logger which works in both MS-IE and Firefox (as well as Chrome).
If nothing else a check in the log4js code to see if the console exists and not generate an error if it's not available. That would at least prevent the error from occurring if the user is running MS-IE.
Can you provide me with the steps that lead you to experience the problem?
I test the system against the latests versions of Firefox, Explorer, Chrome and Safari before release, all of which I intend to support, and haven't found any problem.
Just double checked right now against IE 9 by running the examples & the automated tests (in case something got awry with the release) and got no problem.
Ok, it seems to be a difference between IE 8 and 9. In IE 8 the console is not there unless you open the dev tools
Mike, will you be so gentle as to check whether the attached version works for you with IE 8? Can't test it, as I already have IE 9 installed...
Thanks Pedro, that solved my problem!
Thanks for the fast response on this!
Now the question is does this also work on IE-7, or at least have a "ignore if no console" ability for versions of MS-IE that did not have developer tools?
I'm 99.99% sure that this should work with all versions of IE for which ExtJs 4.x works, IE 7 included.
For full disclosure, let me tell you that I haven't tested this for IE 7. As you know, it can't coexist with IE 9, which is my automated test target when it comes to IE, and that makes testing compatibility with older IE versions a chore.
As an aside... if you (or others!) consider I'm doing a good work, I would love it if you could vote the thread up andstar the project in google(this is even more important), as this is the best way to make log4js-ext popular and worth the effort .
While I intend to keep it for my own use, turning things into a project (i.e., taking the effort to support IE 8, even though I will probably never target it, adding a wiki, etc.) requires double the effort and is reasonable only if log4js-ext is used by many users. The higher the project visibility, the higher the number of users -if the community think it adds value, of course
As an aside... if you (or others!) consider I'm doing a good work, I would love it if you could vote the thread up andstar the project in google(this is even more important), as this is the best way to make log4js-ext popular and worth the effort .
Regards,
Voted up and Starred! Glad to help, and thanks for a neat little logger.
MikeB
Version 1.0.1 is backward compatible with 1.0: you should be able to upgrade to the latest version without running into incompatibilities.
Unfortunately, the documentation is not inline due to googlecode hosting limitations: to take a look at it, open index.hml in the installation directory and click the API documentation link.
Version 1.0.1 provides a fix for IE 8, too, so that log4js-ext works ok when the development tools are not active.
"People will never forget how you made them feel."
Originally Posted by pagullo
Ok, it seems to be a difference between IE 8 and 9. In IE 8 the console is not there unless you open the dev tools
.
Reply With Quote
