Community
Participate
Working Groups
Looking at how we're registering in-page services we're doing stuff like: new mFavorites.Favorites({parent: "favoriteProgress", serviceRegistry: serviceRegistry}); we instead should be doing: serviceRegistry.register(new mFavorites.Favorites({parent: "favoriteProgress"}); -- The problem I think is that tying into the event api is a real pain. In particular you don't get access to the registrations eventTarget until after the service is registered. We need to make this easier by maybe using registering/unregistering calls on the service implementation to pass it what it needs or something similar.
The ServiceRegistration shenanigans are no more. If your service supports event you should use orion/EventTarget internally and expose addEventListener, and removeEventListener. The ServiceRegistry no longer does this for you automagically although it will handle the communication aspects if you plugin registers a service that exposes addEventListener and removeEventListener.
