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 thinking about creating one, but it will take some time.

@ssuess Sure! So, I was new to both Vue and Quasar when I started working on this extension. I was in the same boat just as you are, hence this post here on the Quasar Forum. Initially, I tried using the Quasar CLI as recommended but wasn’t able to make it work. I faced a few issues (which I don’t remember now, sorry). Haven’t tried again but those issues could have been due to me being inexperienced at that stage. I then looked into using the Vue CLI and found vue-cli-plugin-browser-extension. I used that along with vue-cli-plugin-quasar to build Tabtation. I tried other MD frameworks for Vue as well but either couldn’t make them work or the components were not all that great or keeping up with MD 2 like Quasar. A thing to note here is that I’ve used Quasar only to build the UI by using its components. All the other stuff is your usual Vue and Vuex code along with things specific to Tabtation and the Chrome/Web Extensions API. I hope that makes sense! Let me know if it doesn’t and something is unclear. Thanks for asking this!

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.

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