As of r12, dotsAllRemotes objects have to be created with a new() factory
method, and preferably with the dotsAllRemotes.new() factory as well. This
is irritating.
Users should interact with class constructors, not the manager singleton.
The dotsAllRemotes superclass constructor should be smart enough to
register the object as needed with the manager. It should just be able to
take an isTerminal hint when the manager wants it to.
So users should just have to implement a constructor with the isTerminal
argument, passed to super's constructor.
In addition, the new() factory conflicts with the singleton theObject()
factory, which has been a headache for dotsTheScreen, which is a remote and
a singleton, and has already required a registration process separate from
the class constructor. All remote classes should just use a similar
registration process.
Original issue reported on code.google.com by Benjamin.Heasly on 11 Dec 2009 at 6:26
Original issue reported on code.google.com by
Benjamin.Heasly
on 11 Dec 2009 at 6:26