Granted, the server might need to send some values to the display, but it should not matter in the least if the client alters those values

Yes, that's part of what I tried to explain. My apologies if that bit got lost in the ramble. Since it's a client/server architecture, changing object attributes cannot affect the server's copy unless I am dumb enough to add in logic to directly or indirectly propagate those changes in the protocol, which--and you'll have to take my word for this--I'm not. :-)

As you put it, though, how to "send some values to the display" from an OO design standpoint was pretty much my question. To that end, your suggestion of borrowing some wisdom from CPAN is well taken. Thanks!

In reply to Re^2: Moose class design for game by wanna_code_perl
in thread Moose class design for game by wanna_code_perl

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.