Rename?

[raimohanska]

The name bacon-jquery-bindings is not funky. I'm already calling it BJQ for brevity. Maybe BBQ or Barbeque instead?

[wolfflow]

Is there need for jquery in name? Will be there moar bindings, not related with jQ? Just for fun, my picks are bacon-snout and bacon-hogswatch (http://wiki.lspace.org/mediawiki/index.php/Hogswatch) =)

[wilkes]

BBQ :+1

[wolfflow]

Bacon Pancakes =))) http://www.youtube.com/watch?v=1eO5U_uN7DQ

[joefiorini]

Personally I'd vote for bacon.jquery just for the clarity and obviousness. I could see the potential for someone creating a bacon.mootools, or bacon.yui in the future.

[raimohanska]

Well yeah, that would make sense. Funny names don't really help people to find the relevant plugins.

[wolfflow]

Ok then. But, there are much more things in bacon-jquery-bindings which are not directly related or depend on jquery ) Model, Lens and Binding for instance. Maybe these ~150 lines of code could be the part of the core bacon sometime? And then all jquery-binding project would be nothing more than a renewed Bacon.UI ? I think that would prevent later code duplication in possible bacon.yui, bacon.mootools, etc.

[joefiorini]

So would Bacon.UI be the home for any DOM toolkit bindings? I still need to wrap my head around Lens & Binding, but maybe they could go into one repo together?

On Mon, Aug 5, 2013 at 5:12 PM, Daniel K notifications@github.com wrote:

Ok then. But, there are much more things in bacon-jquery-bindings which are not directly related or depend on jquery ) Model, Lens and Binding for instance. Maybe these ~150 lines of code could be the part of the core bacon sometime? And then all jquery-binding project would be nothing more than a renewed Bacon.UI ? I think that would prevent later code duplication in possible bacon.yui, bacon.mootools, etc.

— Reply to this email directly or view it on GitHubhttps://github.com/raimohanska/bacon-jquery-bindings/issues/5#issuecomment-22141379 .

[wolfflow]

Maybe, but not sure, cause each binding needs well separated tests) Also, there could be non-DOM ones, such as Node.js bindings, such as my experimental Bacon.FS one, a bit inspired by rx-fs

[joefiorini]

That's a fair point. Then what about making them each separate? bacon.jquery, bacon.yui, etc?

On Mon, Aug 5, 2013 at 5:39 PM, Daniel K notifications@github.com wrote:

Maybe, but not sure, cause each binding needs well separated tests) Also, there could be non-DOM ones, such as Node.js bindings, such as my experimental Bacon.FShttps://github.com/wolfflow/Bacon.FS/blob/master/Bacon.FS.coffeeone, a bit inspired by rx-fs

— Reply to this email directly or view it on GitHubhttps://github.com/raimohanska/bacon-jquery-bindings/issues/5#issuecomment-22143084 .

[wolfflow]

That's right) The next step is -- to familiarize myself with yui & mootools, or simply make a port from corresponding rxjs plugins)

[joefiorini]

What do you think about normalizing the API across DOM library binding plugins? That would make it easier to eventually build frameworks or toolkits on top of Bacon and plugin whatever DOM library you prefer.

On Mon, Aug 5, 2013 at 5:50 PM, Daniel K notifications@github.com wrote:

That's right) The next step is -- to familiarize myself with yui & mootools, or simply make a port from corresponding rxjs plugins)

— Reply to this email directly or view it on GitHubhttps://github.com/raimohanska/bacon-jquery-bindings/issues/5#issuecomment-22143771 .

[wolfflow]

Great! And it's an idea for scaffolding using grunt-init or yeoman )

[wolfflow]

Also, you might have a look at my first attempt to implement raw html ones: bacon-html-bindings

[joefiorini]

@wolfflow If we made Bacon.Binding a separate bower module, would that be useful to you in writing DOM libraries? I realize Bacon.Binding is only about 10 lines of code, so that may seem overkill, but if we can use it as the basis of every binding library, then maybe it would be worth it?

[wolfflow]

But Bacon.Binding references Bacon.Model, and it seems be more than 10 lines of code total. Any ideas? May Binding module contain also Model and Lens ?

[joefiorini]

How about a bacon-plugin-base module that contains all three?

[wolfflow]

Sounds good.

[raimohanska]

Renamed and moved.

https://github.com/baconjs/bacon.jquery