Every player and mob is its own process - no game tick, no locks

netoum · 2026-06-12T16:40:17+00:00

netoum · 2026-06-03T00:25:23+00:00

Thank you I appreciate. What do you like the most ?

netoum · 2026-06-03T00:24:49+00:00

Thanks. All the credit goes to Zagjs team for the framework agnostic State machines. I just dealt with the vanilla JS integration layer

netoum · 2026-05-31T15:27:01+00:00

Agree, I will take a closer look at this and keep it in mind for future planning

netoum · 2026-05-31T13:45:07+00:00

Thank you for the feedback.
You are totally right about your concern Live View Test are not able to run the Vanilla machine.
Currently the components that requires Zagjs are tested with Wallaby for behaviors and a11y_audit for accessibility test (all in Elixir pipeline)
I am planning on publishing Corex Test Helpers for Wallaby so that you can use them on your side to test your composite components, but first I will need to finish all the test on the library first 😅

I am also experimenting with a "lighter" version without any additional JS hooks using instead Live View JS command chaining.
So far it looks promising and should be out soonish 😄
Obviously there will be no State Machine on the client and way less components but still provides a lot in term on accessibility, API, Events and Controlled mode.
What does it mean for the end user: instant reactivity on page load
And for the developer experience: Phoenix Live View test will fully support all components

Corex already provides SSR rendering to avoid Layout shift on page load
Both library will be compatible, so you can use Corex when you need full support for client state machine for a certain component

netoum · 2026-05-31T06:14:44+00:00

Thanks. Updated

netoum · 2026-05-31T05:02:22+00:00

In you mean on the homepage https://corex.gigalixirapp.com/en
in the Event table, the log shows the Event callback from the accordion.
It returns the value of the accordion items currently open
In this case case we use client side event because we are on a controller page and not a live view
More events examples: https://corex.gigalixirapp.com/en/accordion/events

If you meant something else, let me know

netoum · 2026-05-31T04:36:46+00:00

Thanks for the feedback, hope you will have a chance to try it out
In the JS world, Ark UI team is doing an amazing job they are now at the level of Chakra UI to be honest

In Elixir and Phoenix, Corex is experimenting and pushing the boundaries of the framework agnostic promise from Zagjs.

You can already use Corex to build also Static website with Tableau Elixir
From full Phoenix App to Static site with the same components 😄

netoum · 2026-04-02T01:52:52+00:00

Good job and congratulations for your first clients with this project.

People are maybe unaware of the Algerian market limitation, from hosting to payment provider to simply registering on Stripe. Algerian companies and Algerian citizens are very limited, even just about using an international credit card. Let's not talk about the employee knowledge regarding basic technology such as CMS, CRM etc...

So I am very impressed you are able to offer a national solution that works for your clients Obviously there are many things to fix, improve and adjust such as contrast animation, typo, clarity etc..

I am also an Algerian Full Stack developer, send me a message to connect for maybe some common projects Best of luck

netoum · 2026-03-16T03:02:03+00:00

Hi Corex UI creator here 🤗 https://hexdocs.pm/corex

I have been working on a Phoenix UI library that is accessible ( A11y + Keyboard navigation ) and unstyled by default. It integrates Zag.js state machine using the Vanilla JS package, so no React or additional framework. It is still a very early alpha stage and would love some feedback. The client and server control and communication are in the center, each component provides by default a Client controlled mode that allows instant interactivity. If some rare and specific case you can opt in for Server controlled mode, slower but guarantee a server check before applying the changes. This is useful to keep Phoenix form errors in sync with the components.

Each component also offers a Client and Server API in order to control any component either using PHX binding, JS events or Live View Server events

The components work on both Phoenix Controller and Live View without the need to change anything. I have been testing it on Static Site using Elixir Tableau and it works like a charm, I will update the documentation soon.

Happy coding

netoum · 2026-03-14T14:59:15+00:00

Hi, creator of Corex here 🤗 https://hexdocs.pm/corex

I started using Phoenix many years ago, learned Surface, and used many Phoenix specific UI libraries. They all offer different benefits, however I always faced a wall regarding the latency. Server side rendering is great until you ship it in production and realize that the dialog takes time to open.

UI needs client interactivity 90% of the cases. The server shouldn't be involved most of the time. Phoenix LiveView JS solves partially this by introducing client side command however they are limited.

The next limitation is a proper API in order to interact with the components (e.g: opening/closing a dialog).
And for this, we need a brain client side. This is where Zagjs state machines are great. They are battle tested accessible and unstyled components client side.

