Navigation

    Quasar Framework

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    1. Home
    2. cheesy
    C
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 9
    • Best 2
    • Groups 0

    cheesy

    @cheesy

    1
    Reputation
    318
    Profile views
    9
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    cheesy Follow

    Best posts made by cheesy

    • $ quasar dev not working

      Hi there.
      I have a problem whit quasar when I run: $ quasar dev I get the following output in terminal:

       app:dev Running: Mode [ SPA ] with [ MAT ] theme +0ms
      
       app:quasar-conf Reading quasar.conf.js +816ms
       app:dev Checking listening address availability (192.0.0.10:8080)... +4ms
       app:quasar-conf Generating Webpack config +13ms
       app:quasar-conf Extending Webpack config +24ms
       app:generator Generating Webpack entry point +16ms
       app:dev-server Booting up... +4ms
      
      Build completed in 11.943s
      

      When it should be something like:

       app:quasar-conf Reading quasar.conf.js +816ms
       app:dev Checking listening address availability (192.0.0.10:8080)... +4ms
       app:quasar-conf Generating Webpack config +13ms
       app:quasar-conf Extending Webpack config +24ms
       app:generator Generating Webpack entry point +16ms
       app:dev-server Booting up... +4ms
      
      Build completed in 11.943s
      
      
      
       DONE  Compiled successfully in 11721ms                                                        6:12:27 PM
      
       I  App [SPA with MAT theme] at http://192.0.0.10:8080/
      

      I am using a linux desktop enviroment (Ubuntu 18.04)

      System Information as displayed by the: $ quasar info command:

      Operating System        	Linux(4.15.0-24-generic) - linux/x64
      NodeJs                  	10.4.1
      
      Global packages         	
        NPM                   	6.1.0
        yarn                  	Not installed
        quasar-cli            	0.16.4
        vue-cli               	2.9.6
        cordova               	Not installed
      
      Important local packages	
        quasar-cli            	0.16.4	(Quasar Framework CLI)
        quasar-framework      	0.16.0	(Build responsive websites, PWAs, hybrid mobile apps and Electron apps, all simultaneously using same codebase)
        quasar-extras         	2.0.2	(Quasar Framework fonts, icons and i18n.)
        vue                   	2.5.16	(Reactive, component-oriented view layer for modern web interfaces.)
        vue-router            	3.0.1	(Official router for Vue.js 2)
        vuex                  	3.0.1	(state management for Vue.js)
        electron              	Not installed
        electron-packager     	Not installed
        electron-builder      	Not installed
        @babel/core           	7.0.0-beta.49	(Babel compiler core.)
        webpack               	4.9.1	(Packs CommonJs/AMD modules for the browser. Allows to split your codebase into multiple bundles, which can be loaded on demand. Support loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.)
        webpack-dev-server    	3.1.4	(Serves a webpack app. Updates the browser on changes.)
        workbox-webpack-plugin	3.2.0	(A plugin for your Webpack build process, helping you generate a manifest of local files that workbox-sw should precache.)
      
      Networking              	
        Host                  	[EDITED]
        enp1s0                	192.0.0.248
        wlp2s0                	192.0.0.10
      

      I have:

      1. Checked that the port 8080 is free
      2. Check if there is a new version of vue-cli or quasar-cli
      3. Check quasar.conf.js for erros
      4. Try quasar clean and quasar dev again

      Any other ideeas?

      posted in Help
      C
      cheesy
    • RE: Feature request: <q-map>

      @dari I use this: https://www.npmjs.com/package/vue2-google-maps with quasar and vuex and is working pretty awesome it supports a tone of custom functions and is still maintained.

      posted in Framework
      C
      cheesy

    Latest posts made by cheesy

    • RE: Quasar add electron mode in Debian need some love

      @metalsadman so you say that I need to run a build command once to get this working whithou need of using:

      sudo sysctl kernel.unprivileged_userns_clone=1
      

      ?

      posted in Help
      C
      cheesy
    • Quasar add electron mode in Debian need some love

      Every time I need to add electron mode on my Debian Buster system when developing before running

      quasar dev -m electron
      

      I need to run:

      sudo sysctl kernel.unprivileged_userns_clone=1
      
      quasar info
      

      show that the electron-packager and electron-builder is not installed!
      (Untitled.png

      Developing this way is not a problem for me but I really thing that should be a better way to do this.

      posted in Help
      C
      cheesy
    • RE: How to change the color of the text of a placeholder

      You can use:
      class_name::placeholder { color: #000000 }
      My personal recomandation use as much path you can instead of the class name just to be sure your css is not overiten by other from the framework or any other third party.

      posted in Help
      C
      cheesy
    • RE: Quasar v0.17.11 & CLI v0.17.14 are out!

      Thanks man.

      posted in Announcements
      C
      cheesy
    • RE: Feature request: <q-map>

      @dari I use this: https://www.npmjs.com/package/vue2-google-maps with quasar and vuex and is working pretty awesome it supports a tone of custom functions and is still maintained.

      posted in Framework
      C
      cheesy
    • RE: Checkbox component is faulty

      @s-molinari agree with you but is good to know about a problem this is the first step in solving them. And yes in Firefox browser it`s not happening that is why I mentioned Chrome browser and Opera browser as well. I didn’t test it in Internet Explorer or Safari because I do not own a machine with any Micro$$oft or Apple software.

      Thanks for confirming this @s-molinari .

      Have a nice day!

      posted in Framework
      C
      cheesy
    • RE: Checkbox component is faulty

      @genyded if you make the movie bigger and take a closer look at the checkbox you will see is jumping when is checked (at about one second after the click) this is on the documentation pages not in any application you can try it yourself, there on the documentation page, using Google Chrome browser or Opera Browser I do not think is necessary to provide any fiddle or code. The view you’re using does not count, I tried both of them and both have the same behavior, the checkbox is moving at one second after the click is made . Sorry that I did`n make much sens in my first post and I assure you is there I have test it many times.

      posted in Framework
      C
      cheesy
    • Checkbox component is faulty

      In some cases I observed a strange behavior at checkboxes. I do not have enough privileges to upload a video here so I uploaded it on an Youtube unlisted link (not avaiable at search). This bug is present in Quasar-Framework showcase and and components page Checkbox component page from documentation. And is about that a checked checkbox is moved from the previous position that have as an uncheked chwckbox.

      P.S: @rstoenescu thanks for this awesome framework.

      posted in Framework
      C
      cheesy
    • $ quasar dev not working

      Hi there.
      I have a problem whit quasar when I run: $ quasar dev I get the following output in terminal:

       app:dev Running: Mode [ SPA ] with [ MAT ] theme +0ms
      
       app:quasar-conf Reading quasar.conf.js +816ms
       app:dev Checking listening address availability (192.0.0.10:8080)... +4ms
       app:quasar-conf Generating Webpack config +13ms
       app:quasar-conf Extending Webpack config +24ms
       app:generator Generating Webpack entry point +16ms
       app:dev-server Booting up... +4ms
      
      Build completed in 11.943s
      

      When it should be something like:

       app:quasar-conf Reading quasar.conf.js +816ms
       app:dev Checking listening address availability (192.0.0.10:8080)... +4ms
       app:quasar-conf Generating Webpack config +13ms
       app:quasar-conf Extending Webpack config +24ms
       app:generator Generating Webpack entry point +16ms
       app:dev-server Booting up... +4ms
      
      Build completed in 11.943s
      
      
      
       DONE  Compiled successfully in 11721ms                                                        6:12:27 PM
      
       I  App [SPA with MAT theme] at http://192.0.0.10:8080/
      

      I am using a linux desktop enviroment (Ubuntu 18.04)

      System Information as displayed by the: $ quasar info command:

      Operating System        	Linux(4.15.0-24-generic) - linux/x64
      NodeJs                  	10.4.1
      
      Global packages         	
        NPM                   	6.1.0
        yarn                  	Not installed
        quasar-cli            	0.16.4
        vue-cli               	2.9.6
        cordova               	Not installed
      
      Important local packages	
        quasar-cli            	0.16.4	(Quasar Framework CLI)
        quasar-framework      	0.16.0	(Build responsive websites, PWAs, hybrid mobile apps and Electron apps, all simultaneously using same codebase)
        quasar-extras         	2.0.2	(Quasar Framework fonts, icons and i18n.)
        vue                   	2.5.16	(Reactive, component-oriented view layer for modern web interfaces.)
        vue-router            	3.0.1	(Official router for Vue.js 2)
        vuex                  	3.0.1	(state management for Vue.js)
        electron              	Not installed
        electron-packager     	Not installed
        electron-builder      	Not installed
        @babel/core           	7.0.0-beta.49	(Babel compiler core.)
        webpack               	4.9.1	(Packs CommonJs/AMD modules for the browser. Allows to split your codebase into multiple bundles, which can be loaded on demand. Support loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.)
        webpack-dev-server    	3.1.4	(Serves a webpack app. Updates the browser on changes.)
        workbox-webpack-plugin	3.2.0	(A plugin for your Webpack build process, helping you generate a manifest of local files that workbox-sw should precache.)
      
      Networking              	
        Host                  	[EDITED]
        enp1s0                	192.0.0.248
        wlp2s0                	192.0.0.10
      

      I have:

      1. Checked that the port 8080 is free
      2. Check if there is a new version of vue-cli or quasar-cli
      3. Check quasar.conf.js for erros
      4. Try quasar clean and quasar dev again

      Any other ideeas?

      posted in Help
      C
      cheesy