aboutsummaryrefslogtreecommitdiff
path: root/pipermail/nel/2000-November/000065.html
diff options
context:
space:
mode:
Diffstat (limited to 'pipermail/nel/2000-November/000065.html')
-rw-r--r--pipermail/nel/2000-November/000065.html72
1 files changed, 72 insertions, 0 deletions
diff --git a/pipermail/nel/2000-November/000065.html b/pipermail/nel/2000-November/000065.html
new file mode 100644
index 00000000..6ab4ca99
--- /dev/null
+++ b/pipermail/nel/2000-November/000065.html
@@ -0,0 +1,72 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [NOISE] Re: [Nel] pointers on documentation?</TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:cblt%40cblt.org">
+ <LINK REL="Previous" HREF="000064.html">
+ <LINK REL="Next" HREF="000066.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[NOISE] Re: [Nel] pointers on documentation?</H1>
+ <B>Nicolas Hognon</B>
+ <A HREF="mailto:cblt%40cblt.org"
+ TITLE="[NOISE] Re: [Nel] pointers on documentation?">cblt@cblt.org</A><BR>
+ <I>Wed, 29 Nov 2000 13:16:32 +0100</I>
+ <P><UL>
+ <LI> Previous message: <A HREF="000064.html">[Nel] pointers on documentation?</A></li>
+ <LI> Next message: <A HREF="000066.html">[Nel] Distributed server algo</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#65">[ date ]</a>
+ <a href="thread.html#65">[ thread ]</a>
+ <a href="subject.html#65">[ subject ]</a>
+ <a href="author.html#65">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>&gt;<i> Has somebody a good pointer on some basic documentation (URL, book,
+</I>&gt;<i> paper) that details those concepts found in 3D and distributed games?
+</I>&gt;<i>
+</I>
+you can look at this book : 3D Game Engine Design
+by David H. Eberly
+or at this website : <A HREF="http://www.flipcode.com/">http://www.flipcode.com/</A>
+
+&gt;<i> For the nel guys, is there any &quot;Global Architecture Overview&quot; paper
+</I>&gt;<i> planned? I know about the white paper, but I would be more interested in
+</I>&gt;<i> how you see the architecture in place. For example, it would be nice to
+</I>&gt;<i> read a paper describing a typical interaction: &quot;you setup object like
+</I>&gt;<i> this, with this server and this client; when game starts, at each time
+</I>&gt;<i> step, the client send this info to the server; to model a scene, you
+</I>&gt;<i> need at least this and that...&quot;. It needs not to be very precise, but
+</I>&gt;<i> fill the gap between the white papers and the source code.
+</I>&gt;<i>
+</I>&gt;<i> Of course, I would understand that such a paper would not be on top
+</I>&gt;<i> priority list. ;)
+</I>&gt;<i>
+</I>&gt;<i> Maybe when some usable server/client will be released on Linux platform,
+</I>&gt;<i> we could write an architecture description paper.
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> d.
+</I>
+
+
+</pre>
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI> Previous message: <A HREF="000064.html">[Nel] pointers on documentation?</A></li>
+ <LI> Next message: <A HREF="000066.html">[Nel] Distributed server algo</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#65">[ date ]</a>
+ <a href="thread.html#65">[ thread ]</a>
+ <a href="subject.html#65">[ subject ]</a>
+ <a href="author.html#65">[ author ]</a>
+ </LI>
+ </UL>
+</body></html>