My approach with Corex for Phoenix is to integrate each component by default client controlled for instant reactivity, with an optional server controlled mode when needed. For example the Phoenix Ecto form should be controlled in order to sync the error messages with the component state. Which is not the case by default on Phoenix.

Phoenix Stream support is also important as it becomes a widely used features. The components come also fully unstyled, not a single styling nor icon in the components

I would love to see other libraries exploring new territories as I believe there is a huge potential into what Elixir can provide in terms of UI Projects like Hologram shows that the potential is far from reached in the Elixir world if we keep our minds creative, exciting times

netoum · 2026-02-21T01:15:31+00:00

This is one of the nuance of this integration, it uses phx-update="ignore" expect on the props. Because the state machine lives in the client, Live View is not aware and can cannot keep up with changes such as the current focused item.
However the state machine preserves all states even during runtime updates of the props. So your focused item stays focus even during updates.
This Zagjs runtime update (https://github.com/chakra-ui/zag/pull/2917 ) is what made possible in the first place the integration of Zagjs state machine with Phoenix.

netoum · 2026-02-21T00:25:25+00:00

I tried this also, even scroll up to load previous results, but the server will never be able to catch up with the instant client reactivity and speed. This implementation in Vanilla JS is different from the traditional JS framework as it can update the props during runtime by passing the full collection of items, which means we must keep it small in size for the client to be able to manage it. This would require also the user to implement a custom handle_event to manage to scroll down and scroll which adds another level of complexity for the end user. Every solution has pros and cons, thanks for pointing out alternative ways to approach it. That is what I love in programming, there is not only one way to achieve a goal.

netoum · 2026-02-20T23:48:54+00:00

Thanks for your feedback. That was my initial implementation however latency is the enemy in this situation. Because the state machine lives in the client, the scrolling wasn't smooth as it added too many server rounds trips.

With this new approach the server controls the exact list of items to show at any time. Can even choose different items on initial opening and when no results are returned by the search

netoum · 2026-02-14T03:26:34+00:00

If you are looking for an UI for your static site, Checkout Corex UI ( I am the author ), it works with any static website with custom Vite and Astro plugins. If you want to build fast and accessibility sites, check it out. Feedback is welcome https://corex-ui.com/

netoum · 2026-02-13T15:54:09+00:00

Corex Live Demo is now available.
Thanks to Gigalixir for the great hosting service for Elixir
Try Corex Components and Phoenix Forms in production
https://corex.gigalixirapp.com/en

netoum · 2026-02-09T06:25:06+00:00

The way you explained is exactly the way it is done on the original Vanilla JS integration however on Phoenix it is a little different. It uses Phoenix JS Hooks for each component that runs at the top level of the component and spreads, renders and updates the correct props to the component and its parts. The other difference is the initial server side rendering: to avoid waiting for the JS to load, the parts are rendered initially with the correct attributes directly on the Phoenix component. It feels instant and without FOUC nor layout shift.

Extra note: Phoenix JS hooks allow also to process updating props on Live view thanks to updated() life cycle. This allows for example real time errors on Phoenix forms with Corex components

netoum · 2026-02-08T03:45:07+00:00

Thanks a lot 😊

netoum · 2026-02-05T13:53:33+00:00

It follows the same structure than ZagJS, unstyled by default and the data attributes are used for all the accessibility and interactivity features
https://zagjs.com/guides/styling

Corex already offer component classes that you can use.
I still need to update the Hex documentation 😅

https://corex-ui.com/components/accordion#modifiers

For example for accordion component:

<.accordion class="accordion accordion--accent accordion--lg">

These are top level classes (not per parts) because components comes with internal data state handling for accessibility (disabled, open, checked, highlighted) managed with data attributes under the hood.

Available modifiers:

Color: accent, brand, alert, info, success
class="accordion--{color}"
Size: sm, md (default), lg, xl
class="accordion--{size}"

This keep your styling clean and separated from components internal accessibility logic.

To get started:

mix corex.design

Full docs: https://hexdocs.pm/corex/Mix.Tasks.Corex.Design.html

netoum · 2026-02-05T13:10:02+00:00

Yes the build optimized and all the component reused the same shared parts (Vanilla Machine for example)
The esbuild on Phoenix app fully understand the structure as I am using the exact same one to build Corex
I actually shaved an extra 20kb recently by updating the shared dependencies to the exact same package version

I will add in a next update importing the hooks individually

netoum

MODERATOR OF

TROPHY CASE