Posts made by fsgiudice

Hi @rstoenescu
I had to stop updating an application to the new version because some features are missing in the new datatable: scroll version and sticky columns. Can I help in some way to push the addition of above features to v 0.15?

Great news Razvan!

Found how add styles via attributes prop:

:attributes="{'style': 'text-transform: uppercase;'}"

but should be usefull extend classes too.

Hi @rstoenescu,
may you add style and class extender props so it is possible to pass own classes and styles to <input> ?
At the moment I need to convert to uppercase an input text field and in vanilla html I can do:

style="text-transform:uppercase"

Actually I cannot add uppercase class to q-input
TIA

Thank you @rstoenescu

Yep, I’m in Italy, so is a wrong message by app store.

Same question here

Hi @ssuess,
Google says that app is not compatibile with any of my devices (Nexus 6P and Samsung 10" SM-T805) FYI

Same problem here

@rstoenescu thank you for reply. I will check better and try to create a navbar component.

Hi @rstoenescu, which part of that site (http://teachcloud.com.br/#/) are done with quasar?
I would implement top navbar but how?

Hi,
how can I clean test commits from fork?
I made a PR some minutes ago, but PR show a lot of commits also if only last one is correct.
TIA
Francesco

@rstoenescu
Hi, I already did so.
But with build I can use my fork like quasar-edge in package.json in my test apps.
The other way I tried was to add new components directly to my project, but there were collisions with some paths.
Now I will try using quasar-edge and adding components to apps.
I hope I was clear.
Anyway thank you for your time.
Francesco

Update:
no result playing with paths. As written before latter case works in build mode, former in dev mode.

@rstoenescu
Bingo!
changing to

@import 'src/themes/quasar.core.variables'

@import 'src/components/*/*.mat'
@import 'src/css-components/*/*.mat'
@import 'src/vue-components/*/*.mat'

@import 'src/themes/quasar.core.definitions'

and other files

        modified:   build/script.build.stylus.js
        modified:   src/themes/quasar.core.definitions.styl
        modified:   src/themes/quasar.core.variables.styl
        modified:   src/themes/quasar.ios.styl
        modified:   src/themes/quasar.mat.styl

now npm run build works.
But now I get error on npm run dev
So it is definitively a path problem on build script files.
I’m checking if I can find the error.

Francesco

@s.molinari
No, 64bit

@s.molinari
Sorry for misunderstanding, I know what cygwin is, but what is relation with npm and node?
Is it a prerequisite of those?
Because I use gnuwin32 for some other things and probably it clashes.

@rstoenescu
Yes, already done months ago and again with your last request.
But I’m not under cygwin environment.
Tell me something about this, because it could be the difference.

@rstoenescu,
actually with my fork of https://github.com/quasarframework/quasar.
To be sure, I have cloned your repository directly and, in a empty folder, I did:

git clone https://github.com/quasarframework/quasar.git
npm install
npm run dev

and it works, but if I do

npm run build

the error is exactly the same reported above.

Francesco

Hi @rstoenescu
nope, same error.

Also updated to latest node 6.9.2 and npm 4.0.5 but same results.
npm run dev works correctly, instead npm run build not.
It seems to me as some other global is missing.
Thank you for your effort.

Francesco