Well, there have been a number of features rounded down into this upcoming and released version. You may be wondering what happened to v2.3.1 or v2.3.2. They were rollover versions in hard beta so they pretty much got the skip.
What does this version introduce?
It was requested that the System Response Widget go away when not in use. Thanks @Vustom for the suggestion! It was using up real estate on the screen and in some cases was a little confusing.. a few questions as to "What is that?" made this evidently clear.
Now the system response pops up in an on-demand fashion... saving real-estate and also making the processes clearer. It took revamping the entire subsystem of the packages for installers/uninstallers in regards to plugins, packages and system commands like updateQuickBox.
Another request was to have the system controller and status panels be collapsible. Now, we're happy to announce they are just that. They are collapsed by default, again, saving space and keeping relevancy and attention where it is better owed on the dashboard.
Check it out!
Another big feature added in is the ability to do system updates directly from the dashboard. These are now easily committed with the click of a button. When a new version is introduced, a button will appear informing you there is an update available... click it and have your and eat it too!
UX Update June 09, 2016
I am typically a hater when it comes to scrollbars, I hate them mostly... they are bulky and they tend to kill a golden design. With that said I had been pondering how to include the custom scrollbars (provided by perfect srollbar) on child-elements within the site. Today I spent some time on updating the .js used to handle this as well as pushing some additional UX sexiness. Happy to say, the System Response widget looks 100 times more attractive.
Most things such as installing a package or a plugin will not make use of height dimensions requiring scrollbars, this is a different case however when pulling in updates. Now one can easily scroll horizontally and vertically to review all pulls.
How do we update?
Easy as pie and here is how:
The update process via shell will more than likely show as a blank sequence... don't worry though... it is updating. The update should only take no more than 15 seconds to complete.