Quasar v1.0 beta has arrived
-
In the documentation, the transitions are not very useful. In everyday life I would prefer without
-
@marc;
I have to agree with Marc with the font issue. the fonts are thin, light colored and the background is gray which does not provide enough contrast for long reading.Could you use a different font that is thicker and darker please.
-
QDate --> (with QInput section) https://v1.quasar-framework.org/vue-components/date#With-QInput
QTime --> (with QInput section) https://v1.quasar-framework.org/vue-components/time#Using-with-QInputOr even a QInput type=“date” or type=“time” directly.
-
@rstoenescu
Ok but what about Qinput type=“datetime”? Is it possible in 1.0?
-
@marc
looks exactly like the Vue documentation to me.I assume it also follows material spec.
-
-
This is the most exciting news I’ve seen in the front end universe for a long, long time. Quasar takes the coolest tools in FE development—Vue, Webpack, SSR, the best icon sets, Cordova, Electron, etc., and delivers them to the FE dev on a shiny platinum platter. 1.0 is a revolutionary breakthrough… light years ahead. Razvan is a genius!
-
Congratulations! Looks very promising!
… A logistical question: Where would you like to get potential “bugs” concerning 1.0 reported - forum/git?
-
@enpasos Good question! Looking for answer as well.
Meanwhile I submitted a “pull-request” on github for docs. A small typo on ‘QPopupProxy’.
-
Date with Input (Popup position not good)
-
@theara at least there is the typing functionality that was really really needed.
-
Just WOW! I’ve never been more impressed or excited about version 1 of anything, ever.
Quasar has helped restore my faith in frameworks and I no longer wake in a cold sweat after seeing a certain angular logo creeping into my nightmares.
A big THANK YOU to the whole team. You should be very proud (and extremely rich).
-
@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!
