@mfoitzik Thank you for offering. If all goes well, I’ll have v0.14 as feature complete by the end of next week (although I’m sure there’s going to be bugs to solve before first beta). This new version will allow Tree shaking which impacts how the current (& not ready) standalone version is built. Let’s wait for the tree shaking to be available and then we can walk you through the simple guideline to make this work. Drop me a message on Gitter or an email so we can communicate faster. Thanks!
Your specific case needs CSS investigation. It might be the case of a bug in cytoscapejs dealing with flexbox and setting height. There are lots of quirks on that. A live example would be useful, but trying to remain sane as I develop v0.14 and answering a million questions
Not sure what you mean by your last statement (“If it is includes some divs then all them are zero height”). It would mean Quasar Play for example shouldn’t work. Maybe I didn’t understand your issue.
Currently not possible because Material Icons is a ligature font while the others are not. End result is the different markup these font icons need. For material you need to have a text element inside the <i> tag (<i>alarm</i>) while for Fontawesome you need to add a class name to the tag (<i class="fa fa-calendar"></i>).
As a result, v0.14 will have a q-icon component which will deal with the correct markup.
You need a deep integration of Electron. But this will break websites/mobile app build though (as importing electron in a browser or mobile app will fail), so you’d need two repos: one for electron and one for websites/mobile apps.
How to do deep integration:
In root folder of your project, npm install electron
In /build/webpack.base.conf.js add target: 'electron-main' to exported object
In electron wrapper folder (/electron) add target: 'electron-renderer' to /electron/build/webpack.conf.js exported object
You are perfectly describing AjaxBar component (http://quasar-framework.org/components/ajax-bar.html), except this component shows for ANY Ajax calls (which is excellent when loading route data too). Quasar uses Webpack chunk loading (which happens through Ajax) for Vue routes.
Most elements generated by Quasar components have class names. Use that.
Components encapsulate functionality. It’s generally a bad idea to base your tests on Quasar implementation details (such as inner HTML structure) because these details can change at any time without notice (while functionality remains the same). This goes for ANY framework out there.