1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices Coding] Coding Modules HOWTO:
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Coding%20Modules%20HOWTO%3A&In-Reply-To=000b01c2932c%24aff1d1e0%243d714fd9%40avansys">
8 <META NAME=
"robots" CONTENT=
"index,nofollow">
9 <META http-equiv=
"Content-Type" content=
"text/html; charset=us-ascii">
10 <LINK REL=
"Previous" HREF=
"001742.html">
11 <LINK REL=
"Next" HREF=
"001746.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices Coding] Coding Modules HOWTO:
</H1>
16 <A HREF=
"mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Coding%20Modules%20HOWTO%3A&In-Reply-To=000b01c2932c%24aff1d1e0%243d714fd9%40avansys"
17 TITLE=
"[IRCServices Coding] Coding Modules HOWTO:">achurch at achurch.org
19 <I>Sun Nov
24 14:
36:
07 PST
2002</I>
21 <LI>Previous message:
<A HREF=
"001742.html">[IRCServices Coding] Coding Modules HOWTO:
23 <LI>Next message:
<A HREF=
"001746.html">[IRCServices Coding] Coding Modules HOWTO:
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#1745">[ date ]
</a>
27 <a href=
"thread.html#1745">[ thread ]
</a>
28 <a href=
"subject.html#1745">[ subject ]
</a>
29 <a href=
"author.html#1745">[ author ]
</a>
34 <PRE> To be perfectly frank, my position is that you should at least be able
35 to read the code (and I like to believe that my code is fairly readable) if
36 you're going to be writing a module, cut-and-paste or not. Much as I would
37 have liked to write a full and detailed document on creating modules, and
38 for that matter a complete Services design document, I simply don't have
39 that much time on my hands. The
"protocol/unreal
" module in particular is
40 well documented, and should be instructive on how modules are put together;
41 for
"bot
"-type modules, look at any of the existing *Serv modules, which
42 among others should answer your question about adding commands.
44 The point about how to compile is a valid one, and I'll look at adding
45 more information about that into the manual; in the meantime, look at the
46 Makefile for any of the existing modules and/or read the comments at the
47 top of modules/Makerules for information.
49 As far as the API goes, it's already documented in section
6 of the
50 manual, in case you missed it.
53 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org
</A>
54 <A HREF=
"http://achurch.org/">http://achurch.org/
</A>
56 ><i>*This message was transferred with a trial version of CommuniGate(tm) Pro*
59 </I>><i>I'm the admin for a tiny RolePlayGaming network and we're currently looking
60 </I>><i>into making addon modules for a series of Services Bots that will share the
61 </I>><i>load for a Roleplay Service on IRC.
63 </I>><i>The problem is that none of us are really coders, and we need a lot of help
64 </I>><i>getting started. With enormous respect for Andy and his great works on
65 </I>><i>producing his wonderful services, his documentation re: modules creation
66 </I>><i>leaves much to be desired, and seems to concentrate more on where and how we
67 </I>><i>should indent, then on how to compile a new module, and integrate it into
70 </I>><i>Simple questions to which we should be able find answers baffle us I'm
71 </I>><i>afraid, one such is: Do we add tokens for new commands to the exsiting token
72 </I>><i>list in init.c, or is there a way to introduce them within the modules
73 </I>><i>without editing existing code?
75 </I>><i>How do we include a module to the list of modules to be compiled, ie: is
76 </I>><i>there a command line for compilation of extra modules like with Apache, or
77 </I>><i>do we just drop them into the modules directory and recompile from scratch
78 </I>><i>as with UnrealIRCD?
80 </I>><i>Has anyone written a skeleton module with compilation instructions that we
81 </I>><i>could use as a starter?
82 </I>><i>Is there a list of APIs that we could call on or must we read the code (Very
83 </I>><i>headbreaking for us low IQ, cut
& paste coders).
85 </I>><i>Please don't tell me anything useless like:
"If you don't understand the
86 </I>><i>code you shouldn't be doing this!
" Unless you intend to do the coding for
87 </I>><i>us, for free, because suitable, or not; We're all we've got!.
89 </I>><i>Olly
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">admin at rpglairs.com
</A>
95 </I>><i>Outgoing mail is certified Virus Free.
96 </I>><i>Checked by AVG anti-virus system (
<A HREF=
"http://www.grisoft.com">http://www.grisoft.com
</A>).
97 </I>><i>Version:
6.0.413 / Virus Database:
232 - Release Date:
06/
11/
2002
100 </I>><i>------------------------------------------------------------------
101 </I>><i>To unsubscribe or change your subscription options, visit:
102 </I>><i><A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">http://www.ircservices.za.net/mailman/listinfo/ircservices-coding
</A>
111 <LI>Previous message:
<A HREF=
"001742.html">[IRCServices Coding] Coding Modules HOWTO:
113 <LI>Next message:
<A HREF=
"001746.html">[IRCServices Coding] Coding Modules HOWTO:
115 <LI> <B>Messages sorted by:
</B>
116 <a href=
"date.html#1745">[ date ]
</a>
117 <a href=
"thread.html#1745">[ thread ]
</a>
118 <a href=
"subject.html#1745">[ subject ]
</a>
119 <a href=
"author.html#1745">[ author ]
</a>
projects / irc.git / blob