Mitar

Cool. It would be interesting to see this.

I propose this should be a separate package, but feel free to make any pull requests if you need any integration points or anything else. And feel free to ask...

Hm, is there any features of Blaze Components needed for you to make this work?

Hm, I do not think we talk about the same thing. So as I [explained here](https://github.com/timbrandin/meteor-sideburns/issues/20#issuecomment-146446272) I really think that what is needed is a very basic core: common component...

We will see how Blaze 2.0 will go. It is a community effort. So I have my own ideas how I prefer things, so if community would agree on moving...

I think this is a question without an answer, because I do not believe in libraries winning against other libraries, but in them addressing needs of their users. Both Blaze...

Then we need in some way also many others as well, no? I think we could create a `Mixin` extension of `BlazeComponent` which has this helpers. So if you want...

So maybe `BlazeMixin` could be a good name?

No, let's for now use just the package.

``` mixinSibling(nameOrMixin) -> mixinParent().getMixin(nameOrMixin) ``` Is probably not doing what you want. This could get you into a loop. Especially if you are getting by name. You could have cycles...