Closed GoogleCodeExporter closed 9 years ago
Have to decide what says on the outfox object and what moves to the audio
namespace.
outfox.init should stay put. The management of the event queues should stay
put. The
add and remove observers should become generic on the outfox object and the
audio one
should be a facade with easier to use parameters.
The startup protocol currently uses a set-config response from the server to 1)
indicate the server is ready and 2) indicate the default channel properties.
This
mixes audio specific functionality with the generic startup routine. Need to
factor
it out.
The outfox object might also needs to grow a startService() method so that only
the
services needed by a page can be launched instead of all of them.
outfox.init(div)
var deferred = outfox.startService('audio');
deferred.addCallback(function() {
outfox.audio.say("hi when ready");
});
deferred = outfox.startService('joystick');
deferred.addCallback(function() {
var js = outfox.joystick;
js.addObserver(some_other_callback, js.STICK0);
});
Original comment by c...@unc.edu
on 13 Sep 2008 at 3:50
[deleted comment]
In services branch rev 110
Original comment by c...@unc.edu
on 23 Nov 2008 at 6:23
Original issue reported on code.google.com by
c...@unc.edu
on 5 Sep 2008 at 10:54