What an amazing update! Brilliant stuff.

@aryeh Thanks a lot
I’m going to try find a way to improve the speed, but as you mentioned, initial load is the biggest factor because it needs to load a lot of content into the cache. The files are stored on Amazon S3 in Sydney, Australia. I may have to store the files in multiple locations to improve that speed.

@shone Thank you for the feedback! Much appreciated and I’ll take it into consideration in the next iteration of changes I make.

There is no live demo of 1SPAN CMS at this point as the project is on-hold, but I’ll probably put up a live demo soon

@joepstender Weird… I haven’t had any issues. May I ask what country you’re from? The site is hosted on AWS in Sydney, Australia.

Hello Quasar Community!

I’d like to take an opportunity to show off my new portfolio website which I’ve built using Quasar 0.16 and WordPress!

https://nickzuccarelli.com.au/

Feel free to take a look and let me know what you think!

@paul said in Platform detection and google chrome emulator:

My Bad, need a hard Refresh. Probably platform is detected on app startup.

You’re right
You must reload the page for chrome dev tools to render the app using a specific platform.

Hiya,

I’m wondering if we could possibly get support for QTab/QRouteTab dropdown menus in the future (working similar to the btn-dropdown except in tab-form).

@max I ended up figuring it out! There were only a few small changes I had to make to the quasar.conf file, otherwise it works perfectly!

Hey guys,
I’m wondering if I can get any help setting up Quasar with WordPress.
I am using the cli for installation.
I’ve successfully set up the framework inside of its own WordPress theme, but the only problem I’m having is that assets (such as images and fonts) cannot be found.
This is because they are trying to locate /img/, /fonts/ , whereas the actual files are located in /wp-content/themes/themename/fonts/.

Is there any way I can modify the configuration quasar file to point the build to this location?

@mds1 Yikes! That’s certainly a nasty solution haha. I’ve decided to hold back from upgrading to 0.15 until these features and/or proper workarounds are documented (plus other bug fixes )