once since the observer list now takes care of that.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2062 542714f4-19e9-0310-aa3c-eee0fc999fb1
method invocation services and converted everything to the new style.
Could this be my biggest checkin ever?
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@1642 542714f4-19e9-0310-aa3c-eee0fc999fb1
made our internal order be LRU so we blow users off the chatterlist
in a smart way.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@1622 542714f4-19e9-0310-aa3c-eee0fc999fb1
received whispers from, and make available an interface by which
objects can register their interest in this list.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@1621 542714f4-19e9-0310-aa3c-eee0fc999fb1
to the newly simplified ChatDisplay interface, which now has but one method.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@1620 542714f4-19e9-0310-aa3c-eee0fc999fb1
the various chat displays once we've ascertained success or failure.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@1586 542714f4-19e9-0310-aa3c-eee0fc999fb1
server; chat director no longer needs to wait until we're logged on to
register itself with the invocation director.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@1393 542714f4-19e9-0310-aa3c-eee0fc999fb1
are translated by the client upon receipt. We love to translate.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@1319 542714f4-19e9-0310-aa3c-eee0fc999fb1
as they are intended to represent codes shared between the client and the
server. Made correspondingly necessary changes throughout.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@1240 542714f4-19e9-0310-aa3c-eee0fc999fb1
identifier which indicates which bundle to use when translating the
message for display to the client.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@1074 542714f4-19e9-0310-aa3c-eee0fc999fb1
types. Chat messages arriving on the auxilliary chat objects will be
tagged with the type that was associated with said objects when they were
registered with the chat director and chat displays can then render those
chat messages accordingly.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@807 542714f4-19e9-0310-aa3c-eee0fc999fb1
will probably need to be enhanced so that we can differentiate between
notifications from different objects on the client and render them
differently.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@804 542714f4-19e9-0310-aa3c-eee0fc999fb1
speak messages but come from the server and are displayed differently
(like in all red or something because these will say things like "The
system is shutting down in five minutes.")
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@501 542714f4-19e9-0310-aa3c-eee0fc999fb1
already have that around in 99% of the cases that you're implementing
message handlers and you more likely have it casted to the type you're
interested in and don't get any use out of that extra argument and have to
import PlaceObject when you might not otherwise have had to.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@453 542714f4-19e9-0310-aa3c-eee0fc999fb1
with distributed objects rather than having a single handleEvent() by
which all subscribers are forced to hear about all events. Now one
subscribes separately and then adds onesself as any of a few types of
listener once they have access to the subscribed object reference.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@439 542714f4-19e9-0310-aa3c-eee0fc999fb1
changed to Presents and Party changed to Crowd. Whee!
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@431 542714f4-19e9-0310-aa3c-eee0fc999fb1
Michael Bayne