Hi David, Porter,
> Maybe, this could be added to the todo list with a low priority, clean up
> the buildFile format so that it follows a DTD, and utilises xml
> characteristcs more fully.
Realistically, there is no way this will ever happen. It would require many
100's of hours to change VASSAL to output pure XML for no user gain whatsoever
(as opposed to module designer gain) . While it would be nice to save a few
module designers a few minutes here and there, it just ain't going to happen.
Performance wise, I seriously doubt that any library can parse XML faster than
a delimited text string. The format of the command Strings is also the format
that is transmitted via the server between clients, so the condensed command
strings also keep the data volumes down into and out of the server, as compared
to the seriously wordy pure XML format.
> Surely there is a way to support 2 formats for the buildFile in a transition
> period,
Let's see what you think after you have had a look at the code :)
> but the old addage I think applies, if it ain't broke, don't fix it.
!
*********** REPLY SEPARATOR ***********
On 15/04/2006 at 8:18 PM David Stanaway wrote:
I doubt it would be much faster, just more well specified. I will take a
look at it as soon as eclipse makes it in to debian/testing (When it does it
will be natively compiled with gcj I believe, which should be nice and
fast).
Surely there is a way to support 2 formats for the buildFile in a transition
period, but the old addage I think applies, if it ain't broke, don't fix it.
On 4/15/06, Porter235 <[EMAIL PROTECTED]> wrote:
>
> On Saturday 15 April 2006 19:44, David Stanaway wrote:
> > Maybe, this could be added to the todo list with a low priority, clean
> up
> > the buildFile format so that it follows a DTD, and utilises xml
> > characteristcs more fully.
>
> I too have commented about this, but have never heard back. I know that
> there
> is concern about backwards compatitbilty, and I am pretty sure that I read
> in
> comments within the code, that at least originally, this format was chosen
> over xml due to speed issues parsing xml. I also believe that that choice
> was
> made prior to Java getting some serious XML horsepower added to it, and
> may
> be worth examining again as I suspect that pure XML would actually be much
> FASTER at this point due to the XML libraries now available.
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
[Non-text portions of this message have been removed]
YAHOO! GROUPS LINKS
Visit your group "vassalengine" on the web.
To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
____________________________________________________________
Brent Easton
Analyst/Programmer
University of Western Sydney
Email: [EMAIL PROTECTED]
[Non-text portions of this message have been removed]
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/vassalengine/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/