[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2002 / 001746.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [IRCServices Coding] Coding Modules HOWTO:
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Coding%20Modules%20HOWTO%3A&In-Reply-To=3de077e0.41543%40achurch.org">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="001745.html">
   <LINK REL="Next"  HREF="001747.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[IRCServices Coding] Coding Modules HOWTO:</H1>
    <B>Olly</B> 
    <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Coding%20Modules%20HOWTO%3A&In-Reply-To=3de077e0.41543%40achurch.org"
       TITLE="[IRCServices Coding] Coding Modules HOWTO:">olly at avansys.co.uk
       </A><BR>
    <I>Sun Nov 24 02:53:03 PST 2002</I>
    <P><UL>
        <LI>Previous message: <A HREF="001745.html">[IRCServices Coding] Coding Modules HOWTO:
</A></li>
        <LI>Next message: <A HREF="001747.html">[IRCServices Coding] Coding Modules HOWTO:
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1746">[ date ]</a>
              <a href="thread.html#1746">[ thread ]</a>
              <a href="subject.html#1746">[ subject ]</a>
              <a href="author.html#1746">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>*This message was transferred with a trial version of CommuniGate(tm) Pro*
Andy

I take your point re: ability. I have already stated that I am in no way
good enough to even shine your shoes, and should stick to scripting. Much of
what seems obvious to you, appears obfusticated and confusing to me. But as
I've previously pointed out. I'm all we have just now  :?P

I have, and still am reading the manual. Unlike many that post to these
things I do make the effort. However I did not mean to disparage your good
works, in fact you actually comment far more then most others do, but it is
nonetheless true that you still fall into the trap of assuming that we have
your intelligence, and can guess much of what is required from experience.
Some of us unfortunately need crutches, and whilst I did manage to garner
some of the information from HelpServ myself. I felt I was really hanging
out there with my guesses, and could not determine for the life of me how to
add commands. I have recieved a few excellent modules from Craig (AKA Brain)
based on HelpServ (the module I myself had already chosen as the possible
basis for my attempts at ruining services, as it seems the most likeliy to
succeed), and I may now be able to get a head start on this thing. However,
if there are any other modules out there for me to get my grubby little cut
and paste on, I wouild be extremely grateful. I can't emphasise enough how
helpful it would be for me to be able to see examples of real coders at work
;?) I can assure you that I would respect any restrictions placed on me re:
use, copyrights etc.

My suggestion, if you will allow, is to put together a skeleton module like
the Unreal people do, and comment that. It should take very little time, as
it would probably be based on HelpServ. and would give people like me the
kickstart they need.


Thanks for your forebearance.

Olly

