Vue dialogs

[skjnldsv]

cc @ChristophWurst

Relevant: nextcloud-libraries/nextcloud-vue#408

Closes #6601

[georgehrke]

@skjnldsv Shouldn't this ticket be in the nextcloud-vue repo?

[skjnldsv]

No, because this is about the OC.Dialog implementation.
The nextcloud-vue repo is about the component itself ;)

[ChristophWurst]

We can still have them in nextcloud-vue and re-export in server if really needed. I would keep the number of OC.Dialog APIs as minimum as possible.

[ChristophWurst]

Maybe we just need more description to understand what this ticket is about @skjnldsv 😉

[skjnldsv]

@ChristophWurst well, just replace OC.Dialog? What can I tell more? 🤔

[georgehrke]

Shouldn't we try to deprecate OC.Dialog and let it die eventually?
It's enough if there is an equivalent in vue-components, i don't see a need to ship it in the server

[georgehrke]

(I forgot there is OC.dialogs.filepicker. That we should definitely keep)

[skjnldsv]

It's enough if there is an equivalent in vue-components, i don't see a need to ship it in the server

Well, I'll argue against it by saying this would force everyone to use vue.
If I have a tiny script with pure javascript (which is far better than having a full vue app to compile) that takes 10 lines because it require two checkboxes and a dialog, I would say we should keep a standard.

The dialog component could contain lots of things, and therefoe require a vue component (standard)
But the use cases on server are simple and should be something like: password input, confirm dialog, duplicate file dialog. (anything else?)

[skjnldsv]

nextcloud-libraries/nextcloud-dialogs#301