Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#4271 closed enhancement (fixed)

log viewer : contacts column : light blue background and 1px separation line

Reported by: sam Owned by: evands
Milestone: Adium X 1.0 Component: Adium UI
Version: Severity: normal
Keywords: Cc:
Patch Status:


The log viewer is great now :) But it can look much better too ;) I love the look of NetNewsWire 2.1... what if the contacts column looked like that ?

  • light blue background
  • 1px separation line (dragging this separator can resize the column of course)
  • selected contact is not just plain blue, it's more like a faded blue (see the picture below)

Change History (9)

comment:1 Changed 14 years ago by Evan Schoenberg

Milestone: Adium X 1.1Adium X 1.0
Owner: changed from nobody to Evan Schoenberg
Status: newassigned

comment:2 Changed 14 years ago by Evan Schoenberg

Resolution: fixed
Status: assignedclosed

(In [16272]) The contacts source list in the log viewer now:

  • Has a light blue background, like
  • Has a smaller divider
  • Has a gradient selection highlight

Closes #4271

comment:3 Changed 14 years ago by Ryan Govostes

I think the new UI is an improvement but still needs some work. I'm basing these off of the interface. Colloquy does a good job in mimicking Mail's UI; its source might be helpful in replicating some of these.

  • Nothing below the toolbar should have a focus ring
  • Separator between contact list (left) and the rest (right) should be 0px (and still be resizable)
  • Selection gradient should be lighter - and may depend on appearance settings
  • Multiple selections shouldn't make a continuous gradient. Each selected item should have the same gradient, with a 1 px unhighlighted region between them.
  • Separator between log list (top) and content (bottom) should be the weird white gradient one
  • Move "# of logs" bar to the bottom (#4275)
  • Maybe use a pie-shaped progress bar like Xcode to indicate progress of log indexing

This might be worth another ticket, but also

  • "Opening logs... - Indexing 0 of 1" message shouldn't have ellipses, and shouldn't start counting at 0

comment:4 Changed 14 years ago by Evan Schoenberg

  • What's up with not wanting a focus ring? The source list isn't selectable - can't be navigated with the keyboard - which I think is poor.
  • Selection gradient follows the system appearance settings
  • Continuous gradient looks much nicer than the separate gradients, in my opinion.

Please, one item per ticket, and one ticket per item.

comment:5 Changed 14 years ago by Paul Wilde

I'm going to agree with rgovostes on this one. The Log Viewer could use quite a few improvements still.

I'm also not a fan of the focus rings, they look ugly imo. Very distracting, and doesn't offer anything really.

Attached is a mockup of how I think the Log Viewer *should* be.

comment:6 Changed 14 years ago by Paul Wilde

Damn maximum limit thing. Hosted it instead.

comment:7 Changed 14 years ago by Evan Schoenberg

That's pretty, Paul, I like. The status bar at the bottom looks a lot better; the current one is really just there because it was 0 effort to leave it when revamping the old log viewer - my original mockup of the new one put the status there, too.

I wonder if there's a standard widget for that drag-to-resize header/footer bar... I don't think I've seen it anywhere, although Apple uses it in multiple places.

comment:8 Changed 14 years ago by sam

that's very good :) i hope you can make it for 1.0 :)

comment:9 Changed 14 years ago by Evan Schoenberg

(In [16408]) Along with [16407], in which I accidentally committed a number of log viewer files, implemented Paul's mockup from #4271 for changes to the log viewer. In the process, also made several changes mentioned by rgovostes in that ticket. Focus rings are removed, separator size is set to 0, a source list resizer (the first open source implementation of one of which I'm aware) is implemented, and progress information is improved, including 'indexing 1 of 1' rather than 'indexing 0 of 1'. Refs #4271.

Note: See TracTickets for help on using tickets.