petal_components
surface
petal_components | surface | |
---|---|---|
6 | 11 | |
744 | 1,994 | |
2.3% | 0.6% | |
8.6 | 7.9 | |
22 days ago | 7 days ago | |
Elixir | Elixir | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
petal_components
-
Elixir and Phoenix can do it all
There are component libaries for LiveView.
https://github.com/petalframework/petal_components
https://github.com/coingaming/moon
I personally wouldn't use React for components in LiveView, you are just adding more complexity to your application for no reason. It really not that hard to build components using JS and LiveView. In the end you get less complex components than what you would get with react.
-
Anyone interested in writing a Component Library for Phoenix
You might also look at the PETAL components and ponder improving their accessibility (or the default components that come with the latest version of Phoenix, or any of a number of other UI toolkits).
-
Making a CheckboxGroup Input
Nothing stops you from creating 1 component per file. That's what Petal Components library is doing for example: https://github.com/petalframework/petal_components/tree/main/lib/petal_components
-
Something similar to Vuetify for Phoenix LiveView?
Have you looked at https://github.com/petalframework/petal_components?
-
Petal - A HEEX component library using Tailwind
Homepage: https://petal.build/docs Github: https://github.com/petalframework/petal_components The goal is to have a library of components out of the box ready to go so you can start focusing on solving your clients (or startups) problems instead of getting bogged down in design/css. Write components like this:
- Anyone writing a live view component library? How do you solve testing?
surface
-
htmlgui.nvim - Create html + css + lua apps with neovim as 'browser'. ( proof of concept )
I should have been more clear that my intent was to create/use a compiler for some kind of component syntax. There are lots of them, from Surface (Elixir), Blade (PHP/Laravel), and JSX (React, Vue, Etc)
- Would you still choose Elixir/Phoenix/LiveView if scaling and performance weren’t an issue to solve for?
-
Why I selected Elixir and Phoenix as my main stack
There I learned more deeply about LiveView and Surface UI.
-
Something similar to Vuetify for Phoenix LiveView?
I think Surface is the ideal candidate for this. But it doesn’t have the components you are looking for but you can build anything with it. Hopefully, in future we can have set of headless components built using Surface 🤞
-
Single source of truth with Phoenix LiveView
I have worked with Phoenix LiveView and Surface-UI for about a year; I would like to share some of the things I learned the hard way.
-
Course/Extensive tutorials for Phoenix 1.6?
This is just an idea, but what about implementing using Phoenix.View(via use MyAppWeb, :view in your module)? Then assign I think has access to @conn. Then maybe work some magic to still allow Phoenix.Component syntax - but at this point, this is something I believe is a flow that might be in development. Try investigating / asking in Surface, because that is a lot more similar to React in its approach. In fact, I think Surface is where more aggressive features are pushed out, and ironed-out features get included into Phoenix. This was the case for Phoenix.Component, and HEEX.
-
Porting files generated by phoenix to surface
This post is intended to get you started with surface provided components. I provided the original code and surface versions so you can compare the differences yourself without installing anything. After installing surface following the installation guide https://surface-ui.org/getting_started add surface_bulma in your mix.exs, this will allow you to use the table component.
-
We Got to LiveView
I totally get the "Am I doing this the right way?" feeling, especially coming from Rails where everything was so opinionated and wanting to stay idiomatic.
Phoenix, while it does have opinions, is far less opinionated in the sense that it doesn't do it darndest to force you into certain conventions (for example, if your module name doesn't match your file name, Phoenix won't complain). Its generators do try and push you toward using good DDD practices (which is my opinion is a GREAT thing), but of course the generators are completely optional.
I don't have experience writing large LiveView apps but I would say that if you are familiar with any component-based frameworks (like React), I would take a look at SurfaceUI[1]. It simplifies a few "gotchas" in LiveView (though I would say they are very minor gotchas and worth learning about at some point) and gives you a component-rendering syntax more like React. Once you get going, you'll learn that LiveView doesn't have all the headaches that come with bigger React apps (like having to memoize functions or comparing props to avoid a re-render and whatnot). The recent release candidate for Phoenix 1.6 has made strides for a cleaner component syntax, but if you're having trouble with LiveView, Surface might bring some familiarity.
[1] https://github.com/surface-ui/surface
-
Phoenix 1.6.0-RC.0 Released
Have you seen Surface UI? Pretty cool. Collection of LiveView components. https://surface-ui.org/
- Surface UI – A server-side rendering component library for Phoenix
What are some alternatives?
Sobelow - Security-focused static analysis for the Phoenix Framework
react_phoenix - Make rendering React.js components in Phoenix easy
PhoenixBootstrapForm - Bootstrap 4 Forms for Phoenix/Elixir Applications
torch - A rapid admin generator for Elixir & Phoenix
Tarams - Cast and validate external data and request parameters for Elixir and Phoenix
phx_component_helpers - Extensible Phoenix liveview components, without boilerplate
Formulator - A form library for Phoenix
phoenix_live_view - Rich, real-time user experiences with server-rendered HTML
PinWork - PinWork(Pinterest for bloggers) built with ❤️ using Angular2 (4.0.0)
Raxx - Interface for HTTP webservers, frameworks and clients
querie - Compose Ecto query from the client side
plug - Compose web applications with functions