MASON-INTEREST-L Archives

March 2017

MASON-INTEREST-L@LISTSERV.GMU.EDU

Options: Use Proportional Font
Show HTML Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Message-ID:
Sender:
MASON Multiagent Simulation Toolkit <[log in to unmask]>
Subject:
From:
"Abrams, Marshall" <[log in to unmask]>
Date:
Wed, 8 Mar 2017 03:18:52 +0000
MIME-Version:
1.0
Content-Type:
multipart/alternative; boundary="_000_21223B2A1BF34C28B1EA761EEB9B52C6uabedu_"
Reply-To:
MASON Multiagent Simulation Toolkit <[log in to unmask]>
Parts/Attachments:
text/plain (1280 bytes) , text/html (3407 bytes)
Not sure if maybe I’m missing something, but thought I’d ask.  OrientedPortrayal2D seems unusual in that it has no methods for controlling its intended variation, i.e. its orientation.  Instead one makes the agent implement Oriented2D.  By contrast if you want the color of a portrayal to reflect the state of the agent, for example, you can override a method in the portrayal class and set the color based on the state of the agent.  Then the agent doesn’t have have any features that reflect what’s going on in the UI.  Maybe there’s a way to control OrientedPortrayal2D that I’m not seeing, though.  Requiring that the agent implement Oriented2D seems like a small violation of the MVC model, but I suppose it’s not that different from defining bean methods and other tricks (e.g. implementing Propertied) that one can use to allow Mason to provide object inspectors with almost no work on the modeler’s part.

Thanks-

Marshall

Marshall Abrams, Associate Professor
Department of Philosophy, University of Alabama at Birmingham
Email: [log in to unmask]<mailto:[log in to unmask]>; Phone: (205) 996-7483;  Fax: (205) 975-6610
Mail: HB 414A, 900 13th Street South, Birmingham, AL 35294-1260;  Office: HB 418
Website: http://members.logical.net/~marshall


ATOM RSS1 RSS2