isosphere
Answer Question: Why `yew-bootstrap` Instead of Manually Using Bootstrap?
This is a question I have regarding the project; I think the answer is easier callback handling, but I'm not certain because I haven't tried the alternative.
I think others will have the same question, and we should be able to tell them in our README.md why this project will make their work easier if they intend to use bootstrap.
Why shouldn't a user manually call bootstrap raw in html! { } macros? Would it be a huge pain in the butt for them to do this and also have a "reactive" web application? If we are saving them some pain, we should make that clear.
To add to this: having a typed API to the components prevents some gnarly goofs where a typo'd classname or attribute breaks UI.
What I am looking for with such library:
- Strong typing, which helps removing basic errors
- Integrated documentation for these types, most of the times bootstrap documentation is not needed
- Support for components that require quite a lot of text, typicall forms, so focusing on what we want to display.
