Comments on: Ext.ux.MsgBus Plugin

By: Red

Red — Wed, 18 Jan 2012 16:27:30 +0000

I am little confused about how the actual filtering is performed. Because the subscription is always done for ‘message’ and the publish always fires the ‘message’ event. Is the filtering used in the publish method?

I am trying to get this to work on ExtJs4..it works allright..but Its basically working by creating a listener for message and firing an event on it. No subject filtering as expected. What am I doing wrong?

By: Totti

Totti — Thu, 09 Sep 2010 02:40:38 +0000

Very nice idea. I\’m gonna use this for my current project as to reduce the coupling.

By: Saki

Saki — Mon, 16 Aug 2010 01:14:52 +0000

Take a look at forum and/or learn section of http://sencha.com/learn Hint: override constructor.

By: joe

joe — Fri, 13 Aug 2010 18:30:11 +0000

Very useful stuff indeed. My approach of what I started today before i found your blog post was an event broker component that would pool all events that are relayed to it. Although I do prefer your solution of a message bus.

However, my approach was hooking the necessary code right into Ext.util.Observable, so that all objects that are descendants of Observable could communicate (right now anything thats not of the Component class won\’t accept plugins). However, I failed to override Ext.util.Observable properly, my skillz are not at leet

I\’d love to any pointers by anyone on how to override Ext.util.Observable properly, since it seems to be quite different to overriding Component, to fit the code into the override and have the messagebus be accessible by any descendant of Observable.

By: joe

joe — Fri, 13 Aug 2010 17:01:59 +0000

re: Konstantin

I think that is a limitation of Ext, since direct Observable descendents to not take the “plugin” property. tried it on a RowSelectionModel instance and it failed as well.

By: Konstantin

Konstantin — Fri, 18 Jun 2010 10:29:17 +0000

If you attach plugin to Ext.util.Observable or to your class, that extends Observable, it does not work. I wanted it for my core classes which just do some work, they do not appear visually. But ended up with changing parent for these classes to Ext.Component in order to get it working OK.

By: Michael

Michael — Sat, 08 May 2010 20:49:31 +0000

Saki,
is there a way to use this to build a chat? So two people on two different computers could chat?

By: Plant

Plant — Mon, 19 Apr 2010 09:53:18 +0000

Great plugin, it matched my needs exactly. I just had one question: before a subscriber component is destroyed, should it unsubscribe from all messages? It seems to me as if this is necessary to avoid orphaned subscriptions being left in the bus.

If it is neccessary, this seems to do the trick :

for (subject in this.subs) {
result = this.unsubscribe(subject);
}

Maybe it could be added to a function called on the beforedestroy event, as part of the plug in?

By: dixon

dixon — Wed, 07 Apr 2010 09:03:39 +0000

Nice plug-in! I will probably use it in one of my projects. Therefore I would need some information: is it possible to add the publish and un-/subscribe methods to the prototype instead to each object instance? Or do you think that\\\’s not a good idea …

By: Jorge Mariani

Jorge Mariani — Fri, 16 Oct 2009 00:04:03 +0000

Using onRender worked like a charm.

Thank you!