Recently prepared to work with friends to develop a group of Jin Yong X Games, using Silverlight technology.
Ready to develop our own Silverlight game engine simultaneously while developing this game.
This time I was mainly responsible for engine design and development.
These two days understand some of the features of Silverlight, but also looked at the dark blue qxengine.
Feel that it is more emphasis on the interface display aspect,
And I think our engine should be based on the overall, including the game framework scheduling, the rules of the game to consider.
I sketched it on the paper today and got a mind map.
Or the idea of a very rough, need to be refined gradually.
Then there is the development model for the entire team.
The team now includes three of my members, no experience in game development, and the technology is more general.
I have also tried to lead some inexperienced members to develop, and it is a more formal process, less effective, and similar to the writing of documents these things can easily erase the enthusiasm of members.
So I think as an amateur development, or must first let their development happy. Summarized as follows:
“
My view is that the long-term too "too formal" document and project management process, absolutely to the enthusiasm of our development have disadvantages.
First of all, we have to be happy in the development process, I believe that programmers are willing to write code rather than writing documents (including myself)
So I think we should give the design in general, and then we can start with the implementation. What if the code is confusing.
--the courage to reconstruct.
Look at me above writing such a big word, also shows me the determination of refactoring code, hehe. ”
Well.. These few months still focus on the game to get it.