I’m trying to implement the QTable, but want to edit how the rows / column headers look.

I believe there are two ways which … do the same thing?

• Grid mode:
  https://quasar-framework.org/components/datatable.html#Grid-Mode
• Custom rows:
  https://quasar-framework.org/components/datatable.html#Custom-rows

What is the difference between these two?

So I’m kind of stuck on something:
My entire app is built with a very distinct design and the base of my CSS has always been the iOS theme.

However, for two components I require to use the Material version of the Quasar Material theme, while keeping my iOS theme in tact.

Can anyone point me in the correct direction how I best start writing such a hack, where I’m allowed to choose Material theme for just 1 or 2 components?

The components I need of Material are QTabs and Datetime Picker.

@ssuess Exactly… iOS really f*cked up the PWA support this time…

I believe they want to make the worst compatibility as possible to make devs not use PWA’s and make more native apps. Because Apple won’t make money from PWA’s and they have more chances they will from native apps.

Welcome to the world where money is more important than the consumers.

@ssuess Thanks for your post.
I meant this comment in this post:

What to have in mind
Your PWA won’t keep state between sessions, if the user gets out of a PWA, it will be restarted when coming back, so if you need the user to validate an email, SMS or do a two-factor authentication, have that in mind to offer a proper solution.

It was the same for me, where every time I open the PWA it will flash and take me back to the homepage. Maybe they fixed this already?

Combined with this, not getting the prompt to install the latest service worker and having users using older versions of my apps without me being able to do anything about it just added to the list of problems… That’s why I left PWA’s.

@ssuess Anyway, if you look in service-worker-prod.js in the PWA source folder you will find this line:

case 'installed':

That’s where you need to write your logic. I had:

case 'installed':
  // At this point, the old content will have been purged and the
  // fresh content will have been added to the cache.
  // It's the perfect time to display a "New content is
  // available; please refresh." message in the page's interface.
  if (!window.QNotify) {
    window.location.reload()
    break;
  }
  window.QNotify({
    message: window.store.getters.text.global.newVersionAvailable,
    timeout: 10000,
    type: 'info',
    actions: [{
      label: window.store.getters.text.global.refresh,
      handler: function () { window.location.reload() }
    }]
  })
  break;

@ssuess I made a function that refreshed it a long time ago.
But since iOS 11.12 update just completely screwed up PWA support and keeps refreshing the app every time you open, I just stopped PWA all together now.

Also, I’ve had many problems always with users not on the latest version. Sometimes safari webkit doesn’t recognise and trigger the popup to refresh to get the latest version of the app and I was never able to find out why.

@dkr88 Hi, I need to write a new dashboard for a project, but they requested my to use TS, but I still want to use Quasar!

I have never written typescript, so I’m just doing some initial research on it, but I think just to do the initial setup I’ll follow your guide in the 5th post in this thread.

My question: Is it only compatible with 0.15? or also 0.16?

My reasoning is: if I just setup the base to be TS compatible I can start from the real simple things, and learn TS on the way while typing it.

Like Andy Kaufman would say:
https://youtu.be/2ymMyY4GNAE

@panstromek
It’s usually these plugin files that become so long in my case, I extract parts into other JS files, import them on the top of the plugin file.

One solution is to change ALL these imports to functions, and pass the store as param. But not really beautiful imo…

Do you have any other advice for me?

@rstoenescu I’d love to try out my other apps in the beta build, but wondering about the store:

With the new method of instantiating the vuex Store, it exports a function instead of the actual store. I used to import the store into several places of my app (js helper files etc.) and use it, however, how would I do this with the SSR version?