[mICQ] History file format or getting out the history directly

Rüdiger Kuhlmann micq-list-CKH1bDCG6x4V at ruediger-kuhlmann.de
Fri Apr 6 14:50:41 CEST 2007


>--[Alexander Dahl]--<post at lespocky.de>

> didn't find anything. :( Can somebody give me a hint to find the right
> location in either documentation or source code?

Originally rtc spent some thought on it. He even made some Tcl scripts to
operate on logs that are in the contrib dir. Ah, here: doc/README.logformat
However, I might have broken that with my Jabber changes. The function
to write into the log is in src/util.c and called putlog().

> For further development it's imaginable to directly send the history
> events (mostly messages) to the central impuls daemon. Is there a way to
> get messages out of micq?

Well, with current CVS, any status change or incoming message will be
dispatched to a set of function with a common signature. One for the
logging, one for the message history, one for the text UI, one for user
shell script, etc. Though there is no plugin mechanism.

> This could be possibly done with the TCL
> scripting interface for incoming messages, couldn't it? But what about
> outgoing messages?

Different function. But currently Tcl is not called from there.
That could be changed, though.

However, for Jabber, I'm not sure if I'm yet content how it is handled,
but a la, I don't use Tcl as I don't speak that language.

> If this could be done with some existent interface of
> micq 0.5.2, is there somewhere more documentation than on
> http://www.micq.org/docs/micq.7.html.de ?

http://www.micq.org/docs/micqrc.5.html.de
event <script>

... also sort of defines the arguments sent to the event script.

-- 
 If you lose your power to laugh, you lose your power to think.


More information about the mICQ-List mailing list