Welcome back!

Posts made by fsgiudice
-
RE: Data Table sticky header 0.15
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? -
RE: Add style and class extender to q-input
Found how add styles via attributes prop:
:attributes="{'style': 'text-transform: uppercase;'}"
but should be usefull extend classes too.
-
Add style and class extender to q-input
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 -
RE: Quasar live apps/website [submit to https://github.com/quasarframework/quasar-awesome]
Yep, I’m in Italy, so is a wrong message by app store.
-
RE: Quasar live apps/website [submit to https://github.com/quasarframework/quasar-awesome]
Hi @ssuess,
Google says that app is not compatibile with any of my devices (Nexus 6P and Samsung 10" SM-T805) FYI -
RE: Quasar live apps/website [submit to https://github.com/quasarframework/quasar-awesome]
@rstoenescu thank you for reply. I will check better and try to create a navbar component.
-
RE: Quasar live apps/website [submit to https://github.com/quasarframework/quasar-awesome]
Hi @rstoenescu, which part of that site (http://teachcloud.com.br/#/) are done with quasar?
I would implement top navbar but how? -
Help for git clean test commits from fork
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 -
RE: Local build not work
@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 -
RE: Local build not work
Update:
no result playing with paths. As written before latter case works in build mode, former in dev mode. -
RE: Local build not work
@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
-
RE: Local build not work
@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. -
RE: Local build not work
@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.