Extract bacon-model

[raimohanska]

The non-jquery specific parts could be extracted, including Model, Binding, Lens.

[joefiorini]

I think that's a good idea. What about setting up a naming convention for Bacon projects? So we'd have bacon.model, bacon.jquery, bacon.lens as separate plugins that could be installed via bower or npm. Perhaps for easier discoverability they could live under a baconjs organization on github. Thoughts?

[raimohanska]

Sounds good.

[raimohanska]

Are there any gotchas in moving the stuff from my personal account to the newly created baconjs account? I think it might be a good idea to collect the Bacon modules there.

[joefiorini]

I don't think so. Github will automatically redirect when you transfer ownership of/rename repositories, including when pulling through the CLI. So after you transfer to the organization, anyone visiting raimohanska/bacon.js would automatically be redirected to bacon.js/baconjs.

[joefiorini]

Waiting on yeoman generator mention in #8. @raimohanska, per #5, what do you think of pulling this out along with Bacon.Lens and Bacon.Binding into a bacon-plugin-base repo?

[raimohanska]

I'm thinking to move all plugins eventually into separate repos under the baconjs org.

Would you prefer having a monolithic plugin git repo instead?

oops

Ah, I missed something. So the question is whether Model,Lens,Binding should be separate or combo. I might put them together into bacon.model plugin under baconjs org. Rationale: Binding is tiny and depends on Model, while Lens is a helper required by Model. Later, we might replace Lens with a separate 3rd party Lens impl, possibly fantasy-lenses.

[joefiorini]

I almost always fall on the side of many small repos rather than monolithic
ones. It would be great to have all official plugins in their own repos
under the baconjs org. That will make it very easy for users to find
plugins that are available and help give them an idea of how to contribute.

On Wed, Aug 7, 2013 at 9:58 AM, Juha Paananen [email protected]:

I'm thinking to move all plugins eventually into separate repos under the
baconjs https://github.com/baconjs org.

Would you prefer having a monolithic plugin git repo instead?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-22252818
.

[wolfflow]

bacon.model would do.
Then I can finalize my binding project so there would be bacon.html right there , surely, if you will add it =)
I'm still not sure about implementing native form element bindings, need a strong research about cross-browser compatibility. The last things I'd like to have are: fromWebSocket (quite the same as fromEventTarget) and requestAnimationFrame.

[raimohanska]

Why not just use jQuery? What kinda platform r u targeting? I'm just curious;)

[wolfflow]

My targets are: some embedded browser systems, such as Smart TVs and set-top boxes, some of them are very slow or low on RAM, thanks goodness all of them have W3C-compliant browsers )(

Also I do have a rich front-end experience in UI for payment kiosks Typically, it were: IE6-7 hell + low performance CPU + 256/512 Mb of RAM, no jquery).

And, if there are document.querySelectorAll (plus lodash, plus bacon), the only need of jQuery is... ajax methods, which is could be replaced mostly with self-written ones. =) And tweenMax for faster animations(where possible). That's my point.

And also, I have a dream of making bacon haXe port someday...

[raimohanska]

Interesting stuff man! I was thinking it must be something along those lines. So there will be bacon in a kiosk;)

On 9.8.2013, at 1.08, Daniel K [email protected] wrote:

Some embedded browser systems, such as Smart TVs and set-top boxes, some of them are very slow or low on RAM, thanks goodness all of them have W3C-compliant browsers )(

Also I do have a rich front-end experience payment kiosks' front-ends (IE6-7 hell + low performance CPU + 256/512 Mb of RAM, no jquery).

And, if there are document.querySelectorAll (plus lodash, plus bacon), the only need of jQuery is... ajax methods, which is could be replaced mostly with self-written ones. =) And tweenMax for faster animations(where possible). That's my point.

Also, I have a dream of making bacon haXe port someday...

—
Reply to this email directly or view it on GitHub.

[wolfflow]

And of course, on tablets too =)
Actually, I've never used jquery.mobile and zepto is much slower, despite its smaller size than jquery.

[Dremora]

There are plenty of tiny AJAX libraries, some of them might be a suitable drop-in replacement of jQuery's AJAX functionality.

[wolfflow]

Take a look at what have I done recently: https://github.com/wolfflow/bacon.model
Can it be the part of baconjs family =)

[raimohanska]

Great!

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

I created release 0.1.0.

Now we should make bacon.jquery use this in a smart way :)

-juha-

On 26.11.2013, at 11:16, Daniel K [email protected] wrote:

Take a look at what have I done recently: https://github.com/wolfflow/bacon.model
Can it be the part of baconjs family =)

—
Reply to this email directly or view it on GitHub.

[wolfflow]

Already done, waiting for PR merge )

[raimohanska]

Released 0.4.0. What's left to do is to update Readme