Sorry for the late response. Quasar is a great project and I certainly don’t mean to violate the wishes of the core project team. But, as far as I can tell, there is no supported way to use a font created with Fontello, and the project I’m working on needed some icons that weren’t part of the supported sets. I did suggest a fix for future development (defining custom font prefixes in quasar.conf.js), but given that we are presently right between 0.17 and 1.0 beta I am not comfortable creating a PR because I don’t want to break backwards compatibility, nor do I want to introduce new features during a beta/RC phase. Or when the app-extension docs are available, I can look into that.

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

Any progress? I would love to use/contribute to this type of component. One of the options is to form the vue-form-generator and migrate the input types to quasar components.

@a47ae said in [How To] Building components with Quasar: Most of Quasars components are also distributed as single file components, you can check out their source here. Link is broken … no major just thought I mention.

@israel965 I ran into the same problem. I finally got the fonts working in “build” distros by providing relative paths from quasar/.quasar So instead of src url(/fonts/OpenSans.ttf) try src url(../src/css/themes/fonts/OpenSans.ttf) obviously, customize the path to your font files, but keep them relative, not absolute I will note this is probably only a good idea for local apps such as electron or mobile apps. Webpack will rename font files, so that cached versions of the fonts cannot be used, which, for a web site, will slow down time to load the initial page significantly.

@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?

This is great stuff !! However now, after a couple of new versions of Quasar framework (v0.17 now) it seems to me that this will be quite different ? Is that so ? And if so - how would you include i18next with xhr backend in a 0.17 Quasar app (pwa in my case) ?? Regards

@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.

@nothingismagick good,that is the idea and everyone’s ideas are welcome.

To disable the text input field without disabling the whole component I ended up doing this to my component. in the html tag I put @keydown="ignore()" ref="chip" then in methods add an ignore method ignore () { this.$refs.chip.blur() }, still would be nice to have disable only disable the text field not the whole component.

Nice job. Maybe think about making a PR here: https://github.com/quasarframework/quasar-awesome