Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to Safari
Join our community
Top Pro
•••Top Pro
•••Top Con
•••
Top Pro
•••Top Pro
•••Top Pro
•••
HTTP Streaming is a technique that keeps a connection between the web server and the web client constantly open. When the server has new information, it's immediately pushed to the client. This technique is used to considerably increase loading times, because using HTTP Streaming the web app can start rendering parts of the view that do not require any complicated calculations (for example CSS files) immediately. But to use HTTP Streaming in a Ruby app you need a template engine that supports it, fortunately Slim fully supports HTTP Streaming. See More
By using indentation rather than closing tags and eliminating curly braces, Haml is fast to code. For example This: <div id ="lower">
<div class="right column">
<div id="currentDate"><%= print_date %></div>
</div>
</div> Can be written as: %div#lower
%div.right.column
%div#currentDate= print_date See More
Liquid has some known issues with boolean algebra when it comes to some advanced expressions. Liquid::Template.parse("{% if false and false or true %} foo {% endif %}").render
# => ""
false and false or true
# => true It seems that Liquid simply parses from left to right, and if it finds a false and X it immediately returns false. See More
One development pattern used frequently is to create a "high-level" widget rendering a group of HTML tags, attribute values, and content to support a single use case, then decomposing that into domain-relevant smaller widgets ("nav bar", "user menu", etc), which in turn would be decomposed into smaller widgets, This eventually leaves you with a set of "leaf node" classes encapsulating a single tag with specific attributes and content rules; "helper" widget classes that encapsulate commonly-used configurations of the leaf widgets, with possibly multiple widgets increasing in scope up to an entire page-level widget. This also encourages the use of composition over inheritance; while each widget class must subclass a Fortitude (or Fortitude-derived) base class, the use of inheritance in your own widgets will tend to be quite rare. Typically, this will shout at the maintainer, "I'm a variation on Widget X", resulting in widgets that are by and large loosely coupled and highly cohesive. See More
Fortitude widgets can either encapsulate a single HTML tag, appropriate (and validated) values for attributes, and content, or they can compose multiple such widgets as a single, domain-language-friendly unit; for example, "navigation menu", which might involve a container div, a list, and list items confirming to various formats (for actions, separators, etc). This is textbook use of the interface-segregation principle. See More
Fortitude implements "widgets"; Ruby objects that encapsulate one or more HTML tags, with additional support for the view/app as a whole. By virtue of being Ruby classes, these widgets can use all the techniques used in any other Ruby objects in your app (composition, inheritance, etc), making it easy to develop working code rapidly. See More