No More Posting New Topics!

Great help, both from the original topic and @cheebhodh reply. Up and running with GraphQL and Apollo now, thanks!

@leopiccionia thank you so much.

you’re right for Pug, I forgot it was automatic Great! Right now I’m customizing the build.extendWebpack function of quasar.conf.js to add loaders to my Vue single component files. I guess the documentation will talk about that.

I’m feeling better now…

Why not have both

The beauty of quasar is deploying to multiple platforms form a single codebase.

Regarding PWA caching: all this does is keep in memory the static assets that make up an SPA, so you can access those offline. In other words, a PWA does not help with user initiated server interactions. So if you want your app to work offline and still register user actions somehow, you need to figure it out on your own.

Thanks man,
i solved with

quasar build -m cordova -T android

really appreciated your help.

Once the beta is installed, Is switching back to the released version just doing a reinstall of the release cli ?

Those classes are purely presentation and can be safely removed.

hi @april just got read your article and its cool! 🙂 like you

Main problem with dynamic changing the theme at runtime is webpack related. Can’t manage CSS since webpack is doing it. Once you import some CSS it is there to stay. Before switching to webpack + vue-router, Quasar had its own build system and dynamic theme switching was possible. It actually detected if you’re on an Android or iOS device and delivered the according theme. Looking forward to a solution with webpack if anyone has time for this. I’m currently working on v0.15 goodies and I’m 200% overloaded. Any help on theme switching is greatly appreciated.

Thanks for also providing a solution. I will add verification into the template to ensure the minimum nodejs and npm versions are installed.

Hi, I see a github ticket opened. Let’s continue the discussion there. https://github.com/quasarframework/quasar-template-default/issues/46 Thanks!

@A3an tell me what OS (and version) u have, if you use a custom terminal etc etc.

First, why do you need a second service worker? This is not how PWAs work.
Second, you have the service workers in /build folder.

@spectrolite Both “like this” and “this” link to same animation docs. First one should refer to some docs on icons. Can you give that link please? Thanks!

Do you have some timeframe for the upgrade to v.14?

@luc-claustres your repos are awesome! The only thing I miss to have the full story is the use of vuex and feathers-vuex 🙂

Maybe step 4 is redundant with step 2, I’m not entirely sure. (I mean this could be optional: npm i --save git+https://git@github.com/quasarframework/quasar-edge.git)
But it’ll help people upgrading from a 0.13.x
Those people will want to skip step 2, and should probably read: http://forum.quasar-framework.org/topic/522/upgrade-guide-for-0-14-beta

Hi,

Quasar is a front-end framework. What you are looking for or rather where you should be looking is within the API or backend, which Quasar currently doesn’t have. There are two API wrappers in the works. One for a REST API based on FeathersJS and another for a GraphQL API based on Apollo. They should get you a lot closer to what you are looking for.

Scott