Here’s my first Quasar work in progress prototype : http://sonicviz.com/project/fopra-focused-practice/
Any feedback or bug reports welcome!
Thanks for the cool tools Quasar!
Here’s my first Quasar work in progress prototype : http://sonicviz.com/project/fopra-focused-practice/
Any feedback or bug reports welcome!
Thanks for the cool tools Quasar!
Resolved. Seemed to be an issue purely with gitlab pages as when I deployed to netlify the offline add to homepage works just fine.
Any clues on how to do this?
It might seem obvious but none of the regular position/align things seem to work.
I have a row
I have a column
<q-list bordered separator>
<q-item class="row q-col-gutter-sm justify-center align-center"
v-for="x in y" :key='x'>
<div class="col-1"
v-for="a in b" :key='a'
> <div class="align-center">{{ x[a] }}</div>
</div>
</q-item>
</q-list>
Am I missing something?
@qyloxe said in conversion from bootstrap themes/templates:
@lucasfernog sure, but please read the thread carefully - we’re not talking about components but about thousands of free bootstrap themes, used as a base for frontend sites in business, blogs, landing pages and many other categories of sites.
It is possible to get those momentum in frontend technology because Quasar has a set of compatible with B4 CSS classes which means, that if there would be a clear or relatively easy path of conversion from B4 to Quasar, there is a big chance of putting Quasar mainstream and let the world use it instead of B4. Why? Because B4 has poor components but it’s very easy to start with good looking theme or template but when it comes to really making a site it is very hard. So, as you can see, CSS classes for layout, typography and colors are not a “developer” problem but rather a “marketing” problem.
I’ve just come across this issue converting a project that uses Bootstrap css, which I’m converting into Quasar.
It would have been helpful to have a guide. The point that @qyloxe makes above is very smart business sense as well.
Resolved. Seemed to be an issue purely with gitlab pages as when I deployed to netlify the offline add to homepage works just fine.
Fopra - Focused Music Practice Timer https://fopra.live/
Project page: http://sonicviz.com/project/fopra-focused-practice/
Here’s my first Quasar work in progress prototype : http://sonicviz.com/project/fopra-focused-practice/
Any feedback or bug reports welcome!
Thanks for the cool tools Quasar!
You need to read and understand the lint errors, not ignore them.
It’s quite restrictive and in most cases they are exactly what they say they are.
Updated the manifest file with full start url but it’s still getting the url wrong for static icons
{
"name": "Fopra App",
"short_name": "Fopra-PWA",
"icons": [
{
"src": "/statics/icons/icon-192x192.png",
"sizes": "192x192",
"type": "image/png"
},
{
"src": "/statics/icons/icon-512x512.png",
"sizes": "512x512",
"type": "image/png"
}
],
"start_url": "https://sonicviz.gitlab.io/fopra",
"display": "standalone",
"background_color": "#ffffff",
"theme_color": "#027be3"
}