No More Posting New Topics!

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.

I’m glad you figured things out. Was about to contact you so I can take a look now, but you were faster 🙂

@rstoenescu Your welcome,
I guess we all know what it’s like to see a thread end with “I found a solution. Thanks…(silence)”

Aah, I like you are careful at details! The “scroll” CSS class only applies some CSS tweaks to make scrolling smooth on ALL platforms. But it doesn’t make the container scrollable. You have to add some additional CSS like overflow-y: auto besides setting that height and it will work.

EDIT: I’m talking wrong. scroll also adds overflow CSS to your container. So it should work as is!

@rstoenescu Events work very well. Thanks.
Other option would be using “refs” as described in this post (opening a modal vue component with a button located on the main component)

http://forum.quasar-framework.org/topic/43/modal-create-vuecomponent-in-quasar-0-8

@rstoenescu Thanks Razvan. Using css will work fine for now.

Let me know if you encounter any issues upgrading.

I’d write one myself especially for Quasar but unfortunately just like you yourself said time “is a bit of a problem” 😞 Please share with us what path you finally choose. Thanks!

Every cent counts, unfortunately. I’m not in a good financial situation anymore. Invested all my money so I could work full time for the framework for a year and a few months, and bills keep piling up 😞
Anyway, thank you for even thinking about it!

Haven’t tried it yet, but it has no reason not to work with it. Although my recommendation is to go with vee-validate.