Ryzom

kostika wrote:That seems like alot of extra work for jsut replacing a simple thing like You say With Kostika says. Would be easier to jsut use notepad to do it without the extra fiddliness. (which is what i normally do)

The only benefit of the replace.txt file is that it can have as many entries as you want, so if you always wanted to replace a bunch of abbreviations with full words, or something like that, then it would do it all in one swell foop instead of multiple replaces in Notepad.

lathan wrote:I guess you could check on the log's creation time/date and its last edited time/date, and if the two are sufficiently close together assume that the log's in its original format, otherwise ignore the list of people talking in the log. Although that seems like it might be a bit OTT for the sake of an orphaned menu item!

hehe. It's not actually an orphaned menu item - it's a toggle for chat lines that don't have a speaker that the program recognizes. You will see it also in logs for events where the CSRs use line breaks in their speeches.

kostika wrote:I'm jsut breaking his program

I can't actually think of any uses for the user filtering.

Turning off spammers in an event log was what I had in mind .

[Edit: ... though you could also use it to locate something a particular person had said, by turning everyone off and then just turning that one person back on .]

Hehe, actually Richky isn't the only one who is (re)inventing the wheel.

At the moment I'm writing a similar program, with a slight different focus on reformatting a chatlog-file to a text with BBCode compatible colorcodes.
E.g. if you want to post an event log oder the log of your last guildmeeting in your guilds forum.
So something like that could be usefull, save for Kostika with her edited logfiles.

@Richky:
I took the freedom and run two of my testcases against your program and discovered a few glitches.

• When opening the chatlog, your program seem to be using the default ascii-7 codepage and thus filtering out all the special chars.
  But the chatlog seems to support at least western europe special chars, so a codepage like in

  Encoding codePage = Encoding.GetEncoding(1252);

  could fix this.
• I managed to crash it with one of my logfiles with old entrys.
  Before May 2005 no colorcode (e.g. @{AABB} ) existed and during May the colorcodes where different from now.
  I looks like, you were relying on the existens of the new codes.
  The codes used during May seem to be the problem.

Apart from this: good work!

When I started the programming of my tool, I never thougth of competition.


Carfesch

schlo01 wrote:At the moment I'm writing a similar program, with a slight different focus on reformatting a chatlog-file to a text with BBCode compatible colorcodes.

simple find @{RGBA} from text replace it with #RAGABA in output (well.. for html anyway, dunno about bbcode)

anyway, if all already writing those, then dont forget to add little statistic based log file (xp gained per level, mobs killed, mats looted/foraged, items crafted, crafting success rate, etc

blaah wrote:simple find @{RGBA} from text replace it with #RAGABA in output (well.. for html anyway, dunno about bbcode)

In short thats what my tool will do with the logfile.
A bit more flexible maybe, and yes html-output is possible.

The conversion part ist finished, atm I'm working on the gui, i18n and tooltips/helpfile.

The statistics, you like to see, fit better in Richkys tool I think.

Carfesch

schlo01 wrote:The statistics, you like to see, fit better in Richkys tool I think.

no offence to Richky, but his tool choked on 24k lines already... and i have close to 2 mil in my logfile (atm, 1598139)

statistics was just a suggestion , my bot is already spiting out lot of info, so i see it already.

blaah wrote:no offence to Richky, but his tool choked on 24k lines already... and i have close to 2 mil in my logfile (atm, 1598139)

I am afraid Sir, but you are crazy.

I've made a testfile with ~2 mil lines, which totals to 130 MB in size.
The tool needed about 3 minutes to work through using up to 200 MB ram, normally I'm testing with a chatlog with ~75K lines (with a processing time of a few seconds).
And to be honest, the richtext control I'm using wasn't taking this amount very well either and responded slowly when I tried to modify the output.

But I can't imagine your webadmin will be happy if you post ~2 mil lines in a single posting.
People got killed for less.


Carfesch

schlo01 wrote:[*]When opening the chatlog, your program seem to be using the default ascii-7 codepage and thus filtering out all the special chars.
But the chatlog seems to support at least western europe special chars

Interesting - it displays all that stuff just fine on my machines. I'll have to muck with it some more.

schlo01 wrote:[*] I managed to crash it with one of my logfiles with old entrys.
Before May 2005 no colorcode (e.g. @{AABB} ) existed and during May the colorcodes where different from now.
I looks like, you were relying on the existens of the new codes.
The codes used during May seem to be the problem.

Yep, that would cause a problem. I don't think it is one I will worry about though unless they change the codes again.

schlo01 wrote:Apart from this: good work!

When I started the programming of my tool, I never thougth of competition.

Thanks . I just wanted a way to take an event log and quickly filter out all but the important bits, and writing a program to do it was more fun than doing it manually .

logs + ultra-edit32 + macro -> http://gsm-community.de/eventlogs/ :>

nice program for analyzing chat sessions and looking for certain kinds of informations. a few suggestions tho:
- coloring the lines as per channel would be neat
- it seems to filter out äöü and similar characters
- with speaker filter on it still displays all the spam of the sysinfo channel, when activating that, might want to add another mode there to only display sysinfo regarding the character that is being filtered for
- a general search filter would be nice: enter word, only display lines with that word

thanks for your work =)