Quasar v1.0 beta has arrived
-
@wannymiarelli, could I custom popup position like this
-
@ben-hayat my apologies, I was comparing them on my phone which looked close to identical as far as I could tell. Now that I’ve had a chance to look at the desktop version, I agree that the font could be a bit weightier at the very least. However, the documentation is a HUGE step up.
-
No apology needed my friend, as we all are part of a family trying to make this product better.
However, the documentation is a HUGE step up.
That’s the problem. It’s a great doc and I want to read it, but the poor font and color puts strain on my eyes. This is technical docs for us to read, it’s not marketing contents to look fancy with dim color.
@ Team, please make the fonts darker than thicker. At least make it like Vue. js site with white background and not gray.
-
@ben-hayat
There is also good documentation at https://devdocs.io. You can navigate with the keyboard, view offline and it’s very responsive
It would be best to have Quasar available in this centralized documentation.Marc
-
Can we have a dark theme? Maybe something like this.$q.theme.dark = true, and components with their default “dark” props with that value
-
Does anyone know QField is deprecated?
QField does not exists in 1.0 doc, although QField still exists in quasar dev branch. -
Thanks for the new color scheme of the site, it looks very good!
-
Has anyone already mentioned that u guys are VERY awesome? Thank you Razvan and colaborators!
-
@pavarine said in Quasar v1.0 beta has arrived:
Has anyone already mentioned that u guys are VERY awesome? Thank you Razvan and colaborators!
I’ll have to agree. Quasar 0.x already was the most developer-friendly framework imo, but with v1.0 you guys kicked it to another level. Really impressive.
-
-
Hi, it’s look awesome. Thanks!!
How upgrade to V1.?
-
@tofu Looks like QField is all part of QInput now, which is a very nice change.
Keep in mind that you will now have to use the somewhat humourous ‘bottom-slots’ attribute.
Also, the warning and warning-label props have been removed. I am currently trying to figure out how to colour the error message…
Any tips, guys?
-
@rstoenescu how to add plugins now in v1? quasar new plugin <name> doesn’t seem to work.
-
@metalsadman they’re now called ‘boot’ files.
quasar new boot <plugin name>
Then add the same name to the boot array in quasar.conf.js
-
@Jezzta667 yeah i saw that they’ve change the term for it, thx.
-
Awesome! And the docs are really clear and refreshing as well.
-
@mauri said in Quasar v1.0 beta has arrived:
Hi, it’s look awesome. Thanks!!
How upgrade to V1.?
This!
I got v1 installed and I’m in the process of testing it out (seems AWESOME!!), but was wondering is there a command / path to upgrade existing 0.17.23 project to 1.0?
/ Janne
-
@JanneMekanismi we’re working on it.
