jolo-announce — For publishing Jolo related announcements.

[Mike H. <mh...@le...>]

Fellow Jolo Developers,

Youngm and I have finally finished the initial design work for the core of
Jolo and the documents have been submitted to Source
Forge(http://sourceforge.net/projects/jolo/).  Just go to the Docs section.
The design includes handling objects on the map and how ojbects interact as
well as communications between the client and server.  We still haven't
written up a good design for the server, the plug-in architecture, the
client API and the client itself but those should be much easier than the
core architecture.  Besides with what we have it should be easy to make a
server that plays a virtual game with itself (which will be good for
testing.)

So far the design is very flexible.  The game engine should be able to
handle many different types of objects that can interact in many different
ways going way beyond the simplicity of Bolo.  The communications protocol
attempts to minimize traffic so hopefully even Evan could even play from
home using his 28.8K connection. :)

Even if you don't plan on working on Jolo your input is valuable so if you
have the time (and can understand UML) please subscribe to the Jolo-Develop
mailing list, read the design documents (also on Source Forge) and let all
the developers know what you think by submitting questions and comments to
the mailing list.  These documents are not the final word and are not way
set in stone.  We want to hear your criticism and discover better ways of
doing things.  If we decide this design is a pile of infested cow manure
we'd like to make that decision sooner than later. :)

We want to have a design review via IRC ASAP.  I think it will be easiest to
plan such a discussion via the mailing list.

Your friendly neighborhood Jolo project admin,

heathm

p.s.  Some of you have already recieved this E-mail directly from me but I
wanted to make sure it got archived in the Jolo-announce mailing list.