Cloudron 9.0.15 - upgrade experience / questions
-
Left side bar : wasted space at least 20 pixels after widest entry ?
Status column in My Apps :
icon for login type, icon for update available BUT text for status !!!
Easily changed to green/amber/red/purple? for 4 states
Huge gap between status and final column
This would save enough pixels to avoid hiding logs/terminal/files under an ellipsis.
-
Thanks for feedback. The main goal for v9 is to rewrite the full UI in vuejs. There is over 10 years of UI code with lots of quirks, error handling etc to port over. Mostly, we have paid the most attention to just getting the functionality at par and working. This was already 10 months in the working and at some point we have to get it out and not get hung up on details.
That said, I understand the above information is not interesting or relevant to users, so I don't expect them to empathize with us
All I can say, is that in the next release, we will focus on making the UI better. -
Thanks for feedback. The main goal for v9 is to rewrite the full UI in vuejs. There is over 10 years of UI code with lots of quirks, error handling etc to port over. Mostly, we have paid the most attention to just getting the functionality at par and working. This was already 10 months in the working and at some point we have to get it out and not get hung up on details.
That said, I understand the above information is not interesting or relevant to users, so I don't expect them to empathize with us
All I can say, is that in the next release, we will focus on making the UI better. -
Thanks for the honest feedback, always appreciated!
The left side-bar was commented on by others before. We plan to make that collapsable (on mobile it already is, so this is more about deciding which collapsable style we want to go with) for the next release.
Similar to the quick actions, like opening the logs viewer for an app. Currently, the ... button on all items in the UI collects all actions. With the next release we will look into all those and pick common ones to provide as direct actions on the list items.
-
Thanks for feedback. The main goal for v9 is to rewrite the full UI in vuejs. There is over 10 years of UI code with lots of quirks, error handling etc to port over. Mostly, we have paid the most attention to just getting the functionality at par and working. This was already 10 months in the working and at some point we have to get it out and not get hung up on details.
That said, I understand the above information is not interesting or relevant to users, so I don't expect them to empathize with us
All I can say, is that in the next release, we will focus on making the UI better. -
@fanvyr it's intentional to ship the source code. We want users to have a copy of not just the build but also the source code and the build tools. If one knows how, they can trivially change the source files and build dist. Personally, I would love to see this in all the stuff I use
I like this kind of freedom, to be able to inspect, change and learn.(And also, many of our service providers, simply maintain patches which they apply on top of the release and rebuild. So, it's much easier for them).
-
@fanvyr we also try to keep dependency on shiny upstream projects as low as possible, even if they may offer great benefits, those quickly become a time sink and risk, since those frameworks move fast and often are not aligned with our goals or timeframe (this is not a critique but just different goals).
Also since we are into it for the long run and with self-hosting it is much harder to push out updates for fixes to servers we don't even have access to by design, compared to a "saas git push" style for a quick hotfix, we take different decisions here. We are slowly trying to reduce dependency on npm packages overall also, given the history (leftpad was only the wakeup call). Alone nuxt for example would bring in 737 dependencies from npm. Such amounts are impossible to vet and almost everyone just banks on someone in the community will keep an eye on them...Already choosing vuejs was a tough call.
-
@fanvyr it's intentional to ship the source code. We want users to have a copy of not just the build but also the source code and the build tools. If one knows how, they can trivially change the source files and build dist. Personally, I would love to see this in all the stuff I use
I like this kind of freedom, to be able to inspect, change and learn.(And also, many of our service providers, simply maintain patches which they apply on top of the release and rebuild. So, it's much easier for them).
@girish said in Cloudron 9.0.15 - upgrade experience / questions:
@fanvyr it's intentional to ship the source code. We want users to have a copy of not just the build but also the source code and the build tools. If one knows how, they can trivially change the source files and build dist. Personally, I would love to see this in all the stuff I use
I like this kind of freedom, to be able to inspect, change and learn.Love it. Will play a little around with it.
-
@fanvyr we also try to keep dependency on shiny upstream projects as low as possible, even if they may offer great benefits, those quickly become a time sink and risk, since those frameworks move fast and often are not aligned with our goals or timeframe (this is not a critique but just different goals).
Also since we are into it for the long run and with self-hosting it is much harder to push out updates for fixes to servers we don't even have access to by design, compared to a "saas git push" style for a quick hotfix, we take different decisions here. We are slowly trying to reduce dependency on npm packages overall also, given the history (leftpad was only the wakeup call). Alone nuxt for example would bring in 737 dependencies from npm. Such amounts are impossible to vet and almost everyone just banks on someone in the community will keep an eye on them...Already choosing vuejs was a tough call.
@nebulon very understandable. Thought more from the perspective that you are a more smaller team, it would add faster iterations. And i think nuxt is very much for the long run here, but the argument of dependencies and updates is very valid.. Did you guys consider making the dashboard "pluginable" for theming or even more open-source so others can help? But while writing this i have to admit, that this will also add a lot of work...
Given the current situation i think you guys deliver a great product. Hope you are also here for the long run.Let me know if i can help somehow, beside of late night fix reports ( :
