Відео

Thanks a lot, I will do my best!

Thanks Matt! Yes it's possible. There are 2 ways of doing that depending on the use case: include it directly in your main component, or use dropzones. I can cover that in a future video :)

@@jptrinhh very interested to see that in a future video :)

J'ai trouvé ! Il faut juste ajouté une flexbox supplémentaire. Donc 1 flexbox avec un array bind dessus. Une flexbox qui contient les checkbox component et l'élément text. Ensuite ils suffit de binder la data sur l'élément text et de display none le texte initial de la checkbox

J'ai du mal à tout comprendre mais content que tu ais pu trouver la solution :) Desfois il suffit de binder le bon objet et potentiellement aller chercher des éléments un peu nesté

@@jptrinhh En gros mon layout était comme dans ta vidéo : [ flexbox > [ checkbox-component] ] et j'essayais de bind une data de mon tableau sur le texte qui est par défaut "Checkbox" (dans le composant checkbox). J'ai ajouté une flexbox qui contient le checkbox-component et un élément texte comme ceci dans mon layout : [ 1ere flexbox > [ 2ieme flexbox > [ checkbox-component ] + [ text] ] ] Grace à cette structure j'ai pu récupérer la data de mon tableau pour la bind sur mon élément texte, puis j'ai caché le texte par défaut contenu dans le composant checkbox. J'espère que je suis plus clair que dans mon 1er commentaire, j'avoue avoir du mal à m'exprimer par moment ^^* En tout cas merci à toi, bonne continuation ;)

@@ThomAtome3D Ah yes, je viens de voir en plus ton post sur le forum WeWeb :) Merci pour le partage de la solution et bon projet !

@@jptrinhh Yes ;) c'est normal, merci et bonne continuation

Great suggestion! When it goes off the screen, do you mean for example, if the component is placed at the edge of the page, then the content that is revealed can go out of the screen?

@@jptrinhh I mean, for example, if I have a table that fills my entire screen with 16 rows, the rows further down that have dropdowns, when I open them, my screen will increase in size and create a scroll. Additionally, the dropdowns will go off the screen if I remove the scroll.

Thanks for the feedback! I will improve that on the next ones :)

You know where to find me if you have any questions :)

Thank you! What would you like to see? How to reproduce the components? Or in-depth demos?

Thank you for your support! Let me know if there is anything you would like to see

Thank you for your comment, it keeps me motivated to share what I learn! Tables are often used, and hard to design/implement when there are a lot of data. I will add that to my list!

@@jptrinhh I've got everything working now, except... And this is so silly... The row border lines and header column bgs stop before the end of the table when you scroll the table to the right. Tried for hours with Claude and ChatGPT and couldn't figure it out lol.

@@SmashTheCache Huum hard to tell. You can ping me on X or the WeWeb forum with screenshots if you want!

I'm glad you found that helpful!

Thanks bro! 🔥

Thank you Milan!! It was to add the line-clamp property to the card description. So when the description has over 3 lines, the rest would be hidden behind ellipses (you can see that at the end after binding the collection). I had to add that to in a style tag because of the wrappers WeWeb generates around elements.

Awesome job JP! What about when building a component and you lose the ability to scroll? That's my current struggle.

@@jptrinhh all right thanks JP !!

Thank you Anthony! Hard to tell without more element. I think you can seek help in the WeWeb Community forum with more details (you can tag me there too if you want 🙂)! @@anthonysmith1213

Thank you for your support!

Thank you! I used Screen Studio for recording.