JavaScript Interop in Hologram

[bartblast]

@Eiji

Well … that’s definitely disappointing for those waiting for new news, but we all know how life works in practice. No need to sorry, but if possible you always should consider people on second side.

I hear you! Really appreciate your extensive feedback! It’s super helpful!

@Eiji

Some people may think that project is completely abandoned especially if they see old issues that are opened for few years …

@Eiji

On GitHub I see old issues about mouse events.

The GitHub repository has been cleaned up!

@Eiji

Having in mind that there is also no roadmap it looks very bad - it’s as click is the only event Hologram supports. Size and performance are not as important for early steps as number of features. I’m working on some app and after seeing your post I considered to give hologram a try, but I don’t see any information about features that I already use in said LiveView-based app. For now I have no idea which events are implemented, which events are planned and so on … I cannot see what and when I can do, so I can’t plan anything. That’s a huge blocker for an early adoption / first research.

I understand the importance of having a clear picture of what works and what doesn’t. I’m currently focusing on documentation to help people get started. Soon there will be both a Roadmap docs page and a separate Events docs page. I’ve created a separate forum thread for discussion and announcements about new documentation pages: Hologram Documentation Updates/Feedback

@Eiji

DOM API

Hologram uses a virtual DOM under the hood, providing a declarative frontend layer that abstracts DOM manipulation. The goal is to eventually transition to more efficient mechanisms similar to SolidJS or Svelte. Could you share specific use cases where you need direct DOM access?

@Eiji

Push notifications, Fullscreen API and many other desktop features …

@Eiji

window-based and document-based JavaScript features - some JavaScript browser APIs depend on them (for example document.fullscreenElement)

These features are coming in future releases. If you have a specific use case in mind, creating a separate forum thread would be very helpful - this way the whole community can join in, share similar requirements, and maybe even suggest temporary workarounds. Plus, having focused discussions helps us better understand everyone’s needs.

@Eiji

We don’t have even a JSON support as JSON (new Elixir module) uses currently unsupported with special form and Jason also does not work. I know few sites that put JSON data in element attributes and use them inside JavaScript

Could you elaborate on your specific use cases that require JSON support?

@Eiji

I understand that bringing it all soon may be very difficult, so how about creating some workaround until 1.0.0 version is released?

if ~JS"return document.fullscreenElement;" do
  ~JS"…"
else
  ~JS"…"
end

Well written code could be easily migrated to 1.0.0 version, to … let’s say something like …

if Hologram.Document.get().fullscreenElement do
  # …
else
  # …
end

In such case one of the most important things would be to somehow pass action name, so we can use Hologram actions for events that are not officially supported. I believe that API like that would give people some possibilities to try Hologram on more real world cases.

While there was a working JS sigil implementation previously, I’m cautious about reintroducing it as it might create more challenges than benefits. Proper JavaScript interoperability is relatively straightforward to implement at this stage. If this feature is blocking adoption for you or others, I’m willing to prioritize it. After completing the documentation, I plan to create a dedicated forum thread to understand what features are blocking adoption for users.

@Eiji

I also took a look at hexdocs documentation … there is lots of modules and most probably many of them should have @moduledoc false or they are just completely not documented.

I’ve just created a GitHub Issue for this: Add @moduledoc false to modules that don't need HexDocs documentation · Issue #162 · bartblast/hologram · GitHub
Would you like to contribute a pull request?