phlex VS Tilt

The community was a delight! I can't even count how many people I connected with, and it was just great to meet people whom I had previously only interacted with online. Also got to meet a lot of those people who significantly contribute to the Rails ecosystem. Everyone I said hi to was more than willing to spare time and nerd out and share experiences. I was also thrilled to connect with Philip, who shares my enthusiasm for Phlex. He provided me with some exciting ideas for creating an even more crazy yet cohesive form object with Phlex.

Why use ActiveAdmin or RailsAdmin: Brick is not nearly as configurable -- at least yet! With Brick you can drop in your own model / controller / view template and it will use it, but on its own you can not change theming / use it to do templating tricks / etc. Currently working hard to arrive upon a straightforward and logical approach so that all of this will be possible. Looking into Arbre (used by ActiveAdmin) and Phlex for inspiration.

Phlex is an incredibly refreshing gem created by Joel Drapper. It introduces a remarkable way to build views in pure Ruby, as exemplified below:

A few months ago I came across https://www.phlex.fun and thought it was a nifty little library that could be useful for creating components. Since then I've been playing around with it in Rails, using it more seriously, and finally took it to a point where I built a Rails application with 100% Phlex components and 0% Erb. The other crazy thing is I figured out how to inline the Phlex view components into a controller, so prototyping Rails apps feels vaguely familiar to prototyping one in Sinatra.

A colleague has been using Phlex and I’ve since tried it as well. For me having it all be straight ruby, in one file, has worked and just from my personal preference something I’ve enjoyed over view_components.

phlex

You might want to take a look at Phlex, which essentially has the same syntax: https://github.com/joeldrapper/phlex

The built-in view templates use Tilt's interpolated string engine, which avoids ERB dependency, but requires work to adapt for Rails. So, rodauth-rails' views generator imports already converted ERB view templates that use familiar Rails' form helpers.

If you want people using Rails to use this, turn it into a gem, and use Tilt to make it an actual template language. Generating ERB and saving it to disk like that is a terrible plan for a Rails app. Good idea for a static site generator, like Jekyll, but absolutely a terrible idea for Rails.

Cuba takes help from a lot of other technologies to bring the best of everything. For example, the responses in Cuba are the optimized version of the Rack responses. The templates are integrated via Tilt and testing via Cutest and Capybara.