Could someone explain how quasar-layouts should be used?
- Where should they be stored?
- How to apply a layout to component?
- If I have my SPA and I want to apply one common layout for the whole app, where should I place it?
- Can I use
if you can - support Quasar on Patreon,
if you can’t (and also if you support on Patreon) - SHARE on social media - Twitter, Facebook, groups, forums etc.
Razvan is making great job and if he could more support from Quasar users and hopefully some big guys, Quasar can become even better!
Quasar needs your support!
I would strongly recommend to post on Patreon page.
At least every release note!
It will make people able to see how much work you do!
I found some allignment issue, but on Gitter got information that there are more.
This is the list -
q-btn inside the
q-item side right
It looks really bad. I could try to fix it with some additional classes but I think it should be ok out of the box.
Another one is with toolbar and buttons on the right:
It is ok on desktop, but there is issue when using e.g. S5 in Chrome devtools.
I need to limit the width of main container (so everything, including top nav, footer etc).
As I know, Q-layout has a lot of tweaks to work nice across all range of devices/resolutions and I do not want to screw it up.
This is the app which inspires me -
On resolutions over 1280 it limits the width of main container to 1170 and the app looks really nice even on large screens which is my current issue at the moment.
I am building app where the target user has to get as simple as possible app so on single page I have not too much content/interactions which make it looking bad on large screens even if it looks quite nice on phone/tablet resolution.
@rstoenescu - how can I make it with Quasar ? I know I can easily assign container width but want to be sure it won’t screw up all work which you have done.
@Martin First of all, thank you for such a great effort!
If you need a different layout setup for a particular page, create a new <quasar-layout> for it and make your router.js
jump to that page instead of showing it inside a <router-view>
How? I haven’t seen that in vue-router docs anywhere.
EDIT: 1&2&3 - ok, got idea about layout component (I don’t know why I thought about it as something special, not component…) and subroutes. That’s clear. Sorry.
4 & 5 - still need answer as the only idea which I have is exactly sub-routes. Anything else how to share layouts between components ?
@wannymiarelli Could your company consider supporting Quasar on Patreon?
@rstoenescu link to Editor is incorrect. Should be: http://quasar-framework.org/components/editor---wysiwyg.html
I would appreciate any help with reducing Docker image with my quasar app.
At the moment my dockerfile-dev looks like that:
FROM node:10-alpine ENV NODE_ENV development RUN yarn global add @vue/cli && yarn global add quasar-cli WORKDIR /srv EXPOSE 8080 CMD quasar dev
It is working nice, because together with the volumes set up in docker-compose I have nice hot reloading etc, but I am getting closer to first deployment and I can’t imagine sending/pulling 1.1gb image every time…
As the result I have 1.2 GB image which is pretty bad… I suppose I would have to go for 2 stage build but I am not that docker expert to do that…