Do you use Surface or basic Livecomponents?
I work with @cblavier, we only use Livecomponents.
matthieuchabert
Exadra37
Is this three column template shell(icons menu column, Admin sub-menu column, content column) a custom one or something we can find somewhere?
0
cblavier
Glad you like it, but it’s custom markup / CSS.
If you’re interested, here is the mobile responsive version : CleanShot 2021-04-26 at 14.07.12 · CleanShot Cloud
1
crova
Thanks for this table sample. I was wondering how to handle the headers of a table and you gave me some good pointers.
I had mentioned a form refactor to dig a bit on your library but decided to start with a table. Seemed less complicated.
Don’t be shy on the examples when you get time, they sure help understanding how to properly use the library!
edit: @cblavier Sorry to ping you but I wanted to check something before going hammer here:
Am I’m right in assuming that your are passing the headers: [id: "ID", ...] as a normal assign with Map.put(assigns, :headers, assigns.headers) and not with any kind of helper function you provide within the library?
Something like:
def update(assigns, socket) do
assigns =
assigns
|> extend_class("some-class")
|> Map.put(:headers, assigns.headers)
{:ok, assign(socket, assigns)}
end
And then in your render/1 you do a comprehension with for {k, v} <- assigns.headers do?
Did I get it right?
And if this is the case, any reason you’re doing your headers with a keyword list instead of a simple list?
3
cblavier
Ok 
Knowing that someone (else than me) is using the library cheers me up, so I’ll write some working examples of table components.
I’ll let you know in this thread when ready (this week I guess)
1
crova
No worries.
If I manage to get things right here I would gladly help you with some examples if you’d like.
2
Exadra37
I was not aware of what was storybook, but now I am
So, the question now his if your storybook is something that will be public available to test all live components that you and others release/build?
1
cblavier
If some people here are interested, yes we might indeed open-source this live_components storybook in a foreseeable future.
But like the original storybook, it would be an empty shell that you’ll be able to fill with your own components. The components we’re developing, even if somewhat generic, are really closely fitting to our business needs.
1
Exadra37
I really like the storybook concept thus I would like to see it public if possible.
I started a library like yours only for my personal projects, but each time I see one of your posts here I think in making the switch, and now this storybook is really enticing me
2
cblavier
@crova until I can package some documented examples in phx_component_helpers repo, here is a gist with our Table component and all its sub_components (rows, cells, buttons …)
It’s quite a complex component because it has a lot of optional features (actions buttons, header sorting, row by row checkbox / radio selection, select all)
3