Hi,
By icons do you mean local font material icons? If yes, I’m facing weird issues myself (shows up just text instead of icons). If not, check this: https://cordova.apache.org/docs/en/latest/config_ref/images.html
About splash screens, have you tried cordova api?
https://cordova.apache.org/docs/en/latest/reference/cordova-plugin-splashscreen/
I’m also interested int this config and have researched a lot about this. For the time being, apollo can’t ad hoc integrate with vuex (although has integration wit redux).
My solution so far is to implement
import ApolloClient from 'apollo-client'
const apolloClient = new ApolloClient({
...
})
Then in vuex
const store = new Vuex.Store({
...
mutations: {
apolloClient.query({
...
})
}
})
Working well, but several things is manually integrated.
I didn’t ever used break points. Don’t know how…
Yes. My bad. Have been debuging for a while but it was just now that I’ve found the misuse:
in my component <style> I’ve imported app.variables AFTER app.mat.styl (to use some of the variables, of course).
So this was where I banged my head over and over: in ‘quasar dev’ there where no issues, but when ‘quasar build’ and then ‘quasar serv’ (or apk with cordova), this was a deal breaker.
Anyways, sorry for the dumb topic 
In previous version, my themed builds seemed to work properly, but with the new version of quasar, after clicking in a link, it goes back to default theme (blue).
I’ve searched in the docs, but with no luck so far.
The only thing different from default scripts are my app.variables.styl:
$white_smoke = #F9F8F8
$dawn_pink = #E6D7CB
$fantasy = #EEE4DC
$stark_white = #D6C4B4
$gun_powder = #4D4D5B
$prim = #D6D2D3
$simple_red = #F54B5D
$primary = $gun_powder
$secondary = $simple_red
$tertiary = $prim
$neutral = #E0E1E2
$positive = #21BA45
$negative = #DB2828
$info = #31CCEC
$warning = #F2C037
$light = #f4f4f4
$dark = #333
$faded = #777
$text-color = lighten(black, 17%)
$background-color = $white_smoke
$link-color = lighten($primary, 25%)
$link-color-active = $primary
So, first page seems ok. Clicking to route new page, them falls back to blue.
What am I doing wrong?
I’m also interested int this config and have researched a lot about this. For the time being, apollo can’t ad hoc integrate with vuex (although has integration wit redux).
My solution so far is to implement
import ApolloClient from 'apollo-client'
const apolloClient = new ApolloClient({
...
})
Then in vuex
const store = new Vuex.Store({
...
mutations: {
apolloClient.query({
...
})
}
})
Working well, but several things is manually integrated.
Have you tried some of the css classes http://quasar-framework.org/api/css-positioning.html?
I couldn’t rest until find this nasty bug… And I’ve found it!
node_modules/quasar-framework/src/vue-directives/touch-hold.js:58
Utils.store.remove('touchhold')
Utils.store.remove('touchhold', el)
Still want me to open an issue? [edit: maybe a PR?]
Question: how can I build this fix in my node_module?
I’ve made a pull request for documentation about touch directives (they are now v-touch-swipe, v-touch-pan and v-touch-hold).
So I came acrosss with an issue on v-touch-hold when this directive calls unbind:
Trace
My code:
<div class="card" v-touch-hold="() => { moreOptions(schedule) }">
{{ schedule.info }}
</div>
...
methods: {
moreOptions: function (schedule){
ActionSheet.create({
title: 'More Options',
gallery: false,
actions: [
{
label: 'Delete',
icon: 'delete', // specify ONLY IF using icon
handler: function () {
console.log('Deleted Article')
}
}
],
// optional:
dismiss: {
label: 'Cancel',
icon: 'cancel',
classes: 'text-primary',
handler: function () {
console.log('Cancelled...')
}
}
})
}
}
Am I doing something wrong?