andrielfn.com
⚡️ Backend Engineer 🔮 From Ruby to Elixir 🎨 UI/UX minded 🛠 DevOps enthusiast 🎨 Currently working on http://FluxonUI.com
61 posts
504 followers
52 following
Regular Contributor
Active Commenter
comment in response to
post
And the documentation: docs.fluxonui.com
comment in response to
post
Check all these new components live: fluxonui.com/components/d...
comment in response to
post
With server-side (LiveView) filtering
comment in response to
post
Autocomplete, an easy way to search for items
comment in response to
post
All fully accessible and keyboard navigable
comment in response to
post
Or to select multiple dates and a datetime
comment in response to
post
A better way to pick a date and a range of dates
comment in response to
post
RE headless components, I believe this will in theory be solved for what I envision for a Fluxon 2.0: the components living in the user's codebase instead in a hex package, so you would have much more freedom to shape the things the way you want.
comment in response to
post
You can send it to support[at]fluxonui.com. Can be a bug with the class conflict merging thing, but easier to say with the code.
comment in response to
post
Oh well, I never thought people would use tabs for something as different as that 😄 I'd say it's probably easier to build from scratch than customize the component. The complex part would be the WAI-ARIA stuff though. Any chance you can share the code you have so I can take a look?
comment in response to
post
True! It's just a few more lines of code but I can't also think on any downsides.
comment in response to
post
Nice! I'm still working on the docs, but here is a sneak peek of it docs.fluxonui.com/1.0.20/overv...
comment in response to
post
My main motivation is that with specific component functions I can control which attrs are supported in each variation e.g. range must set start/end fields, multiple only works with the regular date picker, time format only works in the time picker, etc...
comment in response to
post
This is quite funny, actually. We've been working on very similar project, the product names are alike and I believe we even share the same principles when developing these components. I've been a big fan of him since the early AlpineJS days.
comment in response to
post
All from scratch 😅 sounds crazy I know, but given the UX, aesthetics, and work well with LV, using an existing library would probably require a similar effort, if not more.
comment in response to
post
Confesso que pra mim ambas as formas parecem corretas. Acredito que usamos mais "meu"/"minha" no dia-a-dia por ser mais fácil dizer.
comment in response to
post
Nice! I think the presets would also make sense for single date, right? Like "today", "yesterday", "1w ago" etc...
And for the time picker, I just gave it a try; let's see how it goes, haha (and ignore UX, it's still terrible).
comment in response to
post
What non-core features would you like to see? Datetime? Presets? Multiple dates? Disabled dates? Multiple months? Jump to a specific year/month? Anything else?
comment in response to
post
Oh, and keyboard navigation kinda works too ⌨️
comment in response to
post
Here's what the component code looks like now. The radio buttons update the min and max values which then get patched by LV to re-render the component.
comment in response to
post
I usually avoid as much as possible adding dependencies, but I ended up using Day.js (2kB) to make handling dates easier. Currently floating-ui is the only dependency in Fluxon UI.
comment in response to
post
Sure! My idea is also to start the date picker as simply as possible and iterate over time based on users' feedback and needs 🙏
comment in response to
post
Thank you Petar for supporting my work 🥰 And don't hesitate to reach out if you have any bugs, suggestions or feedback!
comment in response to
post
You want to ruin my life 😆 do you have any good references for a datetime picker? There are a bazillion ways to do it in terms of UX/design, so I'm still unsure what's the best way
comment in response to
post
No big expectations please 😆 date pickers are a nightmare
comment in response to
post
Operator Mono (Light)
comment in response to
post
Yeah, in general I believe delegating it to a function is the best option. As I've been using it for demo and document some components this is very convenient.
comment in response to
post
The factory must grow
comment in response to
post
And I haven't played Space Age that much yet, so that might grow to a few more hundred hours or so 😅
comment in response to
post
I'd say 20~30% of my playtime was the PC on during the night doing research, but still it's a lot of hours played 😅
comment in response to
post
Say goodbye to your life 😆
comment in response to
post
Changelog: fluxonui.com/changelog#v1...
comment in response to
post
I've been using Hetzner + Ansible for a few years now. More recently I set up a GH action to simplify deploying new apps. I pretty much just need to add a deploy workflow.
comment in response to
post
Hey, thank you so much 🥰 I hope you enjoy it. Feel free to reach out if you have any questions, feedback, bugs, or requests for components/layouts.
comment in response to
post
Thank you so much Thomas 🥰 If you have any bugs, questions, feedback, component requests, don't hesitate to reach out!