[Telepathy] exposing dialog interfaces to empathy from the protocol end

[Shannon Black]

Makes sense. In fact I may have a solution. The resulting dialog from
libpurple for the mxit protocol requires 3 fields. Captcha, Country
and something else string based. I was thinking of creating a mxit.ui
to accomodate the none captcha settings *prior* to the connection.
Upon connection it will ask for the authentication.

BUT, i also think for the sake of other protocols requiring different
options upon set up. An example would be perhaps prior to
authentification a proprietory protocol asks for EULA. Perhaps
exposing dialog details would be future proof. By Dialog details I
don't mean the actual UI but rather more in the lines of what
telepathy-haze already does. i.e when empathy asks to look at a
protocol, say facebook... it queries for TpConnection params. the
params have an array in param->dbus_signature[] which describes if its
a 's' (string field), [i,y',l, etc ] (integer fields), etc etc .. This
means that the protocol can dictate what fields can be displayed, just
not on the UI level.

What are your preferences?

Shannon Black



On Tue, Oct 18, 2011 at 12:16 AM, Danielle Madeley
<danielle.madeley at collabora.co.uk> wrote:
> On Tue, 2011-10-18 at 09:07 +1100, Danielle Madeley wrote:
>
>> Unfortunately you can't just pass the dialogs through as UI, it breaks a
>> whole bunch of things about Telepathy.
>
> Having now seen your conversation on IRC:
>
> To expose captchas, say one required to make aconnection. You could do
> it using an authentication channel (Chan.Type.ServerAuthentication), it
> may even be possible to dovetail the mode into Chan.I.SASLAuthentication
> using a pseudo mechanism like X-TELEPATHY-CAPTCHA.
>
> --
> Danielle Madeley
> Software Developer, Collabora Ltd.                  Melbourne, Australia
>
> www.collabora.co.uk
>
>