but I’m a Heinz 57.
My friend, you’re in big trouble. !
Hehehe… I know what you mean and some “Germaness” like attention to detail has rubbed off on my. But, it’s not my heritage. I just love living here.
Then based on your last name, my guess is, you’re Northern Italian.
I was a very young boy when Apollo 11 landed on moon and I was watching it on black & white TV. Everyone was so existed. I sat near the TV and I noticed something was odd. The shadows of objects did not all match direction. Some were on one direction and some on another direction. I told my Dad and he said, it’s the Lighting. I said, but there should be ONE source of light from the sun.
Almost 50 years later rumors came out that, that landing was fake and was done in a Studio in Hollywood, based on the shadows that I caught 50 years ago.
Good tip @turigeza!
I believe the plan is to add both a site wide search to the docs and a menu search to find the menu item you are wanting faster. I’m not 100% certain on the menu item, but I’d certainly like that. It would make the docs an awesome reference.
V1 Docs are much better now than before, but there is still room for improvement.
What really helps, is “Best Practices” guideline, how components should be nested or what steps to take build proper multi layered layouts that are created properly than us doing trail & errors.
A good rich sample app can help a lot as a good resource.
If the data of the table changes, should it be assumed that the formerly selected values not be kept “alive”, if those same values are still there? In other words, if they are the same row values, why not leave them selected?
If you want to “unselect” the rows, just empty the
selectedarray, when you do the update.
However, that would seem like bad UX to me, because if I am making a decision to select rows and it takes more than 10 seconds, my selections would happen to disappear on me. That would get a WTF? out of me.
Well said Scott;
yeah it is
So Max, is the content, for example when I look at a component info. and I see samples, API and etc, are these contents coming from DB and populating the forms dynamically or are they pre-rendered static data showing per page?
Secondly, is each option from menu, a page by itself using Vue’s lazy loading?
Is the doc app (https://v1.quasar-framework.org/introduction-to-quasar) written in Quasar V1? Does it make a good demo program for prospects to view it on desktop and mobile to see how a Quasar program runs? Until we get a nice sample demo from Quasar, can we suggest the Doc app for the time being?
Well my friend, as always you give me no-BS answer that I can make decision on. Thanks!
I’m staying with Vue (don’t like Angular)
I’m staying with Quasar for being “Vue Focused”
And I’m “hoping” Quasar Team, will keep the iOS Theme subject at the top of the list. This will come up as new developers join Quasar.
Again Thanks Scott;
Is there any plan that Quasar would carry two (min) sets of themes (one for iOS and one for Android or desktop browser), where the quasar framework at runtime would recognize the platform (Mobile iOS or Mobile Android or Desktop) and apply the platform specific CSS to all the components which they will look for their platform? This was brought up last year, but I thought it would be implemented in V1.
I’ve asked users how important it is that the components (i.e. buttons, list, input and etc.) to look like their native components and the # 1 request was this issue, then performance of scrolling.
So, is there any plan for the next six months for this to be implemented? Just FYI, Ionic 4 for Vue already has that built in. Trust me, we could lose potential users because Material Look & Feel running on iOS.
Please discuss this issue among your teammates, and consider it.
I just saw a video a friend had sent to me that showcased Ionic 4 and Vue. One very helpful feature they had is that they have themes and CSS that covers all their components for iOS and Android and desktop and it automatically switches to the theme for that platform at runtime… This feature didn’t exist in the previous version of Quasar and so far I’ve not read anything that indicates V1 has such theming system. Could you please tell us if this design is part of the roadmap within the next six months?
Thank you in advance!
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.