@Clareon Those are different components. Quasar TABLE is column oriented, datasource binding paged row viewer. What are you talking about is a GRID component, with x,y addressable CELLS. There are many Vue grid/table components, here is a list. You can choose almost anything and use it in Quasar app:

https://github.com/vuejs/awesome-vue#table

This one is very interesting, please look:
https://github.com/handsontable/vue-handsontable-official

And demo:
https://handsontable.com/docs/7.4.2/frameworks-wrapper-for-vue-simple-example.html

@mboeni nice question. My ideal logger:

• would be implemented as web worker (it will not be a burden for main browser thread)
• should write data to local indexeddb and then sync (when online) with logging backend service (because even if not online you should have a possibility to log events and review them later)
• should have a possibility to implement plugins for example mouse position heat maps, touch gestures, eye movement, browser capabilities etc.
• the sync protocol should be open so there will be at least one open source backend server in nodejs or python-fastapi and at least one commercial backend with extended analytics etc.
• should have tons of examples, snippets and demos
• should have quasar app extension for… something (?) ok - quasar integration out of the box would be really, really nice

@prodigy7 The typical way of such a “concept” project is to firstly build a codepen example with what you have now and then it will be easier for people to cooperate and come to solution. From what you write now, it is definitely possible but do we need some events communication, custom components wrapping input groups or something else - IDK. So, build the codepen

@prodigy7 this probably is NOT entirely what you want (at this moment) but it is probable, that (something like) this could be what you will end with

https://github.com/mesqueeb/quasar-ui-easy-forms

@mazahaler said in How to enable data reactivity on the server? (ssr mode):

@qyloxe I tried
And that hasn’t changed anything

hmm, this looks as an error somewhere to me. It should work! Unfortunately, i have almost zero expertise in SSR, maybe this is some SSR quirk.

BUT please do a one another test: There is a technology of navigation guards in vue router:

https://router.vuejs.org/guide/advanced/navigation-guards.html

They could be executed globally or locally, please implement at first a global one, log some info to the console and please check if your route is changed at all! Maybe this is an error?

@mazahaler and #2 - router watcher? technically it will catch initial page opening, too.

@mazahaler I would bet, that your component is created once and reused later, so when you use beforeCreate handler, the data are reused/not downloaded later. Try with a “mounted” or “beforeMount” handler or other one, whichever will be more suitable in your specific case.

Please look at this helpful diagram:
https://vuejs.org/v2/guide/instance.html#Instance-Lifecycle-Hooks

And one more suggestion: you are making a synchronous call to the server. Maybe this is right, but this stops the rendering (ok, I know you are using SSR) and the “more preferred” way is to communicate with the backend asynchronously.

And #2 please look also here - if your reactivity depends on route change, then maybe this will be the solution:
https://router.vuejs.org/guide/essentials/dynamic-matching.html

@king_of_leon Back4App looks interesting. The plan with more than 50 req/sec and more than 4GB DB costs $400 per month btw. With that kind of money one could have quite a fat dedicated server at OVH, for example. Just saying…

@s-molinari said in alternative for firebase:

I think he is looking for an APIaaS or BaaS. @qyloxe

Scott

Thought of that, too, but he also used term “live backend”. Hoping he will tell us what he will choose and how it will be integrated with Quasar “at the end of the day”

@king_of_leon said in alternative for firebase:

Best opensource alternative for firebase to use as live backend ?

Don’t know of best but those are possible:

RethinkDB:
https://rethinkdb.com/

PouchDB/couchdb/couchbase
https://pouchdb.com/

BUT my best (whatever that means ) “stack of choice” would be: websockets on client and fastapi/postgresql on the backend.
https://fastapi.tiangolo.com/advanced/websockets/

There was a time when I was fascinated by WebRTC but it is a rather “big guys” transport protocol. Quite simple at the beginning, nightmare in production.