@bonatoc Absolutely true! I am amazed at how pushy people get for something as soon as it is released. At least let all your upstream libraries to get caught up and tested so it doesn’t break your own products. I am happy to stay a few months behind.
@reks Can you make sure IE is specified in your browserslist inside your package.json - you inadvertantly may not be supporting IE
@donvie @Luis-Adriani Please follow the Electron guide here: https://www.electronjs.org/docs/api/tray
@walfin You should be lazy-loading your images and in place, use QSkeleton until the image is available. If you load all your images at once, the time delay before the first screen is available will be horrendous.
This works only if your button never uses the disable state. If that happens, then the tooltip can become permanently visible.
@dsl101 You should look into dynamic components: https://vuejs.org/v2/guide/components.html#Dynamic-Components
@Taras Then try making it a true JSON object. Currently, you have it hosted as a JS file with export default. That’s a js object.
You can import JSON without making it a js object.
@greenzone Quasar and official App Extensions follow (for the most part) the BEM methodology for CSS naming. It helps prevent collisions.
Here are some links:
https://css-tricks.com/bem-101/
http://getbem.com/naming/
@julczka You didn’t give your QCalenda a view (in code above). The actual QCalenda is a component wrapper. Itself does have @click:date and @click:date2, but the other ones come from the specific component being wrapped.
Also, to avoid overhead, the events are not fired unless there is a listener for it.
Here is a Codepen where you can try out the new events: https://codepen.io/Hawkeye64/pen/eYzJPEW
@Pablo74 There is a markdown-it-mathjax, unfortunate for you, they do not provide a UMD version of it. So, you will not be able to extend the UMD version of QMarkdown with it.