Making Pidgin small-screen-friendly

Michael Terry michael.terry at canonical.com
Tue Feb 24 14:59:51 EST 2009


OK, to summarize where we are now.

Preferences:
My preferences patches seem like good ideas, but there's some resistance
to the 'Sound Events' being to the right of other columns.  We're not
willing to lose the one-column mode.  I'll re-examine.

Since the patches are split up by page, the other patches can go in, if
y'all like.

Buddy Pounce:
Moving pounce triggers to use more columns helps.  I don't think it goes
far enough.  I'll look into a patch that makes the 'send a message' box
be a popup, showing a preview in the main dialog.

SILC:
Sounds like moving proxy settings into a new tab will help.  I think
that's actually probably enough for SILC.  I'll check.  But long-term,
it would be nice to have a general solution for this, so plugin authors
don't break the dialog.

-mt

On Sat, 2009-02-21 at 15:52 -0500, John Bailey wrote:
> Etan Reisner wrote:
> >> 14. Drop dialog separator, possibly shrink dialog spacing a bit (looks
> >> like it's ending up with a 20 pixel border, but I think you are rightly
> >> intending it to be 12, per HIG).
> > 
> > Yeah, the separator should probably go.
> 
> No "probably" about it, let's lose that ASAP.
> 
> > The largest gain for this dialog could probably be found by making the
> > 'Send a message' action work the way the per-account message stuff works
> > in the Status dialog, that is have the message shown inline and have it
> > pop up a dialog for editing. I'm not sure I like the idea but it would be
> > the most effective single change.
> 
> I have no objections to this, but I would suggest not showing more than a few
> words' worth of text (~25 characters perhaps?).
> 
> > As a side note, I've been thinking about moving the per-account Proxy
> > settings into their own tab (so we would have Basic, Proxy, and Advanced
> > tabs) which would help with the dialog height a little bit for the more
> > "complicated" protocols.
> 
> I was actually going to suggest this, as it seems proxy options aren't a
> particularly good fit on either existing tab.
> 
> > One further thing we could consider regarding the New Buddy Pounce dialog
> > is that we know that quite a lot of people get to the dialog by right
> > clicking an entry in the buddy list and selecting Add Buddy Pounce so
> > perhaps we might want to consider (in that case) not giving people the
> > account dropdown and buddy entry area but rather just making the 'Pounce
> > on Whom' text include that account/buddy information in line.
> > 
> >     -Etan
> 
> I have no problem with this, but I suspect we're going to see some complaints
> about this because if the user wants only Buddy B in Contact A to be pounced on,
> the user has to either use the submenu for the appropriate buddy in the contact
> or expand the contact.  Granted, we have complaints already because pounces
> aren't contact-aware.
> 
> John
> 
-- 
mterry | UI & App Engineer, Canonical Ltd. | +1 781 761 9092
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://pidgin.im/pipermail/devel/attachments/20090224/4b9bb568/attachment.sig>


More information about the Devel mailing list