notion of a global group (though we implicitly define one in InvocationCodes)
added a mechanism for directors (which generally handle the client side of
invocation services) to register their interest in bootstrap service groups so
that the whole goddamned complex business can happen magically behind the
scenes.
If you instantiate a director, it will automatically register interest in the
service group it needs and everything will work. If you don't use the director
code, you don't get the services and you can safely exclude all of that code
from your client even though the services are still in use on the server (and
presumably used by some other types of clients).
This is going to break all the builds, which I'll soon fix. Then I'll go write
all this in ActionScript. Yay!
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@4552 542714f4-19e9-0310-aa3c-eee0fc999fb1
These are the preferred way to get instances of Boolean, Byte,
Short, Character, Integer, Long, Float, and Double object.
It's always made sense for Boolean objects, and with 1.5 these factory
methods were blessed as the proper way to get instances unless one
absolutely needed a distinct object.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@4145 542714f4-19e9-0310-aa3c-eee0fc999fb1
genericize Narya data structures, nor make the existing code type safe. That's
going to be an extremely large project.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@4007 542714f4-19e9-0310-aa3c-eee0fc999fb1
databases configured to use utf8 encoding for their strings.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@3899 542714f4-19e9-0310-aa3c-eee0fc999fb1
(inStudlyFormat), it's just the constant that we use to reference that field in
code that's upper case. So we need to convert those as well. And I moved that
code into a documented method.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@3884 542714f4-19e9-0310-aa3c-eee0fc999fb1
its method documentation). And I was doing the wrong thing with event names
which were already unstudlied (but are also uppercase).
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@3883 542714f4-19e9-0310-aa3c-eee0fc999fb1
generator. It handles inner classes slightly differently and prepends a
project-specific header to the generated classes.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@3239 542714f4-19e9-0310-aa3c-eee0fc999fb1
in the prefs. Thus we can now have DSets of arbitrary data types in our
run time config objects, with swanky custom UI no less.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2978 542714f4-19e9-0310-aa3c-eee0fc999fb1
distributed objects which contain our configuration parameters; those
objects once registered with the ConfObjRegistry will automatically be
populated from appropriate stati config files and modifications to those
objects (made through the standard admin config interface) will
automatically be mirrored out to the preferences that override the values
specified in the config files (which override the default values defined
in the config object class definitions).
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@1735 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