RE: [Xenocide-programming] Tech Tree XML layout

[mamutas <ma...@pr...>]

Hi Chris,

Welcome back. It was a while since there was a news from you.

Also, there were some changes and additions in the current list of =
working
items. One being the research tree XML definition file, which Cpt.
Boxershorts is working on. As I see the Xnet DB and the research tree =
XML
files have lots in common, so they should not be developed individually.

First of all, I think that we should split information about visual =
entry
presentation into separate file and to have a file with relationship =
info
(like 'rifle' is 'weapon', 'tank' is 'hwp', kind of info) which will =
refer
to the visual info file. That visual info file will be used by research =
tree
XML in the same way.

Second, I strongly recommend you not to spent your time on writing an =
XML
parser (unless you want to do it just for fun), but use already existing
one. The XML processing will be present in many areas of the project, so
there is a need for fast and reliable parser, which will work with any =
XML
formats. So far, we planning to use Xerces from Apache and that is what =
you
should plan on too.

Third, there is a String class in STL which is widely used with the =
project,
so you should use it as well instead of your implementatioin.

Also, there was a significant work done on converting original names to =
the
ones we will use in the game, which should be utilized everywhere. The =
XML
file of XNDL must use it as well. Breunor or Cpt. Boxershorts will give =
you
more info and directions on that.

Again, sorry if I was to criticizing. I really appreciate the work you =
are
doing and efforts you are putting in the project.

Best regards,
Mamutas.

> -----Original Message-----
> From: xen...@li...=20
> [mailto:xen...@li...] On=20
> Behalf Of Chris Phillips
> Sent: Friday, December 05, 2003 1:49 AM
> To: xen...@li...
> Subject: Re: [Xenocide-programming] Tech Tree XML layout
>=20
>=20
>=20
> Hi Everyone,
>=20
> Sorry I have been absent for so long.  I have been extremely=20
> busy recently.  I'm essentially=20
> working three jobs right now, but I would still like to=20
> continue contributing to this project.
>=20
> I was originally to do the X-Net XML file and X-Net data=20
> loader a couple of months ago. =20
> I have an example of an XML file and the X-Net data loader is=20
> further along.  I am going to post a more complete version of=20
> the XNDL class this weekend.  I have not been able to do any=20
> significant development on it until just a couple of days ago.
>=20
> The XNDL is close to being able to completely tokenize an XML=20
> file (although it may not appear to be..).  We need to decide=20
> on a format  for an X-Net XML file, though.  If we=20
> want a full-fledged XML parser, than the implementation will=20
> be much more tricky.  Basically,=20
> you're dealing with a compiler front-end with that. =20
> Otherwise, we will have to use canned tags=20
> or meet somewhere in between. We can base the XML file on my=20
> example, or any other. =20
> It doesn't matter much to me. But keep in mind, that the=20
> simpler the XML syntax, the more=20
> likely it is to be compatible with the XNDL.  Please keep the=20
> syntax simple for the time being. :) =20
>=20
> I have attached the current state of the XNDL code.  It is very raw.=20
> Don't worry about=20
> critiquing the code.  It's in way to poor of a state for=20
> that. :)  I also included my example XML file.  I will post=20
> more comments and updated code later.=20
>=20
> Regards,
> chrisp
>=20
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.545 / Virus Database: 339 - Release Date: 2003/11/27
> =20
>  =20
>=20

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.545 / Virus Database: 339 - Release Date: 2003/11/27
=20