@labs20 said in Quasar and Keyboard issues:
It is reasonable to expect at least the firing of the standard events on some upcoming upgrade?
Quasar is at the level where some fundamental decisions are inevitable. The problem you encountered is the symptom of such a state. Those decisione will probably seal the fate of this framework. What are those decisions?
Well, Quasar needs to allow (or not - and provide a mechanism to implement it by user) the composition of components. It is not a “hard” problem, but it is the one, where when you decide something it will stick for to the end of life.
What is composition of components? You for instance want to have a global behaviour processing. This behaviour of components (for example validation, presentation, custom actions) depends on the source of native events - from keyboard. Quasar desperately needs to allow process global keyboard events in terms of bahavioral actions which have semantic meaning.
What are semantically meaning behavioral actions? This are actions, fired from external sources (keyboard in your example) but recognised, processed and finished at right components.
What is a right component? In the context of keyboard behaviours, the native browser has a concept of “focused element”. But this “element” can be a single DOM node so it is not useful at the framework level. In the context of framework, Quasar needs a concept and definition of “active” component. This is the one where such actions could be performed (maybe even on “focused” DOM node, but - you want to change that - and now you can’t).
There is more such semantic concepts - let’s take bahaviours of “drag’n’drop”. As for now, it is almost impossible to have a global, consistent DND actions between Quasar components.
Another one is a clipboard - we have VueX but the state of components is as for now not “serializable” or “marshalable”, so in some situations your app can have a “clipboard” with specific Quasar component in some you will hit a wall.
Another concept of global behaviour is “data sources” - as for now, QTable, QList, QTree etc. have specific needs for source of their data. You cant easily just plug this source to axios, or rest or graphql and hope that everything will just work.
OK - let me be clear - this is NOT a rant. Quasar is IMHO the best framework - at this specific level of development. I do admire and I’m in awe of what those guys created and how much good work they put into this. BUT there are always another levels. If you have a local national champion then you will have an opportunity to play in champions league, and this is a whole new game. The decisions I mentioned above are inevitable and there is one element which is preventing from put Quasar in one direction. It is a fear of a wrong decision. BUT - I am sure, and based on actual, so elegant Quasar architecture, that there is nothing to fear. Please just allow us to have keyboard, DND, data sources and we will be happy, and even if it will not be perfect at the first incarnation - it surely will be at one of the next.
