Create view message bus

[tbosch]

----
Render API:

class RenderMessageRef {}

class Renderer {
  sendMessage(view:ViewRef, type:string, data:StringMap):RenderMessageRef;
  setMessageDispatcher(view:ViewRef, dispatcher:MessageDispatcher)
}

class MessageDispatcher {
  dispatchMessage(type:string, data:StringMap, inReplyTo:RenderMessageRef)
}

------
App side:

class AppView {
  sendRenderMessage(type:string, data:StringMap):RenderMessageRef;
  waitFor(List<RenderMessageRef>):Promise<List<any>>
}

-----
Render side (under src/render/dom):

class MessageManager {
  handlers:List<MessageHandler>
}

class MessageHandler {
  supports(type:string):boolean;
  handle(view:View, type:string, data:StringMap, messageRef:RenderMessageRef)
}

class View {
  sendAppMessage(type:string, data:StringMap, inReplyTo:RenderMessageRef)
}

[tbosch]

Very similar to EventDispatcher and EventManager/EventHandler

[pkozlowski-opensource]

@tbosch in the AppView interface you were proposing sendRenderMessage(type:string, data:StringMap):RenderMessageRef; but IMO we should also have a way of referencing individual elements. For example the class directive is a decorator directive that allows toggling classes on a particular element within a View.

So 2 questions here:

• How the proposed API would allow me to specify a particular element? Shell we add ElementRef or similar to this API?
• How a decorator directive could get a reference to the enclosing View? Is it injectable?

Sorry if this is messed up in my head, but before implementing those services I would like to understand how those would fit / play together in the real-life use case (class directive)

[tbosch]

Pawel, you can reference elements within a regular angular view via a bound
element index, which you can get on the app side via ElementRef.
However, imperative views will have their own way of locating elements (eg
a css selector, ...).

That's why the general interface of the MessageBus has no notion of a
location, assuming the location will be part of the data map.
On Wed, Apr 15, 2015 at 6:44 AM Pawel Kozlowski notifications@github.com
wrote:

@tbosch https://github.com/tbosch in the AppView interface you were
proposing sendRenderMessage(type:string, data:StringMap):RenderMessageRef;
but IMO we should also have a way of referencing individual elements. For
example the class directive
https://github.com/angular/angular/blob/master/modules/angular2/src/directives/class.js
is a decorator directive that allows toggling classes on a particular
element within a View.

So 2 questions here:

• How the proposed API would allow me to specify a particular element?
  Shell we add ElementRef or similar to this API?
• How a decorator directive could get a reference to the enclosing
  View? Is it injectable?

Sorry if this is messed up in my head, but before implementing those
services I would like to understand how those would fit / play together in
the real-life use case (class directive)

—
Reply to this email directly or view it on GitHub
#1297 (comment).

[pkozlowski-opensource]

OK, I see, thnx.

[tbosch]

Hi, I think this concept gets obsolete!
We have events for render -> app side communication, actions for app -> render side communication and imperative views. Together, they should allow to do anything!

[pkozlowski-opensource]

Wow, good to hear, since I wasn't that keen on this message bus and was struggling a bit with the impl. Will look at the actions.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}