@terrybradshaw: Did you opened a PR or Feature Request for this issue? It would be awesome to get custom fonts into Quasar. We are at version 1.2.6 now. 🙂

@RishitKedia Can you go into any more details about how to go about getting started making a chrome extension that uses quasar?

Or do you think you could possibly make a starter kit by removing all of the functionality from tabtation and just give us the basic setup for quasar?

I’d really like to use quasar in my chrome extension but I am having a really hard time getting started.

Would you say this is still relevant? When I try to follow these instructions, I get
2019-08-02T00:10:02.836781+00:00 heroku[router]: at=error code=H10 desc=“App crashed” method=GET path="/" host=xxxx.herokuapp.com request_id=95f93426-3129-48a7-800f-98c0789ae696 fwd=“173.59.63.17” dyno= connect= service= status=503 bytes= protocol=http
2019-08-02T00:10:03.644658+00:00 heroku[router]: at=error code=H10 desc=“App crashed” method=GET path="/favicon.ico" host=xxxxherokuapp.com request_id=15855a04-5493-4aba-beaf-34cf70b79eaa fwd=“173.59.63.17” dyno= connect= service= status=503 bytes= protocol=http

@laqul thank you for sharing. I am creating the list of all starter kits and your kit is now included. Feel free to add via comments all undiscovered kits.
After the consolidation is done I plan to curate the list.

Oh thanks, that is a handy shortcut to the attributes.

@metalsadman I thought it must be something like that … thanks for the clarification

I’m getting the same error I followed the how-to from the readme but not working

sure that I am missing something simple as I’m new to this

if anyone has any tips on how to get this running that would be awesome

Thanks

@UnderDog - I’m using a generic node alpine container and installing yarn would just lengthen the process, unfortunately.

You can create your own base container (there might even be one already done with yarn) as you’d like it and just update the Dockerfile container import (FROM) accordingly.

Scott

Nice demo.
I’m new to developer’s world and have no clue about some things, just for record :smiling_face_with_open_mouth_cold_sweat:
I think the next steps are:

Introduce offline support - i unppluged my internet cable and the database disappear Allow that the database be blanked and emmits some feedback - maybe a text or watermark inside the database visual area

@Oggo This was really my first app in Electron because I wanted to know how to do it. I have not done any type of unit testing for Electron, although I would be interested in learning the best approaches. I do know that there will be an integrated testing environment in Quasar v1.0. I am hoping it works well with Electron/Cordova as well.

Would be cool have this one ‘setup’ as well:
https://github.com/antvis/f2
see also:
https://medium.com/@SimaZwx/https-medium-com-simazwx-introducing-f2-c44fb4e74c2d

@ju11 Nice article! Tweeted about it.

thanks for your advice.

@rstoenescu said in Using Quasar components over the Laravel framework:

https://github.com/neatpro/Laravel-Quasar

Hello

It’s still on Quasar 0.14 far as I see.

That one looks like to be based on 0.15, that include major changes:
https://github.com/impxd/laravel-quasar-pwa-template

What’s your thoughts?