search

gmac / backbone.epoxy

Declarative data binding and computed models for Backbone
http://epoxyjs.org
MIT License
615 stars 89 forks source link

Are there any known issues when upgrading to Backbone 1.0.0? #4

Closed AndrewHenderson closed 11 years ago

gmac commented 11 years ago

Nope! Backbone 1.0.0 is great news for libraries like Epoxy because it enforces the stability of Backbone's API. Even then, the primary APIs that Epoxy deals with (Model get / set) have remained virtually (possibly entirely) unchanged since I started using the library in the v0.3.x days. The newest Backbone features that Epoxy relies on are the fantastic listenTo / stopListening Events methods introduced in v0.9.9 (hence Epoxy's minimum version requirement), and those were a long time in the coming.

Epoxy's edge-branch test suite passes with flying colors on Backbone 1.0.0, so go at it. The only testing issue I'm currently tracking is with the options binding running in IE6; the browser is old enough it seems that even jQuery hasn't managed to normalize its select menu behaviors. I'm going to see if that can be addressed without excessive code bloat to the core library; otherwise, I might just cut IE6 loose and set IE7 as the minimum. Once that's decided and the API has had some time to gel, then Epoxy too will be going to 1.0. As of today, edge branch includes all planned features for the core library.

gmac commented 11 years ago

As a followup note on the IE6 support subject: I've resolved the IE6 options binding issue, so it remains a supported browser... mind you, this effort is only included as a gesture toward legacy audience support. Heavy JavaScript is still best avoided when targeting a large audience segments on legacy browsers.