From: John D. G. <jd...@di...> - 2012-05-13 14:21:16
|
On 2012-05-13 05:09, Erik Vos wrote: > Thanks. > > I have created a (temporary) local branch for 1837 where I will collect the > initial bits and pieces. > Once the game can at least be started and show the map, I will merge that > branch into the master branch and push it to the repository so everybody can > access it. > > I have already fixed some unterminated <LayTile> tags in Game.xml. > > Next problem is that you have configured a number of game-specific classes > without providing these classes. That prevents Rails from starting this > game. > > Possibilities: > (1) What we normally do when developing a new game is that we begin with the > generic classes only, and only add new ones when the need clearly arises > during development. > (2) As 1837 presents itself as "a development of 1835", we could also start > with the 1835 classes, which could then be modified or extended. But that > is a bit dangerous (for 1835), and not my preference. > (3) I could also create empty 1837-specific classes according to what you > have configured. These could be filled in later where needed, removed if > unused, or merged with their 1835 siblings where it appears that > generalization is possible. > > It seems to me, that the 1835 UI classes can be reused unchanged or with > minimal changes. On the server side things are less obvious, so we will have > to see how that goes. > > Did you have any particular route in mind? No, I hadn't thought that far ahead. The Prussian-merger stuff shouldn't need to change much, if at all. The three-column starting packet will be new, though. |