aboutsummaryrefslogtreecommitdiff
path: root/pipermail/nel/2001-July/000518.html
diff options
context:
space:
mode:
authorneodarz <neodarz@neodarz.net>2018-08-11 20:21:34 +0200
committerneodarz <neodarz@neodarz.net>2018-08-11 20:21:34 +0200
commit0ea5fc66924303d1bf73ba283a383e2aadee02f2 (patch)
tree2568e71a7ccc44ec23b8bb3f0ff97fb6bf2ed709 /pipermail/nel/2001-July/000518.html
downloadnevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.tar.xz
nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.zip
Initial commit
Diffstat (limited to '')
-rw-r--r--pipermail/nel/2001-July/000518.html72
1 files changed, 72 insertions, 0 deletions
diff --git a/pipermail/nel/2001-July/000518.html b/pipermail/nel/2001-July/000518.html
new file mode 100644
index 00000000..561c12f3
--- /dev/null
+++ b/pipermail/nel/2001-July/000518.html
@@ -0,0 +1,72 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Nel] Snowball 2.0?</TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:ahoyt%40packetport.com">
+ <LINK REL="Previous" HREF="000517.html">
+ <LINK REL="Next" HREF="000507.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Nel] Snowball 2.0?</H1>
+ <B>Tony Hoyt</B>
+ <A HREF="mailto:ahoyt%40packetport.com"
+ TITLE="[Nel] Snowball 2.0?">ahoyt@packetport.com</A><BR>
+ <I>Thu, 19 Jul 2001 09:43:46 -0400</I>
+ <P><UL>
+ <LI> Previous message: <A HREF="000517.html">[Nel] Snowball 2.0?</A></li>
+ <LI> Next message: <A HREF="000507.html">[Nel] Snowball client trouble</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#518">[ date ]</a>
+ <a href="thread.html#518">[ thread ]</a>
+ <a href="subject.html#518">[ subject ]</a>
+ <a href="author.html#518">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Vianney Lecroart wrote:
+
+ I've read some of the logs to this newsgroup so I knew about the
+issues with the current SnowBall. I would like to give NEL a try but I
+was hopeing a more full version example would help me more :-) But yes,
+i'll look at the tutorials some more to see how this sdk works.
+
+&gt;<i> The NeL library user interface changes often because we have not fix it. We
+</I>&gt;<i> plan to fix the NeL interface before the end of this year. But the current
+</I>&gt;<i> user interface doesn't change often anyway.
+</I>
+ I'm a little confused here. Basicly what I want to know is, if I
+write code for nel now, how strong is the possablity of me having to
+re-write that code to take into the count of changes in function
+definitions? now i know the code must evolve and change, but if I start
+writing an application with the sdk, and every two months i need to make
+major revisions to keep up with the latest and greatest, I may pause
+some before starting development. How possable is it to see a lock on
+the headers?
+
+&gt;<i> I leave Cyril Corvazier (lead 3d programer) to answer to this :)
+</I>
+ Also, anyone hear about this new technology Verant Interactive is
+going to be using for EQ1.5? (ie, the upcomeing expansion) I hear it's
+supposed to help make online games work a hell of a lot faster. But
+what is it?
+
+ Tony
+
+</pre>
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI> Previous message: <A HREF="000517.html">[Nel] Snowball 2.0?</A></li>
+ <LI> Next message: <A HREF="000507.html">[Nel] Snowball client trouble</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#518">[ date ]</a>
+ <a href="thread.html#518">[ thread ]</a>
+ <a href="subject.html#518">[ subject ]</a>
+ <a href="author.html#518">[ author ]</a>
+ </LI>
+ </UL>
+</body></html>