It's been pointed out that the client-side class diagram that I posted last night doesn't include anything for the user interface. I have two things to say about that.
First, it was intentional. If you look at the project plan that I posted about a month ago, you see that "Token Source" and "Token Inventory" come before "Draw Token Action" and "Token Display GUI". The Token Source is handled by the server, and the Token Inventory resides on the client. The next two steps require user interaction, but the back-end support needs to be there first.
Second, it's not entirely true. The diagram shows that TLCToken inherits from MHActor, which promotes and simplifies the rendering of animated graphics in the engine. Also, the diagram mentions methods like sortByAttackValue() and sortByDefenseValue(), which will provide sorted lists to be displayed and selected from in the Attack command and the Defend interface. The properties of the token stacks are also values that will appear on the token inventory display. So there's a lot of stuff that will support the UI, even if it's not explicitly represented in this diagram.
Satisfied? Is everybody happy now? :)
A project journal for the Team Laser Combat game by Michael Henson.
No comments:
Post a Comment