Ok. Just wanted to give a helping hand

Hey. Are there any plans to make the progressive loading buttons closer to the native ones, material having those round spinner etc. If not, do you need any help with that?
Also, and this is just an idea, could we at some point, have a start, done, error methods on the intermediate so it can go back to its default state after X amount of time? I know I could run a timeout on my “progress” prop and set it to 0, but it can get a pain, I would have to extend the quasar button with my own button to not write it everytime.
On a side project of mine I implemented pretty much the same because I couldn’t use quasar there and it is really useful for Ajax calls and what not.

Use a slider component with your content in each slide. Then you can watch the @slide event emitted from the slider and change the tabs above. Problem is that you have to have a prop for the tab nav and the currentSlide in the slider and sync them altogether which can be a pain.
Currently the tabs component doesn’t support this out of the box. You can file an issue on github and who ever has time to do this first will try to do a PR.

Its because the parent is set to have a align-items:stretch which stretches all the elements so they have the same position. You have to do a align-items:center or use the items-center class on the parent.

Oh no, not at all. I need a horizontal slider where you slide left and right for each day and that’s it. If you go to the 1st of April and go back it goes to the 31-st of March. I will probably try to implement something later and see if I manage.

OK so I want to create an infinite slider that shows days of the month. Its to be used in a diary of sorts so you start of in the current day and you can swipe left and right to navigate to the day you need. Moment.js would be used for date stuff.
Maybe I can use computed properties to dynamically change prev/next days/components depending on what is currently selected? Then check if I have anything stored for the current, prev or next day and change accordingly?
@rstoenescu Do you have any idea if the Slider component would be able to handle this, or if this approach is any good at all. I think it should be able to handle dynamically adding and removing components.

I am planning to write a tutorial on this when I`m done with it because I couldn’t find anything on the subject.

Vuelidate works wonderfully

I think its in the future plans, currently they are pretty tightly coupled to the framework.

What is the conflict? Any errors?

Today I was thinking about some custom checkboxes I had to implement on a project, that alas does not use Quasar. At one point I looked at the checkbox component code from Quasar and I really liked the way you have implemented the model computed property, really clean. But as I read the docs, input:checkbox can be assigned to an array when its value is set, this way it will add or remove its value from the array, something we cant really do without reinventing the wheel (check to see if the passed v-model value is array, and if current value exists yada yada), so I tried instead of assigning this.model = this.value in the select method, simply to do a this.$refs.checkbox.click() , its native and it actually works pretty good. Here is my implementation, maybe it could help someone else. If this is a bad idea, I would really like someone to tell me early on
Bellow is the radio implementation, checkbox is pretty much the same.

<div class="input-styled radio">
    <input
      class="input"
      type="radio"
      v-model="model"
      :value="value"
      :name="name"
      :disabled="disable"
      ref="radio"
      @click.stop
    >
    <label @click.stop.prevent="select">
      <span class="styled-element"/>
      {{ title }}
    </label>
  </div>

  export default {
    props: {
      value: {
        required: true  // passed from the parent to populate the radio's Value
      },
      checked: {
        required: true  // passed by v-model to sync the :checked property
      },
      disable: Boolean,
      title: {
        required: true
      },
      name: {
        type: String,
        default: ''
      },
      id: {}
    },
    model: { // new property since 2.2
      prop: 'checked', // set the parent's property thats passes to v-model to the checked prop on the child
      event: 'change' // do the above action when this event is fired
    },
    computed: {
      model: {
        get () {
          return this.checked // just return the value from v-model
        },
        set (value) {
          if (value !== this.checked) {
            this.$emit('change', value)  // when we set this.model we emit an event with the current value
          }
        }
      },
      _id () {
        return this.id ? this.id : this._uid + '_' + this.checked
      }
    },
    methods: {
      select () {
        this.$refs.radio.click() // trigger a click on the input element
      }
    }
  }