@quasar/qwindow v1.0.0-alpha.1 Initial release!





  • @Hawkeye64

    Impressive! Wow!

    As I played with multiple window, there are issues with z-index for many windows. The last dragged/clicked should be always on top. It means, that there should be some kind of “window manager” with the concept of currently “active” window. And this “window manager” could have methods like “tile” or “arrange” or “cascade” or “hide/embed all” etc.

    There is a quirk with qscroller in window also. When the mouse is rolled over scroll area inside window, after the end of scroll area, the events are propagated to main page and it is scrolled also, which is slightly confusing. Scrolling over scroll area inside window should not affect the main document. In general, basically any events from your windows should not be propagated to main document.

    I do wonder what is your intended use case for this technology in the context of quasar apps (ie chat windows, iframes etc)?



  • @qyloxe

    As I played with multiple window, there are issues with z-index for many windows. The last dragged/clicked should be always on top. It means, that there should be some kind of “window manager” with the concept of currently “active” window. And this “window manager” could have methods like “tile” or “arrange” or “cascade” or “hide/embed all” etc.

    There is a property for that: https://quasarframework.github.io/app-extension-qwindow/examples#Bring-to-Front-After-Drag

    There is a quirk with qscroller in window also. When the mouse is rolled over scroll area inside window, after the end of scroll area, the events are propagated to main page and it is scrolled also, which is slightly confusing. Scrolling over scroll area inside window should not affect the main document. In general, basically any events from your windows should not be propagated to main document.

    Would you mind adding this as an issue please?

    I do wonder what is your intended use case for this technology in the context of quasar apps (ie chat windows, iframes etc)?

    I usually don’t think of how it will be used because then it becomes opinionated. I try to gie as many options as I can so the dev can make use out of it ways I never imagined. Of course, there is a generalized sense of what it oculd be used for (ie: QCalendar)

    Thanks for all the feedback. I ❤ it!



  • @Hawkeye64 said in @quasar/qwindow v1.0.0-alpha.1 Initial release!:

    @qyloxe

    Would you mind adding this as an issue please?

    Sure! Issues added.

    I usually don’t think of how it will be used because the it becomes opinionated. I try to gie as many options as I can so the dev can make use out of it ways I never imagined. Of course, there is a generalized sense of what it oculd be used for (ie: QCalendar)

    And yet your words inspired me to this: what is the difference between the “standard” qdialog and your qwindow? The qdialog works in the context of the other components/pages etc. Basically when you change route then the qdialog should disappear. BUT your qwindow, in total ingenuity, should work in global/layout context. Meaning, that when you change the route, the qwindow should remain! The qwindowmanager should be something similar to qdrawers then. It is truly brilliant what you created. This opens many possibilities when one needs something “global” on the screen (chat? log window? preview? debug panel? cms editor?).



  • ohhhh, debug panel - hadn’t thought of that. The possibilities are endless. That’s how I like to do design. 🙂 You never know how it’ll be used.


Log in to reply