Hey since yesterday Bootstrap has finally released 4.2 and added awesome new features I also wanted to let you know, that I am currently working on a Blaze package that contains all Bootstrap 4 components out of the box. This was inspired by the already very famous react-bootstrap project, that achieves the same for React.
In fact, this is some sort of “half” announcement but rather a first DEMO (with a limited set of already implemented components) and I would like to hear from you
what you think about this
if you have any suggestions for improvement
if you like to join me to make this a full featured package
Thank you. It is not covering the full component set yet but it will progress with time, since I integrate the components into my own projects as well.
Feel free to open issues or ask a question here if anything is unclear, causing errors or is missing.
I have an app built using blaze and used Ionic , I like blaze due to MVC . Our app is very simple , for the user but has heavy backend logic. It is still on meteor 1.2 and I am looking to upgrade to latest meteor and also see if we can revise to use the right frameworks . Back when we developed meteor Ionic css met our requirements . Wonder what are the ui frameworks that i can use present day for mobile apps when using meter and blaze . How is bootstrap 4 for a mobile app ? have about 10 pages inside the app with header and footer
Much easier to reason about than using complex html constructs, isn’t it? But how does the item know, if it should have the classname dropdown-item or list-group-item? I approached this with two options:
A - Explicitly declare the type using a parameter
This is the faster way (no parent tree traversal required) but also requires an additional type parameter:
Leaving out the type parameter leads to a traversal of the parentView and originalParentView properties of the Template’s view until a Template is found (which is then considered as outer parent).
inside a {{#dropdown}} will find the Template.dropdown parent and the internal mapping of item will thus internally assign dropdown-item as classname to the element.
Focus more on the important stuff
Having abstracted away the meaning of the item we have also more space to focus on custom html content:
It’s been a month since the last update and I finally added cards which are one of the core components. I also made some updates in those components, that can be combined with the card layout, such as navs and list groups.
The version is 0.12.0 and the DEMO has also been updated.
Edit: after I realized, that the card Demo is missing the code panels, you can also read the code in the repository here until the DEMO is updated.
It would be great to get some more feedback or support of some of the Blaze and Bootstrap people around here and I would love to see projects using this package in the near future
Do you have an ETA or more detailed plan for the rest of the work?
There is no specific day as ETA but I intend to publish 1.0 around the summer. The roadmap is currently the list of issues on GitHub, which mainly represent the components that are still to be done (see my last prior post for the list).
I use the components in a MVP already and they will be deep part of the project that builds on top of the MVP. Consider active development ongoing until 10/2020 as safe.
Edit: I jsut released 0.13.0 which now has tooltips implemented.
@jamgold please check the documentation on the github pages, because I have slightly extended the toast, so you can debug globally as well as each created toast individually plus there are now event callbacks that you can pass to the add method.
Very nice about the events, because I just noticed the Template.events only works on the parent, so if you wanted to attach shown.bs.toast or hidden.bs.toast that would be the only place you could put it. You event method arguments solve this.