rails-devel

Re: [Rails-devel] Hex Tilesets

[<wak...@ea...>]

Correct.

I was meaning for the other games: 1870, 1856, 18AL, and 1835


Have you been able to get into CVS?  I haven't heard anything since we last exchanged e-mails.


---Brett


-----Original Message-----
From: John David Galt <jd...@di...>
Sent: Aug 8, 2005 1:05 PM
To: rai...@li...
Subject: Re: [Rails-devel] Hex Tilesets

wak...@ea... wrote:
> They are mostly complete with one exception:  I'm not too familiar with
> the upgrade paths for the whistlestop (small town) tiles, so I've left
> those undefined for now. 

In 1830, those tiles don't upgrade, period.



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Rails-devel mailing list
Rai...@li...
https://lists.sourceforge.net/lists/listinfo/rails-devel

RE: [Rails-devel] Hex Tilesets

[Erik V. <eri...@hc...>]

> > I've committed a preliminary round of Tileset definitions to CVS.
> > 
> > I've created tilesets for each of the 5 games we've defined so far.
> > 
> > They are mostly complete with one exception:  I'm not too 
> > familiar with the upgrade paths for the whistlestop (small 
> > town) tiles, so I've left those undefined for now. 
> 
> XMLBuddy considers your TileSet.xml invalid, and rightly so,
> because there can be only one top-level tag in an XML file.
> 
> I don't think we really need a different tile set for each colour
> (the colour will be a tile property).
> So I propose to merge the <TileSet> tags into one.

... and to indicate the colours in a comment tag.
EV

RE: [Rails-devel] Hex Tilesets

[<wak...@ea...>]

I separated them on the notion that there's potential for non-standard colors and also, rather than several hundred  statements of "Color=foo" in the individual tile definitions, it's only a handful of statements at the TileSet level.

Unless there's a specific benefit I'm not seeing, why make more data entry work for ourselves than we really need to?


---Brett.


-----Original Message-----
From: Erik Vos <eri...@hc...>
Sent: Aug 8, 2005 11:49 AM
To: rai...@li...
Subject: RE: [Rails-devel] Hex Tilesets

> I've committed a preliminary round of Tileset definitions to CVS.
> 
> I've created tilesets for each of the 5 games we've defined so far.
> 
> They are mostly complete with one exception:  I'm not too 
> familiar with the upgrade paths for the whistlestop (small 
> town) tiles, so I've left those undefined for now. 

XMLBuddy considers your TileSet.xml invalid, and rightly so,
because there can be only one top-level tag in an XML file.

I don't think we really need a different tile set for each colour
(the colour will be a tile property).
So I propose to merge the <TileSet> tags into one.

The Map.xml files are not valid either: '&' characters
in private company names must be escaped to '&'

Erik.