Oh, if you look at the code Scott wrote to create dev teams, it seems really clean.
When the wrapper classes are ready for searching by name, you can simply do object.getByName(String, Callback) and you don't need to use any services. It's purely about having easy and clean code (not having to have many places using different services). There's nothing wrong with creating another instance of the service, but it would be nice to have the static service wrapped around by the wrapper classes. The initialising happens in Mugle.java -> OnModuleLoad(). On Mon, May 16, 2011 at 4:52 PM, Matt Giuca <[email protected]> wrote: > > The reason I have the services bound to the wrapper classes makes it easier >> for us not to be initializing Services everytime. >> >> > Sorry? I don't follow this. Is there a reason why I *shouldn't* be > implementing the above interface? > -- *Prageeth Silva*
-- Mailing list: https://launchpad.net/~mugle-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~mugle-dev More help : https://help.launchpad.net/ListHelp
