Skip to content

The scope of reactionview and the herb dependency #93

@ceritium

Description

@ceritium

Hi! First of all, many thanks for your work, it's amazing. I prefer Haml, but when I have to work with ERB, ReactionView gives me the energy I need or something, I don't know, but ERB doesn't feel so bad.

Lately, I was doing some experiments with Haml, as I mentioned in #14 (comment), and I investigated the source code a bit.

As I understand:

  • reactionview depends heavily on Herb for some features
  • but some others like the "herb-floating-menu" and the Render Times would not require Herb. Actually, I did (with Claude) a small gem revelio to port those features to Haml/Slim/ERB and added a few more. I did it before notice I can use Reactionview with Haml with a small initialiser (as I described in the comment above). I would be happy to yank it in favour of the original reaction view if I fully understand this gem's scope and if it matches my needs.
  • You plan to add more features like Reactive Templates. Probably, this will depend heavily on Herb.

We can make the "herb-floating-menu" independent of the herb gem while keeping the other validation overlays in place. What do you think? Herb is amazing, but the "herb-floating-menu" is amazing too. It would be a shame not to be able to enjoy it because we are not using "erb/herb", at least until you release the reactive templates, then we will have no excuses.

Because I was adding more to the overlay, it became too much info on such a small UI, so I asked Claude to prototype a companion and optional extension.

Image

What do you think? Again, many thanks for everything.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions