Posts made by Hawkeye64

Quasar is for front-end. Database packages would be for a back-end. You need to build out a back-end to consume MySQL and communicate to/from front-end to back-end.

QScrollArea is still there. Got missed in docs, but will be there for next website update. It hasn’t changed, so you can use the 0.17 docs for it in the mean time.
Quasar drawer is calculating the height in the CSS just as you are (I believe).

Maybe use QScrollArea…

https://v1.quasar-framework.org/vue-components/dialog#Example–Inception

FYI, with the release of Vue 2.6 (now up to 2.6.2) the code had to be reworked with breaking changes (their release should have been Vue 3.0.0-beta-1). It’s taken a couple of days to be Vue 2.6 compliant, and even then, if the Vue guys make more fixes, we may also have to as we’re downstream.

If a component does not accept a prop, then Vue will keep passing it down until it is accepted. You can see your props in this.$attrs. I recommend reading this article for enlightenment. https://zendev.com/2018/05/31/transparent-wrapper-components-in-vue.html

For instance, in this context, it is when you are using Quasar as a UMD. Or, where you are integrating Quasar into an existing product, etc.

I am going to try and take a stab at this…
In your src/router/routes.js file, as child data in children you would have the following:

      {
        path: 'topic/:topicId',
        component: () => import('pages/DisplayTopic') // <== name of page
      },

Then, on that page, you can access it like this:
this.$route.params.topicId

You can read up on it here: https://router.vuejs.org/guide/essentials/passing-props.html#boolean-mode

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

Glad it could be of use. Sounds like an interesting project.

Can you provide a jsfiddle so we can visualize this? https://jsfiddle.net/rstoenescu/waugrryy/

Figured it was something like that.

@Jon Why? Building something similar?

Added an issue (Enhancement) request: https://github.com/quasarframework/quasar-cli/issues/205

@rstoenescu
This is a discussion for the CLI to support 3rd-party NPM Quasar packages.

If someone were to create and publish a Quasar package to NPM, then the person installing it would have to possibly manually add to the quasar.conf.js file.

I think that it would be great if the CLI could do some of that work. The postInstall of an NPM package would be perfect for this.

quasar conf component QPopover QSlideTransition
This would add QPopover and QSlideTransition to the framework: { components: [ section, if they were not already there.

quasar conf directives CloseOverlay
This would add the CloseOverlay to the directives: [ section, if not already there.

You get the general idea.

Yep, all good. You can see my tutorial here: https://medium.com/quasar-framework/building-an-electron-file-explorer-with-quasar-and-vue-7bf94f1bbf6

I just published my tutorial “Building an Electron File Explorer with Quasar (and Vue)”. If interested, check it out: https://medium.com/quasar-framework/building-an-electron-file-explorer-with-quasar-and-vue-7bf94f1bbf6

what version?
Type quasar info and paste it here.
quasar new [s|store] <store_module_name> should work.

Looking good!

@stuartcusack You could also use this package instead: https://www.npmjs.com/package/idle-vue