Yes. I am looking at postcss sort of functionality - because that is how the defacto css framework tailwindcss works!
https://uniformcss.com/ this project looked interesting to me - scss based utility css framework. I wondered if I can get on with dart_sass also. But, the project looks in very early stages. I can use css, but not exactly a designer. So, hesitant to use.
World across - nationality is trending. In software - native applications are trending. Let us see where this takes us to.
https://deno.land/x/postcss@8.3.6 ← this is postcss on a rust powered runtime. Though afaik I read there are still some problems with tailwindcss on it.
Trivial question: how do you pronounce HEEx? “He-ex”, “heeks”, “H-E-E-X”?
“heex” => “heeks”
For the people interested, both https://github.com/miguel-s/ex_heroicons and https://github.com/miguel-s/ex_fontawesome got a new release which support Phoenix_HTML 3.0.
Thanks @miguels
Congrats on the release candidate! I’m really looking forward to these changes. I have a dead/live view application and it’s historically been challenging to share templates between the two. I also remember that learning the slightly different leex to be a bit of a hurdle when learning live views so I think this unification will be really nice for newcomers. Not sure yet if esbuild will be sufficient but will definitely give it a try as webpack often feels too cumbersome for what I get out of it.
Gave it a run-through foxusing on the LiveView stuff, then teied the esbuild and set up Tailwind CSS in this livestream.
I’m thrilled. Looking forward to this being mainline. I want to use it.
I would like to see a study how much time English speakers spend during their lifetime on average trying to know how something is spelled
Any idea when 1.6.0 stable will be released? What are the remaining blocking issues?
I don’t want to rush the release, I just am itching to try the new features and I prefer to wait until the stable version is out, and I’m not sure if it’s out soon or it might need a few more weeks in the oven.
Is there an intention to provide Phoenix.HTML.Form
& friends as functional components?
To match <.form ...>
, <%= text_input ... %>
→ <Form.text_input (or just input?) ... />
?
Really enjoying 1.6 so far, .heex
is great (especially once slots appear), live_session
looks like it solves some awkwardness I had to deal with from my last project.
I’m guessing that long term the answer is “yes”. For short term, Surface already has those. I’ve used them in my app - pretty sweet.