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. Some people may think that project is completely abandoned especially if they see old issues that are opened for few years … Honestly even I almost forgot about your project while I believe that I have very good memory …
On GitHub I see old issues about mouse events. 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.
We know that our code would be transpiled to JavaScript
, but we have no idea how to use many JavaScript
APIs …
DOM
APIPush notifications
,Fullscreen API
and many other desktop features …- We don’t have even a
JSON
support asJSON
(newElixir
module) uses currently unsupportedwith
special form andJason
also does not work. I know few sites that putJSON
data in element attributes and use them insideJavaScript
window
-based anddocument
-basedJavaScript
features - someJavaScript
browser APIs depend on them (for exampledocument.fullscreenElement
)
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.
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’m currently a bit busy as I’m working on my own project, but most probably in next month I would have more time for Hologram
. I think about writing some mix
tasks for it - maybe even port all phx
tasks.