Thank you, I have updated it.
bluzky
bluzky
bluzky
Update Jun 8th
Release SaladUI
I decide to release on Hex: salad_ui | Hex
I know there are bugs, so please raise an issue on Github if you found one.
Added demo section
With some new dashboard example
What’s next
- I’m building a simple tool to convert from Shadcn React template to heex.
- SaladUI provide building blocks to build rich components. So I’m thinking of building some commonly used block to reduce boilerplate code
9
fuelen
Neophen
Re, select component:
It’s in my plans for a more comprehensive course on that input:
I need some help deciding on the “features and so forth” but will most likely try to follow closely to Radix ui.
It’s going to be a headless form web-component. So will be javascript heavy. But consumer friendly.
You can join my community here if you’de like to be notified about it:
2
heathen
Thanks for the interesting project!
What I’m playing with now is LiveVue from @Jskalc together with shadcn-vue which is using Radix UI under the hood.
I’m trying to convert styling into UnoCSS, but with Tailwind it seems to work well and looks really promising! I think to create live_view “proxy” components which would use shadcn-vue more primitive components underneath. It should help with UX a lot, at least in theory, keeping the main logic inside LiveView.
4
bluzky
bluzky
I don’t have much experience with Vue, but I believe that it provides better UX with complicated components such as select, combobox, …
1
DevotionGeo
Jskalc
Thanks for a shoutout @heathen !
In my project I’m also using LiveVue with shadcn-vue. It indeed works quite well and integrating it was a breeze, since Phoenix uses tailwind by default and LiveVue integrates Vite.
Thinking about your idea… it would require a fairly complex interop of LiveView / JavaScript, mostly when it comes to slots and nesting components. I’m not sure if it’s really possible, since vue components woul need to be rendered differently depending if it’s nested inside other component or not (to avoid creating multiple root-level components) 
But maybe I shouldn’t write here since it’s not the topic for it 
I think integrating client side hooks is a necessity for good UX. Recently there was a quite huge drama on twitter how LiveViews doesn’t scale because of delay between interaction and change in UI in Hey application. This could be avoided with hooks. Just it’s quite challenging to write complex components using hooks because it’s imperative - you have to control all changes by yourself, there is no way to declare a template and ask library to keep it in sync with the state… that’s why I’ve created LiveVue 
But all in all @bluzky you created something really neat, I’ll be using it in the future!
2