https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • f
    So I can't dynamically change the javascript at runtime.
  • f
    Which is what I want for that full Chris Granger / Brett Victor experience.
  • f
    🙂
  • f
    So right now I'm pondering the abomination that would be storing the whole javascript function as a string on one of the data- attributes and then eval-ing it somehow.
  • f
    (You can tell I'm not a javascript programmer)
  • g
    Yes, updating Javascript functions via SSE sounds like a bad time.
  • f
    A bad time... but also AWESOME.
  • g
    It's hard for me to decipher what you're actually changing via these push updates (sorry, I don't know the language you're using). But, what ARE you changing? Would it be possible to include most of that Javascript on the client ahead of time, and then just stream parameters down to it?
  • g
  • f
    This is pretty much out of the htmx wheelhouse now ... so very much not your problem...
  • f
    But I'm making a competitor to Simulink ...
  • g
    True 🙂 I am just interested in all of the use cases...
  • f
  • f
    So, Simulink is a development tool based on a dataflow model.
  • f
    Very much a data-push computational model.
  • f
    I've built the runtime engine.
  • f
  • f
  • g
    frantically clicking
  • f
    And now I'm trying to make a UI for it.
  • f
    So, computationally, it's a Kahn Process Network ... https://en.wikipedia.org/wiki/Kahn_process_networks ... which is to say, the same as every other dataflow-based no-code tool out there ...
  • f
    (This is basically a dataflow-based low-code-ish development environment).
  • g
    from the explainer video... "simply press the run button"
  • g
    if only...
  • f
    The nodes in the dataflow graph are distributed ... potentially over many different computers.
  • f
    Of course, because I do everything in 'hard mode' ... I want the UI for xact to be written in ... xact.
  • f
    Which means smashing the dataflow paradigm and the HATEOAS paradigm together repeatedly until something breaks.
  • f
    The blocks in the diagram are components.
  • f
    Sometimes they are not just components in the compute graph .. they are also UI components.
  • g
    Yeah, there's a lot going on in their explainer. Depending on how much of this you're duplicating, there will be several tons of Javascript running on your client browsers.
1...99100101...1146Latest