[Psi-Devel] Feature request: Handling of im: URIs
textshell-I1QKlO at neutronstar.dyndns.org
textshell-I1QKlO at neutronstar.dyndns.org
Fri Nov 9 08:03:18 PST 2007
On Fri, Nov 09, 2007 at 04:17:05PM +0200, Norman Rasmussen wrote:
> On Nov 9, 2007 3:59 PM, Kevin Smith <kevin at kismith.co.uk> wrote:
> > I may have misunderstood what you wanted. I thought you meant handling
> > of xmpp: links within Psi, whereas now I guess you meant using Psi as
> > the default handler for system xmpp: links. The latter is Textshell's
> > baby in the IPC stuff. If you're interested in the former, it
> > shouldn't be too hard.
>
> Mmm, personally if getting xmpp links to work correctly with-in Psi is
> easy, then I think we should go for that.
That's mainly the missing part of the current code. And it's not quite that
easy because we need to do it in an secure and unobstrusiv way.
And i didn't see any xmpp / im uris send via xhtml-im or normal chat
messages yet, so i think it's not really higher priority than gettig the
ipc and this work.
> (by that I mean
> open-new-chat window to jid and/or add jid to roster and/or join muc
> by clicking a link from an x-html message - or right click choose
> option from auto-htmlized plain text message)
If you like to work on this and you will keep all the small problems
(privacy, usable ui, authority component, multiple accouts, etc) in mind
that's a nicely isolated task. I even got some code, but it's currently not
in a state where i feel it's safe or sane enough, but i didn't review that
code deeply enough to really know much is already done...
i guess we could do some specing out of this in the muc some time...
>
> Once the xmpp handler is complete within Psi the external xmpp uri
> handler can just hook-in to that 'for free'.
sure, ipc and actual handling of the data passed by ipc are nicely
orthognal tasks in this case.
- Martin
More information about the Psi-Devel
mailing list