coen.bakker

coen.bakker

I appreciate being able to use AlpineJS inside my render functions, but often I catch myself wishing I could use Svelte syntax instead. And have the compiler turn the Svelte code to plain JS.

What do you think: how messy would that implementation get?

For example:

defmodule AppWeb.PageLive
  use Surface.LiveView

  def render(assigns) do
    ~F"""
      <div id="page">
        {#if @value and count == 0}
          <SurfaceComponent id="surface-component"/>
        {#else}
          <AnotherSurfaceComponent id="another-surface-component"/>
        {/if}

        <button on:click={handleClick}>
          Clicked {count} {count === 1 ? 'time' : 'times'}
        </button>
      </div>

    <script>
      let count = 0

      function handleClick() {
        count += 1
      }
    </script>
    """
  end
end

I am well aware that there are syntax conflicts right from the get-go between Svelte/JavaScript and Elixir/Phoenix/Surface. I reckon the best way of integrating Svelte is… not doing so. But rather extending Surface functionality into the JavaScript domain, or building a compiler layer on top of Phoenix from scratch – and being ‘inspired’ by Svelte.

Would it be a relieve to have such a tool… or not?

Showing Posts 1 to 6

cmo

cmo

{#if @value and count == 0}

How does the server rendered page get the count value from the front-end?

coen.bakker

coen.bakker OP

I’m thinking that the compiler could intervene. The syntax should first be altered, of course, to make it possible for the compiler to discriminate between Elixir variables and JavaScript variables.

For example, the syntax could use % … ; to indicate a JavaScript variable or expression, like: {#if @value and %count == 0;}. Not sure if % is reserved by Elixir or not – but could be another symbol.

A more elaborate example:

defmodule AppWeb.PageLive
  use Surface.LiveView

  def render(assigns) do
    ~F"""
      <div id="page">
        {#if @value and %count == 0;}
          <SurfaceComponent id="surface-component"/>
        {#else}
          <AnotherSurfaceComponent id="another-surface-component"/>
        {/if}

        <button on:click=%handleClick;>
          Clicked %count; %count === 1 ? 'time' : 'times';
        </button>
      </div>

    <script>
      let count = 0

      function handleClick() {
        count += 1
      }
    </script>
    """
  end
end

I can imagine that once you have solved all the possible syntax collisions, you could end up with (hopefully) pleasant syntax to work with. Not convinced myself, tbo, that that assumption is valid, but can’t help wondering.

hst337

hst337

I think it is writable, but it is just way too much magic to handle
First, you’ll need to precompute expression on elixir (server) side
Second, you’ll need to translate what’s left into Javascript (or write Elixir interpreter in javascript)
Third, you’ll need to make it interconnected back-and-forth with Javascript and Elixir components

This is just way too much magic. If I had a goal to achieve something like this, I would look into web assembly for client side

LostKobrakai

LostKobrakai

What I considered, but never managed to try, with svelte would be using svelte client side only and use a custom svelte store to communicate to the backend, which today could possibly even be something like live_json, though plain channels might work as well.

coen.bakker

coen.bakker OP

This part could be implemented as: only render this here on the server if @value (server) and count == 0 (JavaScript variable passed automatically to backend). But it could also be implemented as: only render this here on the server if @value (server) and if/once it is sent to the client only display/mount if count == 0.

The former is much more magical than the latter, I would say. And also more painful to implement. The latter option still gives you the syntax and the compiled JavaScript.

coen.bakker

coen.bakker OP

Interesting. Have an idea what it might be, but what do you have in mind? In general terms how would you utilize WA?

— All posts loaded —

Where Next? Top

Trending in Discussions Top

AstonJ
As the title says, please share what you’ve been up to with Elixir. Whether that’s been learning it, looking into it, making stuff with i...
2977 92995 915
New
caslu
I want to open this thread for you all to discuss and help those who really like Ash but are still hesitant to use it in a real project. ...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
GES233
I’m posting this in response to Jose’s recent tweet (Cr. link) : People are sleeping on Elixir for a coding harness: Hot-code swappi...
New
_mfierro
Hello, I wrote Stop My Hand, a Scattergories-like web application using Phoenix/LiveView as my learning project for Elixir (after readin...
New
marciol
It would be helpful to have a list of companies worldwide that hire engineers without prior experience in Elixir. Often, it can be quite ...
New
durvia
Anyone running long-lived stateful processes on BEAM? We’re building an AI agent runtime and would love to compare notes. We’re a small ...
New

Other Trending Topics Top

garrison
Hobbes is a low-level distributed database for the Elixir programming language. Hobbes provides a simple, safe, and scalable storage lay...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge &amp; Solve. They are GUI (Emerge) and State management (S...
New
wintermeyer
There are three potential reasons for members of this forum to have a look at https://vutuv.de You are tired or annoyed of LinkedIn. Yo...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews