protocol_data field for PurpleAccount

[Felix Kerekes]

On Mon, Jul 20, 2009 at 6:53 PM, Mark Doliner <mark at kingant.net> wrote:

> On Mon, Jul 20, 2009 at 8:04 AM, Felix Kerekes<sttwister at gmail.com> wrote:
> > Hey,
> >
> > I would like to add a protocol_data field for PurpleAccount. I need this
> in
> > order to sync Pidgin with Telepathy's AccountManager implementation (that
> > would be Mission Control 5). So when Pidgin starts, I'll make sure the
> > account's parameters are up to date with AccountManager, and then sync
> again
> > on exit if Pidgin changed anything (as a side note, a signal notifying
> that
> > account parameters have changed would be useful too).
> >
> > Is there any problem with this kind of change? Or perhaps there already
> is a
> > way of doing this that I don't know of.
>
> It seems ok to me... would the information need to be saved in
> accounts.xml?  Or would it be reinitialized each time Pidgin is
> started?  Was there something about
> purple_account_set_[string|int|bool] that makes them inadequate?
>
> -Mark
>

Actually the purple_account_set_* family could do the job. At first I
thought it's not possible because it will show up in the accounts
preferences window, but I found out that this is not the case. So I guess
there is no need for the protocol_data field after all, heh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pidgin.im/pipermail/devel/attachments/20090720/7c74b498/attachment-0001.html>