[Adium-devl] adiumPurpleRequestFields

[Evan Schoenberg]

With the WebKit-based code already written, especially if some pretty  
CSS can make it blend in a bit better with the OS, using the  
implementation originally written for Smack is a great idea.  A pure  
Cocoa solution would ultimately be smoother, but cost of entry is, as  
described, much higher; perhaps someone will come forward and  
implement it to replace the WebKit based one at some point in the  
future once it's clear how useful this is.

The lack of a requestFields implementation has been a big sore spot  
in our libpurple implementation since Day 1 - so yeah, this would be  
great :)

On Jun 6, 2007, at 10:02 PM, Chris Forsythe wrote:

> Why does it need to be dynamic?

The requestFields has nothing to do with XMPP per sé.  libpurple  
says, "Show an input dialogue with the following information.  Give  
me the results," and then gives a list of things like "textfield with  
message X, radio choices with items A/B/C/D, checkbox labeled foo,  
checkbox labeled bar, table with 9 possible choices" etc.   This is  
used for various XMPP forms extensively but also for password  
changes, showing all buddies awaiting authorization in ICQ, modifying  
account/profile information in Jabber and QQ, and other things which  
don't come to mind offhand.

-Evan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20070606/2a713df7/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20070606/2a713df7/attachment.sig>