software/RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2002/000199.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices Coding] Nickname linking/coding question
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Nickname%20linking/coding%20question&In-Reply-To=">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="000198.html">
  11    <LINK REL="Next"  HREF="000206.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] Nickname linking/coding question</H1>
  15     <B>Andrew Church</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Nickname%20linking/coding%20question&In-Reply-To="
  17        TITLE="[IRCServices Coding] Nickname linking/coding question">achurch at achurch.org
  18        </A><BR>
  19     <I>Tue Feb  5 10:44:26 PST 2002</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="000198.html">[IRCServices Coding] Nickname linking/coding question
  22 </A></li>
  23         <LI>Next message: <A HREF="000206.html">[IRCServices Coding] A few new bugs/suggestions
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#199">[ date ]</a>
  27               <a href="thread.html#199">[ thread ]</a>
  28               <a href="subject.html#199">[ subject ]</a>
  29               <a href="author.html#199">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>     So it looks like the differences are (1) separate memos for separate
  35 nicks and (2) keeping the same nick on the channel access list.  I think
  36 (1) is a PITA; (2) is a good idea and something I've been thinking about
  37 (e.g. store nickname in ChanAccess as well) but a low priority.
  38
  39      You're of course welcome to fork Services and start your own project;
  40 that's what open source is about, after all.
  41
  42   --Andrew Church
  43     <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A>
  44     <A HREF="http://achurch.org/">http://achurch.org/</A>
  45
  46 &gt;<i>It's a system that allows all linked nicknames to still have their own
  47 </I>&gt;<i>memobox. When you switch to a linked nickname, it'll say how many memos you
  48 </I>&gt;<i>have, and how many you have on your linked nicknames. It also allows you to
  49 </I>&gt;<i>add links to the currently used nickname, which is what I was inquiring
  50 </I>&gt;<i>about. Channel entries still display the nickname that was originally was
  51 </I>&gt;<i>added.
  52 </I>&gt;<i>
  53 </I>&gt;<i>Basically, all of the nicknames exist on their own; they aren't copies of
  54 </I>&gt;<i>each other. The system itself only does two basic things:
  55 </I>&gt;<i>    a. when you identify, it automatically identifies to all linked
  56 </I>&gt;<i>nicknames
  57 </I>&gt;<i>    b. if you join a channel and have a linked nickname in the database,
  58 </I>&gt;<i>it'll see that and auto-op you.
  59 </I>&gt;<i>
  60 </I>&gt;<i>It also allows cross-linking. However, I'm probably going to want a system
  61 </I>&gt;<i>that automatically crosslinks them (which ircservices already does
  62 </I>&gt;<i>indirectly)..
  63 </I>&gt;<i>
  64 </I>&gt;<i>In my opinion, the new nickgroup code seems a bit of an overkill for what
  65 </I>&gt;<i>I'm trying to accomplish. The system I'm wanting to use could probably be
  66 </I>&gt;<i>built by using the original nickname structure (ni) and adding an array or
  67 </I>&gt;<i>something similiar to the new structure (ngi) that points to the linked
  68 </I>&gt;<i>nicknames and various pieces of information.
  69 </I>&gt;<i>
  70 </I>&gt;<i>I'm sure there's a better way that I haven't thought of. Suggestions are
  71 </I>&gt;<i>welcome. ^_^
  72 </I>&gt;<i>
  73 </I>&gt;<i>I think I'm definitely going to stick with my current base instead of
  74 </I>&gt;<i>converting to the style 5.0 uses though. It seems a bit tedious to work
  75 </I>&gt;<i>with.. Don't get me wrong - you've done well so far and the idea of a
  76 </I>&gt;<i>services package with module support is a great idea, but when you have to
  77 </I>&gt;<i>search through function after function (and usually in 3-5 files) in
  78 </I>&gt;<i>unfamiliar code to find something being called, it becomes too much work.
  79 </I>&gt;<i>
  80 </I>&gt;<i>------------------------------------------------------------------
  81 </I>&gt;<i>To unsubscribe or change your subscription options, visit:
  82 </I>&gt;<i><A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">http://www.ircservices.za.net/mailman/listinfo/ircservices-coding</A>
  83 </I>
  84 </PRE>
  85
  86 <!--endarticle-->
  87     <HR>
  88     <P><UL>
  89         <!--threads-->
  90         <LI>Previous message: <A HREF="000198.html">[IRCServices Coding] Nickname linking/coding question
  91 </A></li>
  92         <LI>Next message: <A HREF="000206.html">[IRCServices Coding] A few new bugs/suggestions
  93 </A></li>
  94          <LI> <B>Messages sorted by:</B>
  95               <a href="date.html#199">[ date ]</a>
  96               <a href="thread.html#199">[ thread ]</a>
  97               <a href="subject.html#199">[ subject ]</a>
  98               <a href="author.html#199">[ author ]</a>
  99          </LI>
 100        </UL>
 101
 102 </body></html>