surface
Masonite
surface | Masonite | |
---|---|---|
11 | 9 | |
1,994 | 2,150 | |
0.6% | 0.5% | |
7.9 | 7.3 | |
5 days ago | 8 days ago | |
Elixir | Python | |
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.
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
Masonite
-
Portable Django
I would suggest Masonite [0]. It’s lightweight enough to replace Flask and has a plethora of built in features if you need to build a “production-ready” app. It tends to imitate Laravel in its project setup and naming conventions which, depending on your preference, can either be a boon or a bane.
[0] https://docs.masoniteproject.com/
-
Why I selected Elixir and Phoenix as my main stack
Masonite is a wonderful Python framework, much similar to Laravel I found in 2018. I even chatted with Joseph about it in the old Slack channels, before the community moved to Discord.
- Masonite
-
New Django debugging screen: Exceptionite 2
Masonite Framework: https://github.com/MasoniteFramework/masonite
-
Using Exceptionite 2 in Django with a single line
Exceptionite 2 is a debugging screen package written by the Masonite team. Although written by the Masonite maintainer team, it can be used in Flask, Django and of course Masonite.
- Have you heard about it?
-
The History of the Masonite Framework
If you want to learn more about Masonite, visit the GitHub page here: https://github.com/MasoniteFramework/masonite
- Passenger 介紹
-
PHP Laravel Developer who wants to learn Python quickly? You have to look at Masonite.
For those who like the concept and want to encourage the developer please don’t hesitate to give a little star for Masonite on Github: https://github.com/MasoniteFramework/masonite
What are some alternatives?
react_phoenix - Make rendering React.js components in Phoenix easy
Django - The Web framework for perfectionists with deadlines.
torch - A rapid admin generator for Elixir & Phoenix
Flask - The Python micro framework for building web applications.
phx_component_helpers - Extensible Phoenix liveview components, without boilerplate
fastapi - FastAPI framework, high performance, easy to learn, fast to code, ready for production
phoenix_live_view - Rich, real-time user experiences with server-rendered HTML
vibora - Fast, asynchronous and elegant Python web framework.
Raxx - Interface for HTTP webservers, frameworks and clients
Pyramid - Pyramid - A Python web framework
plug - Compose web applications with functions
Websauna - Websauna is a full stack Python web framework for building web services and back offices with admin interface and sign up process