No More Posting New Topics!

If you have a question or an issue, please start a thread in our Github Discussions Forum.
This forum is closed for new threads/ topics.

Navigation

    Quasar Framework

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    1. Home
    2. jaguard
    J
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 2
    • Best 1
    • Groups 0

    jaguard

    @jaguard

    2
    Reputation
    56
    Profile views
    2
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    jaguard Follow

    Best posts made by jaguard

    • How to organize a family of Quasar-based projects that are using common/internal components & modules

      I’m in process of developing a “family” of projects for which I’ve considered Quasar being the best options.
      Here are the “individual” projects:
      1 x Cordova ClientApp: Android/iOS mobile application used by regular users (include BT/BLE support)
      2 x Cordova AdminApp: Android/iOS mobile application used by admins
      1 x SPA Dashboard: web application used by support
      1 x Electron TechnicianApp: Windows desktop app (with off-line support) with BT/bleno integration

      Aside of specialized functionality in all these apps, there are some common functionality and components that I want to reuse, so some modularization by introducing common “library” kind of modules should be used (ex: using FIrebase + authentication + login component, common store/module for user management …etc).

      Maybe the optimal solution is not necessary Quasar specific, but the issue is more generic and may apply to VueJS shared projects as well … The idea is to avoid exposing & publishing internal components as Node modules to be imported in other “consumer” projects …

      I had various ideas like using npm/yarn link to use internal modules without npm publishing or using a monorepo and yarn workspaces … but having a sample/template that really works it will be a lot better 😉

      Any suggestions , hints, links and refs will be highly appreciated … !

      posted in Help
      J
      jaguard

    Latest posts made by jaguard

    • RE: Live update (Hot code push)

      I;ve succesfuly deployed in production an alternative solution from Adobe/PhoneGap phonegap-plugin-contentsync https://github.com/phonegap/phonegap-plugin-contentsync , it seams it works similarly

      posted in Framework
      J
      jaguard
    • How to organize a family of Quasar-based projects that are using common/internal components & modules

      I’m in process of developing a “family” of projects for which I’ve considered Quasar being the best options.
      Here are the “individual” projects:
      1 x Cordova ClientApp: Android/iOS mobile application used by regular users (include BT/BLE support)
      2 x Cordova AdminApp: Android/iOS mobile application used by admins
      1 x SPA Dashboard: web application used by support
      1 x Electron TechnicianApp: Windows desktop app (with off-line support) with BT/bleno integration

      Aside of specialized functionality in all these apps, there are some common functionality and components that I want to reuse, so some modularization by introducing common “library” kind of modules should be used (ex: using FIrebase + authentication + login component, common store/module for user management …etc).

      Maybe the optimal solution is not necessary Quasar specific, but the issue is more generic and may apply to VueJS shared projects as well … The idea is to avoid exposing & publishing internal components as Node modules to be imported in other “consumer” projects …

      I had various ideas like using npm/yarn link to use internal modules without npm publishing or using a monorepo and yarn workspaces … but having a sample/template that really works it will be a lot better 😉

      Any suggestions , hints, links and refs will be highly appreciated … !

      posted in Help
      J
      jaguard