Will push a commit to allow this which will get into v0.9 later this week. Thanks.

@xereda Hi, write that CSS in App.vue style tag at the end.

@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.

Maannn… thank YOU by making this awesome work!

@rstoenescu thank you so much.
I was added to the shadow class in “class”. 😢

No plan to do this on v0.9. Maybe on later releases.

@kosciak ok! Tks for help

Also, for Icons: https://cordova.apache.org/docs/en/latest/config_ref/images.html

@rstoenescu I understand perfectly. And I believe that is correct. That’s right!

Great! Glad everything is working.

Thanks! Turned out that my issue is a different one. In an attempt to avoid unnecessary DIVs I’ve added both layout-view and layout-padding to the same DIV. Turns out that this isn’t a good idea. Moved layout-padding into a separate DIV, scrollbar moved nicely to the right.

Lists are not for everything. Secondary can only be icon or text.
If you want something fancier, simply create your own using Grid CSS: http://quasar-framework.org/api/css-grid-layout.html

Some unpolished example:

<div class="row items-center"> <div class="auto">admin</div> <button class="primary">Edit</button> </div>

Quasar will have its own “autocomplete” feature built-in in the future. Until then, you can use other libs like Remo suggested.

Using the name property has no place in talking about how to require/register a component because it doesn’t affect it in any way. This means however you can use and there’s no reason or recommendation not to. It’s just out of the scope of custom component discussion.

On the todo-list: https://github.com/quasarframework/quasar/issues/108

Search plugin installed. Thanks for reporting this 🙂

Select documentation: http://quasar-framework.org/components/select.html
You need a model and options. Options object looks like this (just an example):

selectOptions: [ { label: 'Google', value: 'goog' }, { label: 'Facebook', value: 'fb' }, ... ]

Use Vue computed properties if needed 😉

0_1478765572526_source.png

http://www.sass2stylus.com/

You can use this to go with 100% Stylus setup. 🙂

Some more things worth mentioning. I’ll just copy paste my comment on the latest Quasar starter kit / template:

/* * NOTE! VueRouter "history" mode DOESN'T works for Cordova builds, * it is only to be used only for websites. * * If you decide to go with "history" mode, please also open /config/index.js * and set "build.publicPath" to something other than an empty string. * Example: '/' instead of current '' * * If switching back to default "hash" mode, don't forget to set the * build publicPath back to '' so Cordova builds work again. */

Also, changing the “publicPath” should be carefully considered as it impacts the way you reference static assets.