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
{{ message }}
This repository has been archived by the owner on Mar 15, 2020. It is now read-only.
As discussed, the vosbox-web interface needs to be modified for usability, and then integrated with the brand when ready.
First of all we need to decide on the issues with the current interface, if any.
To work on the interface, this repository can be forked, allowing changes that can be integrated back into this main repository.
Also, do you all think that it is a good idea to separate vosbox-web from vosbox-api into a separate repository? It makes sense for me, considering vosbox-web is an independent client such as vosbox-iphone.
We can still offer integrated bundled downloads if necessary.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As discussed, the vosbox-web interface needs to be modified for usability, and then integrated with the brand when ready.
First of all we need to decide on the issues with the current interface, if any.
To work on the interface, this repository can be forked, allowing changes that can be integrated back into this main repository.
Also, do you all think that it is a good idea to separate vosbox-web from vosbox-api into a separate repository? It makes sense for me, considering vosbox-web is an independent client such as vosbox-iphone.
We can still offer integrated bundled downloads if necessary.
The text was updated successfully, but these errors were encountered: