New PurplePrefType: string with hint list

[Tomasz Wasilczyk]

> This seems like a reasonable and valuable addition to me in general.
> Some things to think about:
>
>  * In prefs.xml, you probably want to store only inactive entries that
>    the *user* has added; inactive entries added by the prpl at
>    initialization should be suppressed.

Actually, I was rather thinking of storing only selected value. In
that case, prpl could decide, if it wants a newly entered value to be
stored or not (after validation). And it would store these values by
itself, in i.e. in purple_prefs_*.

>  * In some cases, we may have been able to take advantage of this in
>    the past in ways that we don't necessarily *want* to; for example,
>    there have been multiple possible auth servers for OSCAR
>    (particularly for ICQ, I think?), but we generally don't want users
>    using anything but the default, so we wouldn't want to provide
>    alternation.  We need to think hard about what prefs get this sort
>    of treatment -- the GG server makes me suspicious, for example.

I'm not 100% sure, if i understand correctly. Gadu-Gadu have a lot of
connection servers, this list is very mutable (and not published
entirely anywhere, i think). I would like to save successfully
connected server addresses to hint-list with allowing user to find a
working server by himself, i.e. here [1]. This is mainly for case,
when hub server goes down.

>  * Your point re: XMPP ports may fall into the point above, but if it
>    does not, is this an argument for an int selector as well as a
>    string selector?

I'm again not completely sure, what are you asking about. Actually, an
int selector would be better for port numbers than proposed solution.

Tomek

[1] http://www.kadu.im/monitor/