@kmandrup - for my curiosity, what do you mean by “generator”?
Oops. I put the “icon” in the wrong place.
Should have been:
<q-fab class="absolute-bottom-right" @click="alert()" classNames="primary" active-icon="alarm" direction="up" style="right: 18px; bottom: 18px;" > <q-small-fab class="white" @click.native="$refs.drawerleft.open()" icon="some_other_icon"> some-button </q-small-fab> </q-fab>
A guess on my part, but you might need the icon property too?
<q-fab class="absolute-bottom-right" @click="alert()" classNames="primary" icon="some_other_icon" active-icon="alarm" direction="up" style="right: 18px; bottom: 18px;" > <q-small-fab class="white" @click.native="$refs.drawerleft.open()"> mail </q-small-fab> </q-fab>
Edit: Hmm…looking at the docs, “add” should be the default. I would say, if you add the icon attribute, and it works, there is probably a bug in that component.
@AhsanAbrar - Quasar uses Webpack 2. And the framework is pretty stable.
A guess on my part, but you can (should?) use Vue-router with (sub)tabs.
As an example, you can see from the play app, how the tabbed navigation (tabs selection) is using
<router-view>, which uses router.js to route to the different pages (which aren’t there yet). This is how you’d do subnavigation under tabs, I would suppose.
What I don’t understand is why the primary tabs don’t use vue-router. Or do they? Is the inline route definitions to make the navigation easier to understand? Can they also be made dynamic?
Well, the other forums are that way most likely because that is what nodebb defaults to.
Oh well. It’s your forum.
BTW, Onsen added a…um…secondary header/ navigation to the other resource locations in their forum. I am not too keen on how they did it, but it is another idea.
Ok. Well, with my experience of templating systems (ala Twig and home-made systems), I’d be for declaring components locally. I personally haven’t known it any other way.
Looks like your connection to Quasar Framework was lost, please wait while we try to reconnect.