You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For me with the experience of the last release it seems that the migration to Vue.JS should be the next/first step in the next release.
Currently only @danxuliu can work on JS/UI related stuff, due to the wizard staff in his hand which makes him able to understand and handle the Backbone/Marionette stuff.
The biggest issue is, that we have a bloated entry point (app.js, which already got smaller with the recent extractions). Also there are lot of tools/packages which help us concentrating on our core business: the talk app.
Also this would help as a base work for other stuff on our todo list and prevent duplicate UI implementations as we have to do everything in backbone/marionette first and then in Vue again:
For me with the experience of the last release it seems that the migration to Vue.JS should be the next/first step in the next release.
Currently only @danxuliu can work on JS/UI related stuff, due to the wizard staff in his hand which makes him able to understand and handle the Backbone/Marionette stuff.
The biggest issue is, that we have a bloated entry point (app.js, which already got smaller with the recent extractions). Also there are lot of tools/packages which help us concentrating on our core business: the talk app.
Also this would help as a base work for other stuff on our todo list and prevent duplicate UI implementations as we have to do everything in backbone/marionette first and then in Vue again:
So I would suggest to discuss this in our meeting next week.
cc @nextcloud/talk @nextcloud/vue
The text was updated successfully, but these errors were encountered: