OK so Quasar is really only for the front-end. I can still keep my old NodeJS APIs, right? It means I have 2 projects to manage: 1 for the front-end, 1 for the back-end?

Best posts made by djcaesar9114
-
RE: Quasar app architecture
Latest posts made by djcaesar9114
-
RE: quasar-logo.svg doesn't display on cordova after clean
Actually this external link was already set by Quasar, and at first it worked. What is strange is that I didn’t change anything in the config.xml:
<?xml version='1.0' encoding='utf-8'?> <widget id="fr.nc.delegue.referendum" version="0.0.1" xmlns="http://www.w3.org/ns/widgets" xmlns:cdv="http://cordova.apache.org/ns/1.0"> <name>XXX</name> <description>XXX</description> <author email="dev@cordova.apache.org" href="http://cordova.io"> Apache Cordova Team </author> <content src="index.html" /> <plugin name="cordova-plugin-whitelist" spec="1" /> <access origin="*" /> <allow-intent href="http://*/*" /> <allow-intent href="https://*/*" /> <allow-intent href="tel:*" /> <allow-intent href="sms:*" /> <allow-intent href="mailto:*" /> <allow-intent href="geo:*" /> <platform name="android"> <allow-intent href="market:*" /> </platform> <platform name="ios"> <allow-intent href="itms:*" /> <allow-intent href="itms-apps:*" /> </platform> <allow-navigation href="about:*" /> </widget>
-
quasar-logo.svg doesn't display on cordova after clean
Hello,
I rancordova clean
in the src-cordova folder and now when I run the cordova build, the logo won’t display although there is no problem with the SPA:
quasar dev
shows me the logo.
What have I done wrong? Why can’t my app fetch https://cdn.quasar.dev/logo/svg/quasar-logo.svg anymore?Thanks
-
Display permissions on apk installation (cordova)
Hello,
I use the plugin https://github.com/NeoLSN/cordova-plugin-android-permissions to manage the permissions. Everything works fine (I can check and set the permissions within the app).
But When I install the APK, it tells me the app doesn’t need any permission. How can I change that? I think I have to put something in a certain manifest, but how?
Thanks in advance
César -
RE: Use cordova SMS plugin correctly
I managed to buldi my apk after editing my .eslintrc.js file:
'no-undef': 'off'
But I think it’s not the correct way to do it.
-
Use cordova SMS plugin correctly
Hello everyone,
I’m trying to use this plugin: https://github.com/floatinghotpot/cordova-plugin-sms#readme
I added the plugin usingcordova plugin add cordova-plugin-sms
And updated my Formulaire.vue like this:
<template> <q-page padding> <p> FORMULAIRE </p> <q-btn color="primary" icon="question_answer" label="Vérifier en central" @click="sendSMS ()" /> </q-page> </template> <script> export default { name: 'Formulaire', data () { return { SMStext: 'TEST SMS' } }, methods: { initApp () { if (!SMS) { alert('SMS plugin not ready') } }, sendSMS () { var sendto = '+123456' var textmsg = 'TEST' if (sendto.indexOf(';') >= 0) { sendto = sendto.split(';') for (var i in sendto) { sendto[i] = sendto[i].trim() } } if (SMS) { SMS.sendSMS (sendto, textmsg, function () { }, function (str) { alert (str) }) } } }, created () { if ((/(ipad|iphone|ipod|android)/i.test (navigator.userAgent))) { window.addEventListener ('deviceready', this.initApp, false) } else { // updateStatus ('need run on mobile device for full functionalities.') } } } </script>
But when I run
quasar dev -m cordova -T android
I have this error:
/home/cesar/projets/quasar/client_sms_referendum/src/pages/Formulaire.vue 24:12 error 'SMS' is not defined no-undef 37:11 error 'SMS' is not defined no-undef 38:9 error 'SMS' is not defined no-undef
I know I didn’t defined ‘SMS’ but I checked the example given on github and I really don’t see how I can solve it…
Thanks for your help -
RE: NUXT with Quasar
@alancix then I think you should contribute to the current development
Use VueJS SSR in another project, that’s what I do, and hope I won’t have to change all my code when Quasar will be SSR ready.
-
RE: Quasar app architecture
@chbarr Thanks a lot, this kind of organization is new for me, I used to handle everything as a whole project, but it could be great for collaborative programming
-
RE: Quasar app architecture
OK so Quasar is really only for the front-end. I can still keep my old NodeJS APIs, right? It means I have 2 projects to manage: 1 for the front-end, 1 for the back-end?
-
Quasar app architecture
Hello,
I’m new in Quasar and the first thing that is weird for me (coming from a full NodeJS world) is that the “dist” folder only contain files to be uploaded directly on the server.
How can I organize my projects with APIs? I used to have some urls like this “/api/user/add” “/api/user/show” “/api/topics/add”, etc.Thanks in advance for helping a beginner