Really like the site design and content. Responsiveness is excellent. Congrats! Mostly loads slow, but occasionally is very slow. Should show a proper message if client browser doesn’t support JavaScript.
I’m new to Quasar, but on first blush it appears that initial render size/speed is one of the biggest issues it faces. I wonder if the work on server side rendering will change that (across all of its build targets including Cordova).
@narmer23 Thanks Narmer23. I think the “can be added now too” is somewhat misleading to those new to Quasar.
The Quasar roadmap states that Typescript support “can be added now too”.
Where is how to add this support documented?
Excited about ,and grateful for the release. Many thanks. Now my dreams are all in TypeScript 
If you have a “long running application”, then use a “named” function as a global event bus listener rather than an anonymous one. This allows you to remove the event listener as Hawkeye64 mentioned.
You should not just use the event name as an argument for the $off method. Doing so will remove all event listeners for this event name. A specific listener is removed by providing both the event name, and a reference to the listener.
See the documentation for $off() at https://vuejs.org/v2/api/#vm-off for an explanation.
Be aware that a global event bus (i.e. via Quasar’s $root) is normally used between sibling components. Parent-child components do not need to do so, and do not require any explicit cleanup.
Make saveXX() a Vue instance method, rather than a global function as you’ve written, i.e. put it in “methods”. Alternatively, just execute your saveXX functionality in an anonymous function, e.g.
created() {
this.$root.$on('event_name', () => {
// your saveXX functionality that can access current instances "data" through "this"
// e.g. let myAge = this.age;
}
)
Really like the site design and content. Responsiveness is excellent. Congrats! Mostly loads slow, but occasionally is very slow. Should show a proper message if client browser doesn’t support JavaScript.
I’m new to Quasar, but on first blush it appears that initial render size/speed is one of the biggest issues it faces. I wonder if the work on server side rendering will change that (across all of its build targets including Cordova).
At question is really where to break down your application into different components, if at all. Once you decide that, you can communicate between components by having them raise events, which others listen out for and act on if necessary. Alternatively instead of notifying other components that something happened (and providing them with some optional information about that event), you might choose to store shared state globally, i.e. through Vuex.