Quasar integrated with existing desktop js website?
-
Hey guys,
It may be a stupid question but I am new to this (coming from a PHP stack) so please bear with me.
For a new project I intend to play with nodejs and vue the to build the desktop website.
I wonder if/how Quasar can be integrated into this as to use it for building the mobile hybrid apps which are required.
Is there any integration workflow so I can understand if the desktop JS code can be somehow re used in Quasar? -
@rhobur - It isn’t quite clear. Are you starting a project or do you have the project already started with a good bit of code? If you are just starting, it would be best to use Quasar CLI to build your site. It will be mobile ready from the start. If you already have a code base, trying to “jimmy in” Quasar will be a challenge. I’m not going to say it isn’t doable, but if it is a PHP based website and not a SPA with a PHP built API, you’re probably not going to do well. You might get it done if you already have a SPA with a PHP API.
Scott
-
@s-molinari Sorry for not being clearer, I intend to start from scratch using Sails.js and Vuejs, I am fiddling with sails and coming from the LAMP stack, its MVC pattern is something I can understand quicker.
I had a look on the quasar docs but I didn’t get a clear notion of the framework having some quick development tools like sailsjs apparently has. -
Sails.js is an allrounder MVC framework made for Nodejs. It’s sort of like Laravel, but for Node. It comes with its own templating engine, which means, it isn’t really built to support Quasar. Or rather, if you want to create a SPA or SSR site, you can use Quasar alone, but it will only fulfill, for the most part, half of your project needs. You’ll still need a backend API. The better solutions for this is either Feathers for REST/ SocketIO interface, or with something like Apollo through GraphQL Yoga/ Prisma.
So, you might be looking at Quasar with the wrong intentions. It is basically a RAD system for frontend applications.
Scott
-
@s-molinari thanks for pointing me to the relevant directions; I thought I could use any spa/ssr builder framwork and then somehow integrate quasar functionality just for the mobile app builds.
This project requires a classic hopefully reactive web app (no ecommerce) rendered in usual browsers, linked to a mobile hybrid app (Android, IOS) with live notifications and things between them.
Having a generous timeframe I thought that the nodejs environment coupled with a reactive frontend might do a better job than my current LAMP stack, although it requires some heavy studying. -
Quasar is a good approach, because the components it offers can cover a wide variety of applications. It also makes it easier to jump into PWAs or native mobile apps over Cordova. You can even build out an Electron app, if you want.
Scott
-
@Rhobur I’m using SailsJS (as a rest api) with Quasar and it is awesome
Since SailsJS comes with rest api support out of the box it is really easy to get it going with Quasar.
If you don’t want to use Quasar for your web app (but you definitely should) you can just build API routes and use them in your with Quasar for building mobile apps.
Feel free to DM me if you have any quastions.
-
Yes, I’ve just learned that SailsJS also supports creating REST APIs. I guess I should have known, as Laravel does that too. LOL!
Scott
-
@s-molinari Yea it’s a nice framework. It uses Vuejs for views (some custom implementation of Vuejs via sailsjs cloud sdk (as they call it)).
Personally I don’t like it, I’m more for Rest API + Quasar solution…
Using Django (Django rest) or SailsJS or any other framework for the rest (depends on he skill or project) with Quasar is awesome. Productivity goes through the roofQuasar