Recently, I attempted replacing the current equipment-based model with a role-based model. The required changes are pervasive and are certain to introduce any number of bugs. Therefore, I propose a gradual migration. As a first step, the Role enum could be replaced with a Role class. This is not too difficult, but provides no immediate benefits. The next step would be to introduce methods to convert between equipment and roles, so that all methods getting and setting equipment could be gradually migrated, starting with the combat model, for example. Does that sound reasonable?
Regards Michael ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ Freecol-developers mailing list Freecol-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freecol-developers
