@dgk It alway wise to be careful when starting on an new adventure 🙂

The Quasar.start, as far as I understand it, is a way to make sure that some of the mobile platforms are properly initialized (when needed), no magic just a way to give Quasar a change to init som stuff early. If you just make sure this is in you startup function, there is really not much to it.

Quasar is just components, BUT the layout filosofi here is to use the same layout on different platforms, and therefor quasar is able to help you most if it controls things like startup and layout (q-layout).

Regarding webpack … it is true that the cli version makes a rather large Webpack2 setup, but this is NOT at all necessary, I have a single file version using webpack 1.x (and i also use typescript) and this works just fine. What you need as a minimum, is stylus, babel and a few defines (PROD, DEV and __THEME).

The quasar build utility is just a wrapper, nothing magic just trying to be nice 🙂

So I understand you concern I have just been over all this myself 🙂

@rstoenescu Excellent tip, way better to write

if(DEV) { window.wsPath = 'ws://localhost:4000/socket/websocket?vsn=1.0.0' } if(PROD) { window.wsPath = 'ws://acasito.com/socket/websocket?vsn=1.0.0' }

Thanks, putting audio files on statics/ dir works, thanks @rstoenescu for your support. You’ve made a wonderful framework.

Due to the way Vue Router works, the following markup is needed (notice the wrapper <div> right below <template>):

<template> <!-- root node required --> <div> <!-- your content --> <div class="layout-padding"> <!-- if you want automatic padding --> </div> </div> </template>

Check https://github.com/quasarframework/app-template-default/blob/master/template/templates/view.vue

Search for the right ESLint rules here: http://eslint.org/docs/rules/

Hi,

Question: does the top part changes?

Some assumption first: you only want the item list to be scrollable and the rest of the UI to always be visible on screen.
If “no” then add it as part of the layout header (div slot="header").
If “yes” then it requires some thinking. You still need to add it to the header, but you also need to either use Vuex or a simple store of your own to sync what the layout should show based on the page the user is on.

This is just the high level design based on Vue’s own capabilities. Tell me if you need further information.

Hi,

By default, if you create a page component per route you’ll be using System.import()(check src/router.js) which automatically creates a lazy loading chunk. This will make each page be loaded on demand, along its CSS.

Yesss, thank you.

CLOSED

Hi Martin,

Currently no. And the reason for q-transition to exist was to wrap the slide transition as it is now with some JS (can’t be done in CSS alone when you don’t know the exact height of the children). This component will eventually get removed and replaced by a collection of Vue CSS transitions.

Hi,

There’s currently no “official” way to deal with Progressive Web Apps. Yet. It’s going to be added soon through a starter kit or a wrapper, but not launching it until it reaches very high quality as Quasar devs are used to.

Until then, take a look at https://github.com/quasarframework/quasar/issues/77

Cheers,
Razvan

What are you trying to do?

As mentioned in the comments on SO, the person asking the question is basically using Vuex for the wrong purpose.

Scott

I use svg instead of font icon , that work well

It seems that the actual file does not need to be in the root of the site. That is a requirement for service workers, but not the manifest file.

So this works…

Index.html

<link rel="manifest" href="/statics/manifest.json" />

and put the manifest.json file in the “src/statics” folder.

This doesn’t solve the problem of serving a file from the “root” for a service worker, but that’s another question…

<div class="text-center"> <h1>HELLO</h1> </div>

?

Quasar v0.11 (trying to release at the end of this week) will get enhanced sorting capabilities including specifying your own sorting method. This will allow you in your problem here.

One more thing that you can do even with v0.10 is to compute/alter/map your data before you feed it to DataTable, so instead of using an object as cell value, use the object’s property directly in the computed data --> the result will be that you’ll feed DataTable directly with the value that you want to display. Example (let’s say you want for ‘col2’ to display ‘col2.secondprop’):

Original Data:

let orig = [ {col1: 'some data', col2: {oneprop: 'sdfs', secondprop: '...'}}, .... ] // Computed data: orig.map(row => { return { col1: row.col1, col2: row.col2.secondprop } }

@rstoenescu
Thank you, I’ll try

@boyd Make two builds. ‘quasar build mat’ and ‘quasar build ios’. Note that each build command replaces the existing ‘dist’ folder. After each Quasar build you can make a cordova build. Let me know if you need a more detailed explanation.

@mirko Use the more modern ‘<em>’ tag instead of old ‘<i>’