#Avadatheme #avatarupload #avatars #backbonejs #bpavatar #BuddyPress #BuddyPresssettings #Debugging #frontendbugs #memberdirectory #pluginconflicts #profilepicture #sitediagnostics #themecompatibility #troubleshooting #userprofiles #wordpress #WordPressadmin #WordPresssettings #WPdiscussionsettings
#backbonejs
Got a notification that #BackboneJS has released a new version and was instantly mentally transported back to happier simpler times.
Still an example of clear, well-documented, and elegant (as it gets) #Javascript: https://github.com/jashkenas/backbone/blob/master/backbone.js
@papa_alpha_papa Interesting! Could I apply your benchmark to the #BackboneJS Events interface as well?
@aral Reminds me of #BackboneJS! đź’•
I think about 2 years ago I had a long thread over here about updating my 10+ year old SPA (#backbonejs, #javascript, #perl, #Mojolicious) to a MPA using just #htmx for frontend interactivity.
Well, I've been way too busy to even start any of that! But, in the last couple of days I decided to go for a hybrid approach. I've added some htmx components to my single page application. My app's dashboard finally provides me with some interesting reports, powered by htmx.
That should do for now :-).
Are people still using Backbone.js to make JSON calls inside the WordPress Admin as suggested in the Rest API docs?
https://developer.wordpress.org/rest-api/using-the-rest-api/
I want to get the latest post in a category from another site.
A beginner #webdev asked whether there was any #MustacheTemplating equivalent of #Angular's ngStyle. I answered on #StackOverflow with a short tutorial on how this can be achieved with #BackboneJS and #MVC.
@linear I don't know whether you work in JavaScript or Python, but out of principle: please know that you would be welcome to contribute to any of the projects I maintain. That's #UnderscoreJS, Underscore-contrib, #BackboneJS, #Wontache and pip-review (currently trying to transfer the latter to a new maintainer).
A collection of Backbone.js tutorials and articles for building backbone.js apps, backbone design patterns, backbone with node.js and much more https://www.apaintingfortheartist.com/2023/08/30/a-collection-of-backbone-js-tutorials-and-articles-for-building-backbone-js-apps-backbone-design-patterns-backbone-with-node-and-much-more/ #backbonejs #webdesign #webdevelopment
Types of “components” (I’m being a bit broad with the word) that I’ve written as a #webDeveloper, in order of most created to least:
1. #webComponents
2. #backboneJS views
3. Proprietary frameworks
4. jQuery plug-ins
5. #reactJS components
And, there’s easily orders (with an “s”) of magnitude between all other “components” combined and the number of #webComponents that I’ve created and shipped in production over time.
I just released version 1.5.0 of #BackboneJS! It has
- an option to keep the trailing slash on a route URL
- bug fixes
- a code of conduct, security policy and many other doc improvements
Change log: https://backbonejs.org/#1.5.0
NPM: https://www.npmjs.com/package/backbone/v/1.5.0
#javascript
@danjac I still have a couple of SPA’s to manage that are about 9-10 years old. Written in #CoffeeScript 1 (not too bad) and #BackboneJS with a #Perl #Mojolicious backend.
Getting to run the JS dev stuff and keeping it up to date, or rather working with a newer Node version is challenging. Looking back it being a SPA doesn’t do much for 85% of these apps. I should’ve used some #jQuery instead for the interactive parts. That way I could’ve moved to #htmx without any issue.
I set out to answer an old question on Stack Overflow, but ended up writing a long tutorial on #BackboneJS, @jquery, #UnderscoreJS and #sprintf, including some advanced techniques. Comments, questions and suggestions welcome.
#JavaScript
https://stackoverflow.com/a/76237929/1166087
@selzero Both. 🙂 Bootstrap (and jQuery, which it depends on) is still valid. Not using anything else is old-fashioned, but if it works for you, why not?
I make full-blown client side applications, which benefit from a proper application framework (Bootstrap calls itself a framework, but is a widget toolkit). You could try #BackboneJS, which is lightweight and compatible with Bootstrap+jQuery. I maintain it. But if most of your HTML is static, or generated on the server side, you can do without.
@yenzie @gizmomathboy @genehack @randomgeek @ovid Nice parable. Can I add #BackboneJS, which was written by a vegan adventurer. It is a Toyota Hilux, which looks outdated but never fails you.
Like I said, this stack of #perl, #Mojolicious, #MySQL, #CoffeeScript, #BackboneJS and #Bootstrap has served me well this past decade. I've got several business critical webapps running in it.
The backend stays. The frontend gets replaced by mostly plain #HTML with #htmx and #TailwindCSS. This makes development a lot faster: less context switching as most of it is done inside HTML templates. Added but very nice bonus: less complicated and error prone build pipeline!
END
Having been in webdevelopment for about 20 years now (yikes!) using stuff like #MooTools, #jQuery, #Knockoutjs, #Backbonejs, #Marionettejs and #React sort of fixed the issue of making webapps interactive/reactive. It always felt cumbersome though as it required a lot of different stuff to make it possible. And now we suddenly had to manage state, validation etc. on the client side as well. More work.
But, I think I found the solution to this problem. One that reminds me of the good old days...
Trying to add some new stuff this week made me realise: I don't enjoy working on this. It has nothing to do with the backend though. I'll always love #perl and #Mojolicious. Both very stable and this past decade I had very little issues with upgrading if any at all.
The part of the stack that needs replacement is the frontend. It's one big #SPA (single page application) which means a bunch of HTTP JSON endpoints and #Backbonejs + #CoffeeScript + #Mustache taking care of the client side.
The webapp is written in #perl with #Mojolicious for the backend powered by #MySQL.
For frontend I went with #Backbonejs and #CoffeeScript. The state and support of modern #JavaScript features was limited back then, dare I say cumbersome. I also enjoyed CoffeeScript, even though I don't like #Python ;-). To make it look half decent I went with #Bootstrap as a CSS framework, but hardly any customisations.
For development I used #Vagrant with #VirtualBox, but since 4-5 years I moved to #Docker.
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst