Shannon V. OKeets
From: Honolulu, Hawaii
Don't take me wrong, I take that Steve was an excellent interpreter of the rules even before he started this project, which made him analyze every single step of them, in order to code the game.
However, I have seen WIF gurues make mistakes...
Don't get me wrong I thank Steve has done a good job with CWiF.
But there are two types of programmers:
Development Programmers who start from scrath and code the whole program or system.
Maintence Programmers who take existing programs or systems and make changes to them.
Steve is a Maintence Programmer. And there is nothing wrong with being a Maintence Programmer.
Therefore special thanks should be given to the people who helped Steve:
Captain for his leadership of CWiF.
Patrice for his tireless work on the maps.
All the people how helped with the write ups.
Joseignacio how can you judge Steve's abilities with CWiF prior to 2005 when the first Beta Test team was anounced
Although I know you will argue the point, you are wrong.
When the amount of code grows from 100,000 lines to over 400,000 lines, that is not maintenance. When all the graphics, for the maps, units, and forms are changed, that is not maintenance. When there are another dozen unit types added, a couple dozen optional rules, and the number of forms is doubled to over 150, that is not maintenance. Of the 100,000 lines of original code in CWIF, there is probably less than half still included in MWIF.
The analogy would be to say that someone who bought a new suit, shirt, tie, shoes, and socks, but kept his old underwear, had just updated his old wardrobe - instead of replacing it.
Now if you want to get technical, many of the fundamental routines in CWIF were written in Assembler, and I have replaced their functionality with code written in Delphi. Likewise, CWIF used a monolithic rectangle to encapsulate all the forms, which I replaced with an open design to let players place forms anywhere they want on multiple monitors. That decision requires changing the most basic compile option for programs written in Delphi.
I've also restructured the modules used to progress the sequence of play from less than 6 to over 60, changing the processing sequence to support NetPlay.
But, hey, if you want, you could argue that the IPhone 5 is just a maintenance improvement of the Apple II.
Perfection is an elusive goal.