Re: [Rails-devel] Fix for MapHex Display Problem

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

 
	We should however somewhere most prominent put at least that Assumption (Preprinted Tiles have negative IDs, tiles can have an ID and a picture ID differing) as a Design 	Guideline either on the Wiki or in a Readme for Developers/Implementers.

It's rather a requirement than an assumption.  

	Theres a number of not so trivial points in the code that costs a lot of time for someone to understand :)

Yes, the learning curve is steep.  I'm not sure we are already at a point where we can codify the whole global design; it's still somewhat volatile, and in particular Stefan is working on it. 
But surely there are many aspects that can and should be described.
 
	Action-Handling through different Classes...
	movestack() (wth is that :)) I think it has to do something with the possibility to undo and redo moves :)

Exactly: it's the undo stack.

	differentiation between game engine and UI
 
	Thats some points of my head which cost me a lot of time and frustration.

	While i find the design from my limited point of experience flexible its not easy to understand :)

I should remark that you have taken a path that I would not recommend to anyone: to implement a complex game like 1880 with almost no prior experience with Rails.
For myself, I take a gradual path: increasing complexity in small steps, adding some new features with every new game that I start working on.  If I would have thought of doing 1880, I would first have looked for some simpler game from the OO stable.  Given all that, I must say that you have made tremendous progress, a lot more than I had expected.

Erik