-----Original Message-----
From: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">ircservices-coding-admin at ircservices.za.net</A>
[mailto:<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">ircservices-coding-admin at ircservices.za.net</A>]On Behalf Of Andrew
Church
Sent: 24 November 2002 05:36
To: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">ircservices-coding at ircservices.za.net</A>
Subject: Re: [IRCServices Coding] Coding Modules HOWTO:


*This message was transferred with a trial version of CommuniGate(tm) Pro*
     To be perfectly frank, my position is that you should at least be able
to read the code (and I like to believe that my code is fairly readable) if
you're going to be writing a module, cut-and-paste or not.  Much as I would
have liked to write a full and detailed document on creating modules, and
for that matter a complete Services design document, I simply don't have
that much time on my hands.  The &quot;protocol/unreal&quot; module in particular is
well documented, and should be instructive on how modules are put together;
for &quot;bot&quot;-type modules, look at any of the existing *Serv modules, which
among others should answer your question about adding commands.

     The point about how to compile is a valid one, and I'll look at adding
more information about that into the manual; in the meantime, look at the
Makefile for any of the existing modules and/or read the comments at the
top of modules/Makerules for information.

     As far as the API goes, it's already documented in section 6 of the
manual, in case you missed it.

  --Andrew Church
    <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A>
    <A HREF="http://achurch.org/">http://achurch.org/</A>

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (<A HREF="http://www.grisoft.com">http://www.grisoft.com</A>).
Version: 6.0.413 / Virus Database: 232 - Release Date: 06/11/2002


</PRE>

<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="001745.html">[IRCServices Coding] Coding Modules HOWTO:
</A></li>
	<LI>Next message: <A HREF="001747.html">[IRCServices Coding] Coding Modules HOWTO:
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1746">[ date ]</a>
              <a href="thread.html#1746">[ thread ]</a>
              <a href="subject.html#1746">[ subject ]</a>
              <a href="author.html#1746">[ author ]</a>
         </LI>
       </UL>

</body></html>
Commit	Line	Data
3bd189cb JR	1	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
	2	<HTML>
	3	<HEAD>
	4	<TITLE> [IRCServices Coding] Coding Modules HOWTO:
	5	</TITLE>
	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=3de077e0.41543%40achurch.org">
	8	<META NAME="robots" CONTENT="index,nofollow">
	9	<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
	10	<LINK REL="Previous" HREF="001745.html">
	11	<LINK REL="Next" HREF="001747.html">
	12	</HEAD>
	13	<BODY BGCOLOR="#ffffff">
	14	<H1>[IRCServices Coding] Coding Modules HOWTO:</H1>
	15	<B>Olly</B>
	16	<A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Coding%20Modules%20HOWTO%3A&In-Reply-To=3de077e0.41543%40achurch.org"
	17	TITLE="[IRCServices Coding] Coding Modules HOWTO:">olly at avansys.co.uk
	18	</A><BR>
	19	<I>Sun Nov 24 02:53:03 PST 2002</I>
	20	<P><UL>
	21	<LI>Previous message: <A HREF="001745.html">[IRCServices Coding] Coding Modules HOWTO:
	22	</A></li>
	23	<LI>Next message: <A HREF="001747.html">[IRCServices Coding] Coding Modules HOWTO:
	24	</A></li>
	25	<LI> <B>Messages sorted by:</B>
	26	<a href="date.html#1746">[ date ]</a>
	27	<a href="thread.html#1746">[ thread ]</a>
	28	<a href="subject.html#1746">[ subject ]</a>
	29	<a href="author.html#1746">[ author ]</a>
	30	</LI>
	31	</UL>
	32	<HR>
	33	<!--beginarticle-->
	34	<PRE>This message was transferred with a trial version of CommuniGate(tm) Pro
	35	Andy
	36
	37	I take your point re: ability. I have already stated that I am in no way
	38	good enough to even shine your shoes, and should stick to scripting. Much of
	39	what seems obvious to you, appears obfusticated and confusing to me. But as
	40	I've previously pointed out. I'm all we have just now :?P
	41
	42	I have, and still am reading the manual. Unlike many that post to these
	43	things I do make the effort. However I did not mean to disparage your good
	44	works, in fact you actually comment far more then most others do, but it is
	45	nonetheless true that you still fall into the trap of assuming that we have
	46	your intelligence, and can guess much of what is required from experience.
	47	Some of us unfortunately need crutches, and whilst I did manage to garner
	48	some of the information from HelpServ myself. I felt I was really hanging
	49	out there with my guesses, and could not determine for the life of me how to
	50	add commands. I have recieved a few excellent modules from Craig (AKA Brain)
	51	based on HelpServ (the module I myself had already chosen as the possible
	52	basis for my attempts at ruining services, as it seems the most likeliy to
	53	succeed), and I may now be able to get a head start on this thing. However,
	54	if there are any other modules out there for me to get my grubby little cut
	55	and paste on, I wouild be extremely grateful. I can't emphasise enough how
	56	helpful it would be for me to be able to see examples of real coders at work
	57	;?) I can assure you that I would respect any restrictions placed on me re:
	58	use, copyrights etc.
	59
	60	My suggestion, if you will allow, is to put together a skeleton module like
	61	the Unreal people do, and comment that. It should take very little time, as
	62	it would probably be based on HelpServ. and would give people like me the
	63	kickstart they need.
	64
65
66	Thanks for your forebearance.
67
68	Olly
69
70	-----Original Message-----
71	From: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">ircservices-coding-admin at ircservices.za.net</A>
72	[mailto:<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">ircservices-coding-admin at ircservices.za.net</A>]On Behalf Of Andrew
73	Church
74	Sent: 24 November 2002 05:36
75	To: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">ircservices-coding at ircservices.za.net</A>
76	Subject: Re: [IRCServices Coding] Coding Modules HOWTO:
77
78
79	This message was transferred with a trial version of CommuniGate(tm) Pro
80	To be perfectly frank, my position is that you should at least be able
81	to read the code (and I like to believe that my code is fairly readable) if
82	you're going to be writing a module, cut-and-paste or not. Much as I would
83	have liked to write a full and detailed document on creating modules, and
84	for that matter a complete Services design document, I simply don't have
85	that much time on my hands. The "protocol/unreal" module in particular is
86	well documented, and should be instructive on how modules are put together;
87	for "bot"-type modules, look at any of the existing *Serv modules, which
88	among others should answer your question about adding commands.
89
90	The point about how to compile is a valid one, and I'll look at adding
91	more information about that into the manual; in the meantime, look at the
92	Makefile for any of the existing modules and/or read the comments at the
93	top of modules/Makerules for information.
94
95	As far as the API goes, it's already documented in section 6 of the
96	manual, in case you missed it.
97
98	--Andrew Church
99	<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A>
100	<A HREF="http://achurch.org/">http://achurch.org/</A>
101
102	---
103	Outgoing mail is certified Virus Free.
104	Checked by AVG anti-virus system (<A HREF="http://www.grisoft.com">http://www.grisoft.com</A>).
105	Version: 6.0.413 / Virus Database: 232 - Release Date: 06/11/2002
106
107
108
109	</PRE>
110
111	<!--endarticle-->
112	<HR>
113	<P><UL>
114	<!--threads-->
115	<LI>Previous message: <A HREF="001745.html">[IRCServices Coding] Coding Modules HOWTO:
116	</A></li>
117	<LI>Next message: <A HREF="001747.html">[IRCServices Coding] Coding Modules HOWTO:
118	</A></li>
119	<LI> <B>Messages sorted by:</B>
120	<a href="date.html#1746">[ date ]</a>
121	<a href="thread.html#1746">[ thread ]</a>
122	<a href="subject.html#1746">[ subject ]</a>
123	<a href="author.html#1746">[ author ]</a>
124	</LI>
125	</UL>
126
127	</body></html>