https://github.com/latentflip/back-bacon

https://github.com/latentflip/back-bacon

Last synced: 30 days ago
JSON representation

• Host: GitHub
• URL: https://github.com/latentflip/back-bacon
• Owner: latentflip
• Created: 2013-01-21T22:11:01.000Z (almost 12 years ago)
• Default Branch: master
• Last Pushed: 2013-01-24T08:32:01.000Z (almost 12 years ago)
• Last Synced: 2024-04-15T02:17:36.075Z (7 months ago)
• Language: JavaScript
• Size: 7.97 MB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Some thoughts on what this is:

- I like backbone because it's nice and lightweight, and no nonsense.

- I don't like:

  - Lack of computed properties

  - Lack of view bindings

  - Boilerplate

  - Dependence on RESTful APIs, how does one merge a realtime API with a RESTful one?

- I like

  - Bacon.js

  - I want bacon in my views

# Models

- I like backbone models

- But I want property composition

- And I want multiple events to happily update my models

- So what needs to happen

  - Get events as eventStream, like 

  - property getters, let's say getBacon, which returns a (cached?) bacon property for a model's property

  - property pluggers, let's say plugStream, which adds a property stream to an event bus which updates the backbone property

    - Hmm?

      - Is there a difference between a computed property and a live property?

      - How many axes should be able to plug into a stream