This only makes sense if you have never, ever fleeted or plan to fleet anything above the care-iest bear-iest PVE content in your life (or fleet at all). This is completely and totally impractical in any way, shape, or form.
This has been proposed before and MIGHT have some merit, namely with regards to detaching local and minimizing local chat but keeping Local member list open. The detached member list would need to be titled so we know what the associated chat box is. There are issues associated with the idea but overall it is somewhat feasible, though in practice is really only has one use case (Local monitoring, where you make the window as narrow as possible if you don’t care about the chat contents itself, even though you should because intel is key and you’d be surprised what you can learn from reading chat).
The scroll bar isn’t wide and it’s inside rather than outside the window, so this is purely cosmetic and doesn’t clutter anything
This only makes sense if you have never, ever fleeted or plan to fleet anything above the care-iest bear-iest PVE content in your life (or fleet at all). This is completely and totally impractical in any way, shape, or form.
You misread. This is why I highlighted the “set per channel” line.
I can set the fleet window exempt. And set all 10 intel windows to display only the most recent information.
Lastly, mac OS lead the UI innovation in computers - your prejudice actually makes a case to adopt even more of their ideas.
Wrong. While Apple has advanced Human-Computer Interaction in many ways, the reality is that MacOS is full of grauitous vanity that has zero functional value. It’s all about looking pretty but not increasing throughput. So much of the UI/UX slows you down compared to more practical, less glamourous, more spreadsheet-esque alternatives.
I am biased toward efficiency, throughput, and screen economy.
Window transparency is already a feature anyway. We don’t need additional transparency features. And we certainly don’t need floating chat bubbles.