3 ms·
Are you guys taking care to send as-plain-as-possible markup from the server to the client and then style it up to keep most the UI development in CSS or are yo
by rkalla 15y ago
Are you guys taking care to send as-plain-as-possible markup from the server to the client and then style it up to keep most the UI development in CSS or are you just sending through raw, styled HTML that gets inserted as-sent directly into the page?
This reminds me of the early days of Java Servlets when people would stream back HTML from inside their Java Servlet code to JSP pages to build it out... made it impossibly hard to edit the templates.
Then the Java world moved to templating engines, but it was still the same idea.
Just curious how you are managing this pain point (I am not a Ruby dev so maybe there is a well-known 'best practice' templating approach?).
- dhh 15y agoI'm not sure I understand the pain point you're describing. What's "styled HTML"? We're sending HTML across the wire that looks exactly like the HTML we used to render the initial page. It has classes, ids, and custom data descriptors. We have not experienced any pain doing this.
- rkalla 15y agoYou answered my poorly-worded question. Thanks.
- losethos 15y agoLoseThos has a document format "Ltf". The format supports local file links and graphics and trees and colors and page settings. It's kinda like an HTML language. This file converts to HTML. http://www.losethos.com/LTHtml/Adam/ToHtml.html http://www.losethos.com/LTHtml/Adam/ToHtml.html Your small minds cannot imagine something besides html or what? Short circuit? Don't get me started on arrogant Indian airheads. I tell them I wrote a compiler and they start talking down to me clearly having no clue they should be talking up to me.