Closed nosyke closed 1 year ago
I totally agree with you. What I am trying to do is copy the component that I want to use in my project and make the necessary adjustments (functionality, styles) in the core code.
I'm hoping that the Flowbite team will finish this project soon, because I purchased their template and I feel like I bought something that doesn't meet my needs.
Hey peeps,
I'm one of the maintainers of the core library - can you please give some specific feedback on what you'd like to see differently or improved with Flowbite Vue? It's still a work in progress so we are quite versatile with the API changes.
Cheers, Zoltan
Hi @zoltanszogyenyi Thank you for your interest.
These would be great if Flowbite-Vue had them:
This is my personal opinion based on my needs, and I do not consider it to be better. As I work on my project, I'll send you new ideas.
Thank you once more.
I'd like to add one more thing:
Drawers are all too common these days. Many user interfaces use modals that are positioned on the side (left or right).
Hi Zoltan,
Thanks for your openness to feedback. I appreciate the opportunity to share my experiences and issues. Here are a couple of key points that I've noticed:
Flowbite-Vue Library Visibility: Initially, I had difficulty figuring out why Vue wasn't integrating well with Flowbite, despite following the documentation closely. It took some time and considerable digging through various online posts to discover an alternative method of integration. Making the Flowbite-Vue library more prominently visible on the main site could eliminate this confusion and barrier for others.
Compatibility Issues: There have been quite a few challenges when it comes to merging Flowbite with Vue. For instance, certain component reactivity isn't rendering as expected. The instructions on your website for Vue integration don't seem to accurately detail the steps needed for effective use with Vue 3 and Flowbite. If there are known compatibility issues and 'hacky' solutions are required, it would be helpful to have this information upfront. Similarly, if a separate library tailored for Vue and Flowbite exists, this should be clearly communicated from the outset.
I hope this feedback proves useful. I'm eager to see the evolution of Flowbite and am more than willing to continue providing feedback as necessary.
Best, nosyke
Recently started using Flowbite-Vue and I have to say, it's been a bit of a bumpy ride. First off, it's like finding a hidden gem (not in a good way) - the main site doesn't even point to it unless you happen to scroll all the way to the bottom where Flowbite advises actually you should use this other library we've halfway built because the main library doesn't actually work with Vue like you'd expect.
Then, when I finally got to it, it turns out its still not even working right. Ran into a bunch of issues that just seem like it needs a lot of work before this is ready for use.
And don't get me started on the docs - what is even going on with those?
Not trying to rant, but was really looking forward to using Flowbite and it's been a letdown so far. If I had known there were this many problems with Flowbite and Vue I would not have used it to begin with.