remote-standalone
fragmentify-js
remote-standalone | fragmentify-js | |
---|---|---|
2 | 1 | |
0 | 0 | |
- | - | |
10.0 | 10.0 | |
over 10 years ago | over 6 years ago | |
JavaScript | JavaScript | |
- | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
remote-standalone
-
HTML First – Six principles for building simple, maintainable, web software
I published this article on Template Animation (aka DOM Templating) 12 years ago:
https://benkoworks.com/your-templating-engine-sucks-and-ever...
It fits nicely with this goal. My colleagues and I created a tool that allows HTML developers to work in HTML by compiling HTML using a Chrome extension, and then allowing developers to compile the same in their code platform of choice and operate on the DOM:
https://github.com/iaindooley/Fragmentify
https://github.com/iaindooley/fragmentify-js
Even if you're doing a SPA you can use this same method, by sending updates over the wire and doing the processing on the server. We created a standalone package that facilitated that by loading the initial page from the server then transparently allowing the server to send just the changes to the page and having them applied on the client side:
https://github.com/dgrinton/remote-standalone
The combination of "remote" and "fragmentify" and Template Animation/DOM Templating, in my opinion, would be a tremendous "retreat to move forward" in web development technologies.
-
We're breaking up with JavaScript front ends
Many years ago a colleague and I wrote a stand-alone version of a package for my own arcane php framework called Remote.
The idea was that you write in Web 1.0 and immediately get a Web 2.0 front end because it just updates what it needs to.
I still think this is the holy grail of frontends:
https://github.com/dgrinton/remote-standalone
fragmentify-js
-
HTML First – Six principles for building simple, maintainable, web software
I published this article on Template Animation (aka DOM Templating) 12 years ago:
https://benkoworks.com/your-templating-engine-sucks-and-ever...
It fits nicely with this goal. My colleagues and I created a tool that allows HTML developers to work in HTML by compiling HTML using a Chrome extension, and then allowing developers to compile the same in their code platform of choice and operate on the DOM:
https://github.com/iaindooley/Fragmentify
https://github.com/iaindooley/fragmentify-js
Even if you're doing a SPA you can use this same method, by sending updates over the wire and doing the processing on the server. We created a standalone package that facilitated that by loading the initial page from the server then transparently allowing the server to send just the changes to the page and having them applied on the client side:
https://github.com/dgrinton/remote-standalone
The combination of "remote" and "fragmentify" and Template Animation/DOM Templating, in my opinion, would be a tremendous "retreat to move forward" in web development technologies.
What are some alternatives?
clace - Clace is a web app deployment platform for internal tools
htmf - A minimalist partial html swapping library similar to HTMX and other libraries which create an MPA app and enhances it with a focus on HTML forms.
Fragmentify - Django like template inheritance for XML
- - Hyphen - An elegant custom element base class
tailgate - Client-facing generative-AI components without the fuss.
intercooler-js - Making AJAX as easy as anchor tags
unpoly - Progressive enhancement for HTML
qwik - Instant-loading web apps, without effort