diff options
| author | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
|---|---|---|
| committer | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
| commit | 0ea5fc66924303d1bf73ba283a383e2aadee02f2 (patch) | |
| tree | 2568e71a7ccc44ec23b8bb3f0ff97fb6bf2ed709 /pipermail/nel/2001-June/000436.html | |
| download | nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.tar.xz nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.zip | |
Initial commit
Diffstat (limited to 'pipermail/nel/2001-June/000436.html')
| -rw-r--r-- | pipermail/nel/2001-June/000436.html | 121 |
1 files changed, 121 insertions, 0 deletions
diff --git a/pipermail/nel/2001-June/000436.html b/pipermail/nel/2001-June/000436.html new file mode 100644 index 00000000..2e0366a1 --- /dev/null +++ b/pipermail/nel/2001-June/000436.html @@ -0,0 +1,121 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Nel] .shape file format change</TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:tanis%40digi-web.it"> + <LINK REL="Previous" HREF="000435.html"> + <LINK REL="Next" HREF="000437.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Nel] .shape file format change</H1> + <B>Valerio Santinelli</B> + <A HREF="mailto:tanis%40digi-web.it" + TITLE="[Nel] .shape file format change">tanis@digi-web.it</A><BR> + <I>Thu, 28 Jun 2001 16:41:58 +0200</I> + <P><UL> + <LI> Previous message: <A HREF="000435.html">[Nel] .shape file format change</A></li> + <LI> Next message: <A HREF="000437.html">[Nel] Compiling NeL from CVS</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#436">[ date ]</a> + <a href="thread.html#436">[ thread ]</a> + <a href="subject.html#436">[ subject ]</a> + <a href="author.html#436">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>----- Original Message ----- +From: "Daniel Miller" <<A HREF="mailto:miller@nevrax.com">miller@nevrax.com</A>> +Sent: Thursday, June 28, 2001 4:01 PM + +><i> First for the Nevrax.org home page: the news is all badly out of date and +</I>><i> doesn't show what's going on at the moment. Sorry about that. We're just +</I>><i> sorting out our internal knitting so that we can post news more easily. +</I>><i> There should be a general improvement at this level soon. +</I> +I spoke to Lecroart about this point. I think that keeping the site up to +date at least once a week wouldn't require a great effort. I'm not asking +you to report on the news page every single change that happens upon the +codebase. Just some generic news about what's going on in order to know that +the project is still alive. + +><i> For the roadmap - my mail of last week entitled 'a bit of news' contains a +</I>><i> loose plan for the next few months. It'll go up on the site some time +</I>soon. +><i> I'm not sure if it contains the information you're after - please shout if +</I>><i> it doesn't. +</I> +The roadmap you posted last week has been greatly appreciated on my part. :) +I hope that you can keep sending those once every one or two weeks ;) + +><i> On the documentation side - We posted a handfull of new 'features' +</I>documents +><i> under the different library headings earlier this week. Any feedback would +</I>><i> be very much appreciated. Beyond that we have been discussing what docs +</I>><i> would be good to write among ourselves. Any ideas are very welcome +</I>although +><i> our time for writing dociments is a bit limitted right now!; The problem +</I>><i> with 'how to design and build an MMORPG' type docs is that they warrant an +</I>><i> entire book - and I don't have time to write a whole book right now :(. +</I>><i> I'll see what I can do. +</I> +I've just looked at the new docs. I'm going to print them all and read them +with ease later on during those lonely nights :) + +I'm not going to ask you to write a "how to design and build a MMORPG" book. +That's out of our scope. If I'm evaluating NeL, it's because I am already +designing an MMORPG and I'm evaluating a framework that would reduce the +efforts needed to code all the game from grounds up. +The kind of documentation that I'm looking for in the future is something +that gives an overview of how the pieces of the NeL framework are tied +together, and then, some more indeep documentation about how to build a new +3D entity, how to make a connection to the server and all those things that +explain what objects should be used and which method should be called to +accomplish the main operations. + +><i> Snowballs is being re-written (to look more like a designed program and +</I>less +><i> like the accumulation of a few dozen chunks of test code spaghettied +</I>><i> together). We're just starting, so our first steps 'll be up on line +</I>><i> shortly... +</I> +I'm not pressing you to make a new Snowballs in no time. You've got all the +time you need (I know that I have no influence over this, anyway :)) +I just wish that the new Snowballs will show how to write a basic server and +a basic client, and how to code the main functions needed to make them both +run with each other. That's enough to get started with coding upon NeL. + +><i> For a binary sdk - it's a good idea - We'll look into it. :) +</I> +I agree on this one. A binary SDK would save a lot of compiling-time which +is mainly unneeded. + +Having an offline version of the code documentation without going over the +doxygen compilation time (which took a hour or maybe more on my Athlon) +would also be useful once the code is in a fairly stable condition. + +-- +Valerio Santinelli +<A HREF="http://www.digisoft-multimedia.it/">http://www.digisoft-multimedia.it/</A> + + + +</pre> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI> Previous message: <A HREF="000435.html">[Nel] .shape file format change</A></li> + <LI> Next message: <A HREF="000437.html">[Nel] Compiling NeL from CVS</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#436">[ date ]</a> + <a href="thread.html#436">[ thread ]</a> + <a href="subject.html#436">[ subject ]</a> + <a href="author.html#436">[ author ]</a> + </LI> + </UL> +</body></html> |