charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.3000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300
X-Server: Indy SMTP Server
X-Library: Indy 9.00.10
N7 wrote:
|| I was wondering if anyone can point me in the right direction for
|| building my own set of emoticons.
|| Building the DLL and adding it into Exodus.
oh... this is uber-bleeding-edge :) I haven't written any docs yet since this
stuff is ONLY in the daily builds. Basically, you need an XML description file,
which is basically a JEP-38 formatted file. The MSN one is here:
http://www.jabberstudio.org/cgi-bin/viewcvs.cgi/exodus/exodus/msn-emoticons/icon
def.xml?rev=1.2&view=auto
Then you need a RC file which basically allows a resource compiler to compile
all of your stuff into a .RES file.. The MSN one is here:
http://www.jabberstudio.org/cgi-bin/viewcvs.cgi/exodus/exodus/msn-emoticons/msn.
rc?rev=1.2&view=auto
The most important bit here is that you include the icondef.xml file as an XML
resource, with the name of "icondef". This is what Exodus looks for when it
loads everything up. If you've got a win32 compiler, chances are you have a
resource compiler. With delphi, you run brcc32.exe msn.rc, and you get msn.res.
Then you create a DLL project in your favorite build environment which includes
that .RES file that you just compiled. In Delphi, the MSN project file looks
like:
http://www.jabberstudio.org/cgi-bin/viewcvs.cgi/exodus/exodus/msn-emoticons/msn_
emoticons.dpr?rev=1.1&view=auto
Once this project is built, you have your DLL.
FWIW, I'm planning on adding the ZIP file support that JEP-38 uses shortly. So
you'll just be able to build a ZIP file which contains the icondef.xml, and all
of the emoticons. We wanted to the DLL thing for our standard emoticons, and to
build the framework. It was easier to start with that than to add the complexity
of the ZIP stuff in there as well.
pgm.