4 ms·
disheartened? we've basically said the same thing. as for the wizardry - it's jquery (or zepto or something else), not backbone that does this. while backbone
by derickbailey 15y ago
disheartened? we've basically said the same thing.
as for the wizardry - it's jquery (or zepto or something else), not backbone that does this. while backbone integrates with and uses jquery heavily in the views, i don't think it's a fair claim to say backbone creates facilitates those user experiences. it helps us organize our code effectively so that we can create those user experiences in a well structured manner.
and come on, Jeremy... you know how much I love backbone! it's 80% of what I blog about these days! :)
- eric-hu 15y agoYour modelbinding plugin looks like it handles form-model binding really elegantly. Any intention of packaging it as a gem as well? I've been using the backbone-rails gem and modelbinding would go nicely with that..
- derickbailey 15y agoI thought about that when I first wrote it but decided not to, because it's not a ruby app. The backbone-rails gem provides some convenience generators and other things... but I'm not sure I see the value in packaging the modelbinding plugin as a gem. Is there a specific reason you would like to see that?
- eric-hu 15y agoSorry for the late reply. I personally like having gem wrappers as it makes installation, upgrading, checking for upgrades, and removal easier. These are all just little things, but they add up over many plugins.