Stop using Components in Toddle!

🚀 Learn more about Toddle & LowCode/NoCode in my Daily Office Hours: nocodeprocode.com
Projects & Questions: [e-mail]
Thanks for watching 🙏💛
#nocode #nocodesaas #nocodedevelopment #nocodeai #nocodeintegration #nocodetools #nocodeplatform #nocodeapp #lowcode #lowcodedevelopment #lowcodenocode #lowcodeplatform

[@NoCodeProCode]

🚀 Learn more about Toddle & LowCode/NoCode in my Daily Office Hours: nocodeprocode.com

[@patricktuub2607]

Best video!! I was struggling with a Input component, and now its clear to me, so, perfect timing! Thanks!! 🤩

[@NoCodeProCode]

@@patricktuub2607 Haha - that’s great timing ⏱️😃

[@marianamoment4423]

Thanks.

[@NoCodeProCode]

@@marianamoment4423 🙏💛

[@devwithflow]

please make video on how to work with toddle asyncronously Like: using interval and timeout in js. and how to clear them on any event or condition

[@NoCodeProCode]

@@devwithflow Absolutely 👍

[@luquimbo]

If I understood well, you don't recommend using the new Spark Core package for Toddle right?

[@NoCodeProCode]

@@luquimbo I don’t suggest any frameworks in general, as you are learning to use a specialized framework rather than the basics of HTML, CSS and JS. Spark and Shoelace add abstraction to HTML elements, which saves time and makes things easier, but you are also not learning HTML using them, which keeps you in the Toddle ecosystem, which is never good - with any tool. (Even though Toddle is great we wanna learn the bigger picture to be flexible in what tool we use)
I use Toddle as a faster way to write HTML, CSS & JS on the frontend, not as a tool to add more abstraction to what I do.
But since I focus on the core basics of HTML, and so do we do at NCPC, we could move to WeWeb all tomorrow or React (better Next JS) and with a little bit of adjusting our muscle memory we’ll be able to make something work on those frameworks/tools as well.
So the price you are paying when using packages and mainly abstracted libraries is your experience and expertise.