Opened 13 years ago

Last modified 9 years ago

#43 new Enhancement

Text Encoding Menu

Reported by: anonymous Owned by: timothy
Component: Colloquy (Mac) Version: 2.2 (Mac)
Severity: Minor Keywords: text encoding menu
Cc:

Description

There are three things that Colloquy should probably do to make life easier for its users.

1) Allow changing of the character encoding via a menu. A lot of people, myself included, don't like buttons and whatnot. This would also mesh nicely with Safari's View -> Text Encoding menu.

2) Have the scroll bar on the right side of the chat view already present (although greyed-out) when the window is opened. It's just a little strange to see all the text shift around when the chat window finally fills up.

3) Get rid of the cmd-right arrow and cmd-left arrow bindings for switching between tabs. In practically every app where you can enter text, those actions move the cursor to the beginning or end of the line and this behavior is inconsistent. Perhaps shift-cmd-arrow? Definitely not option-arrow. Given the limited space in which one types on IRC, cmd-up and cmd-down might even be appropriate.

Change History (7)

comment:1 Changed 13 years ago by graphite

command up and down allow me to go the beginning of the line in tab view and change the channel in drawer view.

i also brought this up, but i can't really come up with a better solution over all.

comment:2 Changed 13 years ago by eridius

Out of the given options, cmd-shift-arrow is best, I think, and next/prev active panel can be cmd-shift-opt-arrow. However, I don't know if that's the best solution overall, or just the best solution given so far

And no, cmd-up/down wouldn't make sense to me in a tabbed window.

comment:3 Changed 13 years ago by fs@…

The problem with cmd-shift-right and cmd-shift-left is that those key bindings are used to select text from the current position to the beginning or end of line, which would then be impossible. Safari had this problem too, before in 1.3 and 2.0 they changed this behavior so that you won't be able to change tabs anymore if the cursor is in a text field.

Better key bindings would be cmd-alt-right and cmd-alt-left, I think. The "select next/previous active panel" could then be changed to cmd-alt-shift-right and cmd-alt-shift-left.

comment:4 Changed 12 years ago by Rinoa

  • Summary changed from 3 quick UI recommendations to Text Encoding Menu
  • Version changed from 2.0 (2D9) to 2.0 (2D16)

The only one that might happen is the Text Encoding menu.

comment:5 Changed 12 years ago by Gary King

  • priority changed from normal to high
  • Severity changed from normal to trivial
  • Type changed from enhancement to defect
  • Version changed from 2.0 (2D16) to Latest Nightly

I think the key bindings for moving between channels in Tab mode should also be changed.

comment:6 Changed 12 years ago by akempgen

  • Keywords text encoding menu added
  • priority changed from high to low
  • Severity changed from trivial to minor
  • Type changed from defect to enhancement

my personal opinion is, that the cmd key should absolutely not be used to move the cursor in text fields, that change in safari is still really annoying and not very apple like, therefore i think we can keep cmd-left/right and cmd-up/down...

and since this ticket is now only about the text encoding menu, i'll switch it back to enhancement.

comment:7 Changed 9 years ago by Rinoa

  • milestone set to Colloquy 2.3
Note: See TracTickets for help on using tickets.