Hi
I think there is a problem if we have two types of plugins. Up to now
the plan is to have protocol plugins and gui plugins. I don't really
know why this classification is done but I think the difference between
them is the type of event they work with. Is that true?
I can identify two main types of events. One type is passed from the
daemon to the protocol plugins. It consists of IP address and the data
of the IP packet, let's call it LicqIpEvent. The second type is send
from protocol plugin to gui plugin. Here the uid, ppid and so on are
available, let's call it LicqUserEvent.
If we have these two main classes of events we can say all plugins which
handle LicqIpEvent are called protocol plugins. The rest is called gui
plugin. That means:
protocol plugin = ssl, icq, msn
gui plugin = gpg, guis, spellchecker, osd
Someone said that when the gui plugin (e.g. qt-gi) wants to send a
message it sends it to the protocol plugin. But that's not possible. If
I want to use GPG is must be send to the gui plugins first and then to
the protocol plugins.
I think it's better not to make a difference between protocol and gui
plugins. All plugins simply receive and send events. So the daemon
should handle all the same way. That means sending all events can look like
daemon->pushToProto("send-message", pMsgData);
Here pMsgData can be a void* or a base class which inherits LicqIpEvent
and LicqUserEvent.
What do you think?
rsLeo
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Licq-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/licq-devel
