Site Examples
-
Hi,
A part of the project site examples is not synchronized with what is presented in the simulator. To avoid problems, always access the sample source code that is there in github.
By any chance, is there any task maped for updating the examples that are on the site !?
I question this, because it is a recurring question in our groups in the telegram, both in the “Quasar Framework Brasil”, as well as in “VueJS Brasil”.
Thanks for return.
-
@xereda Hi. Can you give specifics? What have you found to not be synchronized?
-
http://quasar-framework.org/components/floating-action-buttons.html
Notice the difference of what we have in the simulator compared to the documentation on the left. The FAB button is an example, but there are others that I can not remember now.
-
I can get around this by seeing the source code, no problem. But I was concerned, seeing several developers report that the site examples do not exactly match what is being shown. So I quoted here on the topic. For I am evangelizing Quasar here and this is a recurring issue.
In fact, Ionic itself does not have exactly the same code that is presented in the simulator. At least it did not beat me up when I studied him. Believed that the site code, the example on the left of the page, is for illustration only, and base code must be retrieved from github.
What do you think about this issue?
-
Please reply to this thread whenever you find inconsistencies so I can fix them.
Porting everything to Vue 2 was done at light speed and some inconsistencies may exist in documentation because of this. People wanted to jump to using Vue 2 really fast because of deadlines in their projects.
-
@xereda What exactly is the difference for FABs? I’m exhausted in my defense, but can’t spot the inconsistencies there…
-
I understand perfectly.
-
-
Well in this case yeah. The simulator is Quasar App, which needs to be an app on its own. People install in Google Play Store, need to have a feel of the framework. When on a documentation website, the examples need to teach a certain aspect but in a gradually manner. The simulator UI in this case would be a too complex example when starting to learn about FABs (too many features at once in an example that should focus on FABs only).
-
@rstoenescu said in Site Examples:
Well in this case yeah. The simulator is Quasar App, which needs to be an app on its own. People install in Google Play Store, need to have a feel of the framework. When on a documentation website, the examples need to teach a certain aspect but in a gradually manner. The simulator UI in this case would be a too complex example when starting to learn about FABs (too many features at once in an example that should focus on FABs only).
Makes sense. Thank you.
I already passed this on to the developers here. If they go to analyze the Ionic site, the same thing happens.
