|
FastMail Forum All posts relating to FastMail.FM should go here: suggestions, comments, requests for help, complaints, technical issues etc. |
|
Thread Tools |
19 Jun 2017, 08:44 AM | #1 | |||||||
Member
Join Date: May 2010
Posts: 47
|
Style sheet "Concise" (in Classic)
I may be in the minority here, but I like the "Concise" style sheet in Classic.
To cut to the chase: If anyone would like to see a "Concise" theme in the new interface, I suggest you submit a support ticket. MORE DETAILS I've been using FastMail Classic with "Concise" style sheet for several years (previously using the Classic, no-Ajax UI in Yahoo Mail Plus), and it has worked well for me. I like the color scheme and overall layout, and, being a "road warrior", I use an ultraportable with limited screen space and find that "Concise" works well in a constrained space. In May, I submitted my suggestion to add "Concise" to the new interface via the "classicfeedback" address noted in the Transition Guide (linked from the Classic login page). I didn't get a response, so I submitted a support ticket in June. The response to that says that there's not much demand for the Concise theme, and input from customers factors into prioritization of requests. So, please submit a support ticket if you're interested in the Concise theme. As someone said: Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
|
|||||||
19 Jun 2017, 09:08 AM | #2 |
The "e" in e-mail
Join Date: Jul 2002
Location: VK4
Posts: 3,029
|
It would be much nicer if they retained the classic UI
It's pointless doing a support ticket as all you will get the same script reply that everyone else gets. |
19 Jun 2017, 09:12 AM | #3 |
Essential Contributor
Join Date: Dec 2002
Location: UK and Cyprus
Posts: 399
|
The Large Font Theme in the new interface addressed the issues I raised about using Fastmail on a small screen.
There may, however, be value in reintroducing a wider range of styles in the new interface. |
19 Jun 2017, 11:18 AM | #4 | |||
Member
Join Date: May 2010
Posts: 47
|
I agree, as I'm not a fan of heavy JavaScript and related things (like Ajax). For one thing, you're less likely to get meaningful and timely error messages when the connection is flaky (as you would when using a non-JS interface).
Quote:
Quote:
Quote:
One thing that would help is if users could choose the colors in any of the themes. |
|||
19 Jun 2017, 02:09 PM | #5 | |
Essential Contributor
Join Date: Dec 2002
Location: UK and Cyprus
Posts: 399
|
Quote:
Last edited by labarum : 19 Jun 2017 at 02:27 PM. |
|
19 Jun 2017, 03:19 PM | #6 |
The "e" in e-mail
Join Date: May 2003
Location: mostly in Thailand
Posts: 3,095
|
While I sympathize, I can imagine that in the current interface this could not be solved simply with CSS changes, but would involve Javascript changes and also changes in the backend. This would be doable, of course, but needs the developers to agree it is important. If my sense of what is involved is correct, this is a fair bit of work.
|
19 Jun 2017, 04:01 PM | #7 | ||
Member
Join Date: May 2010
Posts: 47
|
Quote:
However, there's an issue with how headers are displayed. I need to see the "To:" header of each message, because I use a lot of aliases and I need to see what alias each message came in on. In "Large Font" I have to click "Show details", meaning an extra action for every single message I read (which is a lot). Because of this, I'll probably wind up using the so-called "Classic" theme, which displays the headers by default. In that case, I won't be using browser zoom because the font would be too tiny. Sigh... so much for "Concise". There's an additional issue that the new interface either shows too much header info or not enough. As I mentioned above, the terse version doesn't show me the "To:" address (and I also want to see the full "Date:" header), while the verbose version (via "Show details", or by using the so-called "Classic" theme) takes up extra screen real estate by displaying the Subject twice, the From address twice, the recipient's "real name" twice, and also the Size (which I don't need to see except on the message list page). The classic "Concise" theme displayed the header information exactly as it should, with everything I need to see, and no redundancy. And that's another reason why I find the classic "Concise" theme superior to anything in the new interface. I really don't understand why they'd allow problems like the above to crop up when those problems had already been solved in the previous implementation. Having worked in the software industry, and knowing the situation with employee turnover, I can only guess that the designers of classic left the company and took with them their rationale for the various design decisions they made. Quote:
Bottom line, for the various reasons stated above, I seem to have would up in the camp of those who see the transition out of classic as "one step forward, two steps back." |
||