[OTR-dev] Pidgin plugin development and GUI look
Ian Goldberg
ian at cypherpunks.ca
Tue May 27 16:24:11 EDT 2008
On Tue, May 27, 2008 at 10:14:38PM +0200, hcat at gmx.net wrote:
> > I wanted at least some help text that doesn't entail going to the web.
> > You're suggesting just having "What's this?" open the HTML widget
> > directly, with the current first-level text as its first paragraph?
>
> I didn't realize that it embeds a HTML widget. I just don't see the
> need for two expanders here, if a user really wants some help text
> he/she will most likely open the second expander as well, just to see
> what's written there.
I can see about making this change. Not today, though.
> I just ran a few more tests with different GTK themes and engines and
> it looks like most are affected. Only the very basic ones display
> "correctly"... Not sure if this is a GTK or engine bug though.
In any event, I'm pretty sure it's nothing we can fix.
> I understand this now, but I take it for a bad sign that I was not
> able to get the meaning myself. But indeed not easy to solve...
But even if you don't understand why it's there, it's at worst
a bit redundant.
> > We left the button available for people who want something like this.
> > Do you think this is vitally important? (Do most people leave that
> > toolbar visible at all?)
> I didn't know the toolbar can be disabled... IMHO the old button takes
> a way too much space. Integrating the OTR status into the toolbar
> (like http://blog.pesa.se/2007/09/25/goodbye-big-bloated-otr-button/)
> doesn't change the pidgin UI too much but still shows the OTR status
> very nicely.
Yes, I totally agree. We just need (a) to find a way to do it that
still allows for multiple conversations, and (b) someone to actually do
it once we figure out what ought to be done.
- Ian
More information about the OTR-dev
mailing list