FR: Parse the actual logfiles to become more like LogSaw and the native Error Log in Eclipse

[GoogleCodeExporter]

Hi,

Liking the LogViewer, but I think it could be approved greatly.

If you look at the LogSaw project or at the native Error Log in Eclipse, they 
sort of know the content of the actual logfile, they handle the content of the 
file not as plain text.

They seem to parse the log files and aggregate the content in the file so 
instead of a plain text view, you get a grid with log entries, on which you can 
click to see the details.

When LogViewer would support such stuff, it'll be an even more handier tool. As 
an added bonus, it would be nice to then be able to also configure when the Log 
viewer should be activated. Currently, it is either never, or when something is 
appended to the log. I'd like it to activate itself only when something is 
appended to the log when it's of a certain logging level or higher, for 
examples only on errors.

Just some thoughts...

K.

Original issue reported on code.google.com by Kyd...@gmail.com on 18 Nov 2010 at 9:38

[GoogleCodeExporter]

Hi,

yes the idea is good, see issues 24, 47 and 48 too. The problem is in the core 
of this plugin, it's not easy to extend it for such contents, because the RegEx 
rules are evaluated in the UI-context. So, we have also performance issue (see 
issue 35)
I already started redesign of core plugin.

I think i can put effort into this issue later for version 1.1 

Regards,
Andre

Original comment by andre.bo...@gmail.com on 18 Nov 2010 at 8:15

• Changed state: Accepted
• Added labels: Component-UI, Milestone-Release1.1, OpSys-All, Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Original comment by andre.bo...@anbos.de on 29 Sep 2012 at 7:05