How about a small <script> body with minimum a export default {} inside ?

I guess vue-loader would complain if the html is not valid, but this is the only thing i can come up with. Have you looked at the render function output the loader generates ?

I think the 0.14 release will be the first thing to consider, and then some months with consolidation

It would be nice with an interface like the IndexedDB, but we also need some query handling and event insertion, and editable grids. What I am saying is, that this could be a potential large project in it self.

But some inspiration from things like dgrid may be worth including

Ok, so … if we could make WebPack build the two themes as two separate css bundles, we could load these after platform detection ?

I tried to do this (separating the css file from the main bundle), as we like our customers design requests separate from the main logic, but at the moment we let the http server do the mapping of these files.

Perfect, I had not checked 0.14 css setup yet, seems like a good time to do this really soon.

Have you any idea how hard it will be to make dynamic theme change ?

I understand the distinction between theme and platform, but I just realized that the only css indication is a class on the body, but this is not related to the detection code but only to the theme. So no, I was not looking for __THEME, but it is a useful thing to know

These theme things are all injected in the quasar init code, last time I looked, and I thought that we could benefit from a platform related class too, so platform quirks in css can be globally controlled by this. If this was the case I could write CSS like this :

.ios_platform iframe {
    width: 1px
    min-width: 100%
}

If ios_platform was set on the body tag along with the theme (ìosormat`) it would be really nice, and we have all detection ready anyway at this point.

Btw…can 0.14 select theme automatically (or be setup for this) ?

Hi …

I was very happy to see that Quasar got a DataTable , as this is a extremely useful component, but I like to use other sources that plain data in an array, an like to ask if it would be possible to make some kind of data store.

This way we could support the current data array model, but also make things like paged RESTful called to deferment backends, but isolate data providing and rendering.

Something like :

class DataStore {
    query( args: Object, order: Array, limit:number, offset: number ) : es6_iterator

    getKeyName(): string
    remove( key )
    set( key, data ) 
    get( key ) : any
}

This model would of cause have a memory version that could be used by default, to make it simple to make simple things.

I could also try to do this as a PR (if I can find a way to make it work), is this has any interest