@turigeza cannot agree more!

@dsl101

I agree, you could create feature request in github:
https://github.com/quasarframework/quasar/issues

or open a new discussion about it on the new forum( this forum is dead):
https://github.com/quasarframework/quasar/discussions

@damiendeville

a) The commands to create the project do not mention neither meteor nor quasar

Every thing under api is managed by meteor. So for example to start the meteor backend you use Meteor CLI to start it. Also to update meteor you use meteor cli. And of course Quasar Cli is used to manage and start client.

The code in quasar-meteor/api/client/main.js/ contains Blaze code; why should it be needed it if the client is made of Quasar/Vue components?

I have not seen that, because I run meteor headless. But you could create a gui in the api backend part of meteor, for admin things. Its’ optional/just a bonus.

@damiendeville

100% correct.

@tlloyduk

I would ask this on the new forum where the Quasar team now gives support.

https://github.com/quasarframework/quasar/discussions

@kuba

I would ask this on the new forum where the Quasar team now gives support.

https://github.com/quasarframework/quasar/discussions

@cwoodman

Better post it on the new forum.

@cosby said in How to use QDialog from javascript file:

Dialog

here:
https://quasar.dev/quasar-plugins/dialog#usage

@saifobeidat

Is this even a valid approach and doable using the platform detectors, or it’s preferred to go with a separate project to serve the mobile app?

Yes it’s very doable with platform/mode detectors in a single project.

Here’s a repo/project/product(enFocus) that has a different ui/flow based on if you are on mobile or electron.
It is using different techniques to archive this( for example using functional components and different routes depending on what mode quasar is running).

https://github.com/vycoder/qodo

I would post this for better support on the new Quasar github discussions forums:
https://github.com/quasarframework/quasar/discussions

@kuba

Probably legacy / custom css that’s bothering you in Quasar UMD mode. Btw UMD mode is the only way to go with jsp.

Try to create a new demo project with just a clean jsp( outside of your project) just like you did with html.

@partofthething

No don’t think so.

@krish7280

for vue3 you need the beta version of Quasar. See the docs.

@socrates3142 said in Electron Splash Screen?:

splash screen

You could look at this:
https://stackoverflow.com/questions/39126429/electron-splashscreen-on-startup-application
https://github.com/trodi/electron-splashscreen
https://github.com/bkniffler/electron-splashscreen

@rainer9202

Did you upgrade any deps , local or global related to quasar?

@manolo

Please create a codepen.io for better support:

https://codepen.io/rstoenescu/pen/VgQbdx

Even better create a post with codepen.uo on the new Quasar forum, github discussions:

https://github.com/quasarframework/quasar/discussions

@kaizoku2508

Use the v-model to show the dialog like this:

 <q-dialog v-model="showDialog"
...
showDialog = true  // set to true will show dialog

@phgrund

Could you post this in the new support forum : quasar github discussions?

https://github.com/quasarframework/quasar/discussions

Considering you’ll be one of the first support posts on the new forum, I bet you’ll get first class support!

@kaizoku2508

My partner create a login page

btw I don’t see any page( containing a q-page) in your original ‘page’ code

Login component in components/Login.vue:

<template>
  <div class="q-pa-md" style="width: 400px">

    <q-form
      @submit="onSubmit"
      @reset="onReset"
      class="q-gutter-md"
    >
    <q-input
        filled
        v-model="email"
        label="Your email *"
        lazy-rules
        :rules="[val => !!val || 'Email is missing', isValidEmail]"
      />

      <q-input
        filled
        type="password"
        v-model="password"
        label="Password *"
        hint="Password should be 8 characters"
        lazy-rules
        :rules="[
          val => val !== null && val !== '' || 'Please enter your password',
          val => val.length === 8 || 'Please enter a valid password'
        ]"
      />

      <q-input
        filled
        type="number"
        v-model="phone"
        label="Your phone number *"
        lazy-rules
        :rules="[
          val => val !== null && val !== '' || 'Please enter your phone number',
          val => val.length > 8 && val.length < 12 || 'Please enter a valid number'
        ]"
      />

      <div>
        <q-btn label="Login" type="submit" color="primary"/>
        <q-btn flat to="/user/requestpassword" label="Forgot Password?" type="submit"/>
      </div> -->
    </q-form>

  </div>
</template>

<script>
export default {
  data () {
    return {
      email: null,
      password: null,
      phone: null,
      accept: false
    }
  },

  methods: {
    isValidEmail (val) {
      const emailPattern = /^(?=[a-zA-Z0-9@._%+-]{6,254}$)[a-zA-Z0-9._%+-]{1,64}@(?:[a-zA-Z0-9-]{1,63}\.){1,8}[a-zA-Z]{2,63}$/
      return emailPattern.test(val) || 'Invalid email'
    },
    onSubmit () {
      if (this.accept !== true) {
        this.$q.notify({
          color: 'red-5',
          textColor: 'white',
          icon: 'warning'
        })
      } else {
        this.$q.notify({
          color: 'green-4',
          textColor: 'white',
          icon: 'cloud_done',
          message: 'Submitted'
        })
      }
      this.onReset()
    },

    onReset () {
      this.email = null
      this.password = null
      this.phone = null
      this.accept = false
    }
  }
}
</script>

Login page containing a QPage and your custom Login component:

<template>
  <q-page>
      <Login/>
  </q-page>
</template>

<script>

import Login from "src/components/Login"

 export default {
   components:{Login},
   data () {}
 }
</script>