Feature Request: Adjusting the Admin area - Width.
Feature request sequence: A
Description: It will benefit every admin of the SE software; The admin area is more user friendly after changing to full 100% width. Why only use a fix width of 950px if you have a full screen to work with?
All fields and other data on one line instead of being cropped to the next line. Also the Layout Editor will look much better with a wider list for the widgets. Also the "login as Member" link will show up on the Member Manager page instead of scrolling to the right.
Most of us admin will prefer a wider screen to look at.
This request is: for the layout adjustment of the admin area in total.
At the minute it is only using a "width: 950px" which is way too low as it cripples all columns and data. An examples below you see the 950px.
So all columns in the rows look much better.
Here a sample of Width: 950px
Here a sample of the layout editor, look already better at 1400px width, preferable full 100% if possible. The list of widgets are easier to read, better than the small list at 950px:
Here a sample of the columns messed up at 950px, should be adjusted to full 100% width of the page to suit the columns better:
Yeah I work from a macbook pro and have had this issue a lot (the login not showing, etc). Good idea.
@Donna
I work from a desktop pc with is 1900px wide, but it is not showing everything as the admin is set to 950px wide.
Will you accept this feature request?
I was going to create my own post about the admin panel but thought I would add to this thread instead. With the onset of Responsive Web Technologies, is there any plans to redesign the admin panel? Even if it was closer in line with SE Cloud. There is just too many missed opportunities to manage my sites from my mobile phone because of the antiquated admin panel.
love this request!
This is something we had in the pipeline to update admin panel. We couldn't do it on this release.
My vote is still 'plain vanilla'. Although I see the benefit (even for myself using more recent displays), my 2 primary concerns are:
A. If it's wider, what happens on displays that can't handle the extra data-width? Which leads me into my next concern.
B. Although I asked if it would be Responsive, I take that back because I don't want it to be. There are too many issues with Responsive not displaying well across devices, unless you have a very Responsive, Responsive Theme. But I don't want to risk ADMINcp issues due to its reliance on a Theme - ADMINcp being the backend shouldn't be open to any risks of improperly displaying content. There's a reason in the US that most banks/insurance/etc. firms still have 'old-fashioned' text based apps displaying inside current OSs - and this is one of the reasons. I'd much rather have something that always works for everyone on the majority of devices. I've seen .css issues preventing proper display in ADMINcp and simply don't want to risk that.
My 2 cents is that since multiple columns are useful for much of ADMINcp, that the page be horizontally scrollable (so that if it all fits on a wide display, then great; but if not, everyone else isn't penalized but can still see the data via scrolling). Yes, I don't like having to scroll, but that's safer than some other options, and it may be moot depending on the display width.
Other non-risky suggestions/ideas?
Coming back to your question "Other non-risky suggestions/ideas?" ... the RISK FACTOR = There is NO RISK.
max-width, width, min-width in percentage or a fixed (px) width in the CSS is supported by all main browser.
The RISK-precentage of choosing the wrong data with a smaller viewing area is larger.
I love it when you refer to the Banks, I used to install banking systems, card/encoding printers and banking servers, but our systems where as you said "text" based but will use up the whole viewing area of the screen, not 60% or 70% and with the columns proper presented. Some viewing areas used more than 2 screens to show the data needed. But then we don't use MySQL for banking systems, more like Oracle and DB2 (IBM), IBM mainframes (text based) systems are used for the core banking. Some new banks are using the 'newer' Cassandra and Postgres as database systems with their own main frame terminals.
I don't know how it is possible to compare SE PHP and a Banking System as they are two different types of systems; programming languages/programs/operating systems/databases/security.
For the CSS styling;
So the over all RISK is none as the actual data is not touched, just displayed in a better form.
This request makes sense - while in there I would love to see a deeper more graphic representation of over site health and stats be available as well. Take the site stats area and really make it robust so site owners can see the pulse of their community at a glance and track trends easily. Even have this with draggable widgets so you can create your own unique dashboard. I use AgileCRM and they do a decent job of this but I am sure there are better examples out there
I agree.