These have been a long time in the making; and they’re barely the initial alphas, but the Practical Framework is officially open-sourced.
They’re 3.0 releases because they’ve gone through 2 internal revisions. Next up is:
If you’re curious:
A great read: animationobsessive.substack.com/p/rejecti…
After 3+ years of work and refining in private repos, I’ve finally published an open-source implementation for client-side error handling that should work for 99% of cases! github.com/practical…
This is still one of the best guides & approaches for progressively enhanced form errors. I’ve been running a version of it for 2 years; and will be open-sourcing that library in the next few weeks
After months of research and development, a new guide about how to build maintainable view layers in Rails (and overhaul an existing UI without stopping feature development) is live.
This is the largest thing I’ve ever seriously published, clocking in at about 8.2K words, with an open-source snapshot to boot
After a short break, I’m going to extract the framework-level code into libraries, then start the process of migrating Little CRM 💪
I’m currently in the middle of re-tackling the view layer for Practical Computer. Now that there are 2 apps + a framework, the complexity is high enough to actually tackle the problem comprehensively
So, from my view of the Rails View Layer landscape, you have the following paths:
Am I correct here? Am I missing something?
Sneak peek of a new feature that’s coming soon to Little CRM
Having fun with error messages once again
I’m starting to add notifications, reminders, followups, prompts to Little CRM. Let me know your thoughts and what you’d find valuable (and more importantly, what you’d find annoying!)
Now that I’m in the phase of my hiatus where I’m figuring out the balance of app work + music, updates are back on the menu! 💪
A new mini-tool from the Practical Computer labs: an Extism plugin to process Mustachio templates: github.com/practical…
Overall, I’m impressed with how Extism is structured. Being able to use WASM to deal with a thorny issue (running Mustachio’s official C# library in a Ruby codebase) with a small, cross-platform binary that can be embedded into the repo itself, dramatically simplifies the problem at hand.
The goal is to hand this off to Postmark directly, since this gives their entire ecosystem a huge boost in usability.