Re: [Rails-devel] Rails-devel Digest, Vol 2, Issue 1

[brett l. <wak...@gm...>]

On 7/1/06, John A. Tamplin <ja...@ja...> wrote:
> brett lentz wrote:
>
> >All those will work.  Do you have time to work on the XML data for those?
> >
> >
> I don't own 1899, 18NL, or 18KAAS, but I can do the others.  Where are
> special abilities for privates defined?  What is missing for 18AL, which
> is already there?
>


There's not really much documentation outside of reading the source. I
can try to work on improving that a bit.

I'll need to double check, but I think all the special properties are
in a single file.


> >We were waiting on route calculation for someone (you?) to port their
> >tile data over.
> >
> >
> Perhaps I misunderstood -- when we last discussed that sometime around
> last November, it sounded like you didn't want to use the tile database
> for route determination but only for drawing, with a comment about the
> connectivity bit fields which would be used for route calculation being
> too convoluted for use in Rails.  If I am remembering incorrectly or you
> have changed your mind, there is no reason the API to the tile database
> couldn't be nailed down pretty quickly and the route calculation code
> written based on that.
>

I don't really remember the specifics of the discussion, but at this
moment I'd be willing to accept as much code as you're willing to
contribute.  We need both route calculation and to improve the drawing
code, so if you can do one or both, I'm happy with that.

> I'm sorry I haven't had the time I thought I would, and I am pressed for
> time to get 2 more (possibly 3 or 4) games in production in time for
> Essen.  I wont have time in the next month or so to spend a lot of time
> such as finishing up the Java port of the tile rendering code (or then
> writing the Swing output device for it), but it wouldn't be hard to
> implement the non-drawing parts of the API based on a static XML file
> for use in route calculation (or derive it from the information
> currently in Tiles.xml which appears to have the connectivity
> requirements, other than track that merges before a city [ie, city to A
> and city to B share track before it gets to the city and can't be used
> by two different trains]).
>

No worries.  The summer time has traditionally been our slow time
anyhow. Most of us are out playing in the sun and don't have as much
time to dedicate to sitting inside coding. ;-)