Instead, why don't we eliminate the need for Apps in a browser to require HTML. Right now, our large scale app has one div inside the . It's just an anchor for our SPA built in React js. We should push for browsers that can launch from a .js file, rather than requiring html. Have a base UI.kit that can even keep css, or use javascript to stylize. I'd like the 'base' UI to be as skeleton and simple as possible. We can…
> Instead, why don't we eliminate the need for Apps in a browser to require HTML. Accessibility.
HTML6 proposal for single-page apps without JavaScript
31–40 of 177 posts
Re: HTML6 proposal for single-page apps without JavaScript
#32Re: HTML6 proposal for single-page apps without JavaScript
#33Re: HTML6 proposal for single-page apps without JavaScript
#34Instead, why don't we eliminate the need for Apps in a browser to require HTML. Right now, our large scale app has one div inside the . It's just an anchor for our SPA built in React js. We should push for browsers that can launch from a .js file, rather than requiring html. Have a base UI.kit that can even keep css, or use javascript to stylize. I'd like the 'base' UI to be as skeleton and simple as possible. We can…
> Instead, why don't we eliminate the need for Apps in a browser to require HTML. Accessibility.
(My project does not require supporting anything below IE 11, it's the greatest blessing, ever.)
Re: HTML6 proposal for single-page apps without JavaScript
#35Am I mistaken, but this kinda looks like XForms. Why not just use XForms? Edit: Obviously I understand that XForms isn't a viable option these days, but that is kinda my point. Why isn't XForms an option? Those reasons appear to apply to this proposal too...
Re: HTML6 proposal for single-page apps without JavaScript
#36Re: HTML6 proposal for single-page apps without JavaScript
#37Re: HTML6 proposal for single-page apps without JavaScript
#38I'm not necessarily opposed to something along these lines, except that it's basically already been tried: XSLT was essentially the inverse of this, where data endpoints were annotated with some static rendering descriptors. To me the XSLT approach seems cleaner, in that the URLs the browser is visiting are for the raw data itself, the URL scheme between machine and human is identical, and so on. XSLT also encouraged…
Yep. I used to love XSLT -- working in it finally forced me to understand recursion at, like, a deep cellular level -- but the whole time I was using it I knew it was a doomed language (because most people don't want to have to understand recursion at a deep cellular level just to be able to lay out a damn web page.)
Re: HTML6 proposal for single-page apps without JavaScript
#39Re: HTML6 proposal for single-page apps without JavaScript
#40Instead, why don't we eliminate the need for Apps in a browser to require HTML. Right now, our large scale app has one div inside the . It's just an anchor for our SPA built in React js. We should push for browsers that can launch from a .js file, rather than requiring html. Have a base UI.kit that can even keep css, or use javascript to stylize. I'd like the 'base' UI to be as skeleton and simple as possible. We can…
> Instead, why don't we eliminate the need for Apps in a browser to require HTML. Accessibility.