[wp-trac] [WordPress Trac] #21170: JavaScript actions and filters

[WordPress Trac]

#21170: JavaScript actions and filters
-----------------------------+-----------------------------
 Reporter:  koopersmith      |       Owner:  koopersmith
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:  Future Release
Component:  General          |     Version:  3.4
 Severity:  normal           |  Resolution:
 Keywords:  2nd-opinion      |
-----------------------------+-----------------------------

Comment (by MikeSchinkel):

 Replying to [comment:68 carldanley]:
 > Just to clarify, I'm not dismissing it rather just saying that it
 becomes cumbersome.

 I was really just replying to the ticket vs. replying to your posts
 specifically.  I wasn't ignoring your comments on purpose; your comments
 just caused me to see the ticket in my inbox again. I've been working with
 Backbone.js since I last commented on this ticket and now had some
 perspective to share.

 > It's a bigger decision to extend Backbone because we then need to
 include Backbone & underscore everywhere in core (frontend & backend) to
 make this events implementation available. If that's the route people are
 leaning to, that's fine with me.

 That's a good point. I'm obviously not in the position to decide any of
 that.

 What I have noticed is that the Events subset of Backbone is both elegant
 and small, and could be forked to load for when full Backbone is not
 loaded plus extended in a way that would be compatible with an event-only
 fork as well as full Backbone. FWIW.

 BTW, the more I learning about the Javascript features used to create
 Backbone.js, the less I like programming in PHP.

--
Ticket URL: <http://core.trac.wordpress.org/ticket/21170#comment:69>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software