Smiley API

Mauro Sérgio Ferreira Brasil mauro.brasil at tqi.com.br
Wed Dec 5 12:12:38 EST 2007


Hi!

The "Smiley API" purpouse is to provide the necessary means so libpurple 
core and protocol plugins can perform CRUD like operations with custom 
smileys.
And it is designed to be an independent entity (different of prior patch 
that was bound to account).

Libpurple's core and protocol plugins (like MSN, Jabber, Yahoo, and so 
on) can use this "Smiley API" to add new custom smileys, and/or delete, 
find or update the stored ones.
The "Smiley API" will be a global repository of custom smileys.

Regarding your question about the sending and receiving of custom 
smileys feature, firstly I need to say that it has nothing to do with 
"Smiley API".
Protocols that support this feature for sure will use "Smiley API", and 
that is all regarding this API.

Now, getting back to sending and receiving custom smiley feature:

1- First of all, the protocol must support the feature;
2- The necessary implementation must be done on libpurple's respective 
protocol plugin so it supports the feature too.

Without that, you won't have the feature working, even having the 
"Smiley API" fully operational on libpurple.
Resuming, the "Smiley API" is a tool to be used inside libpurple core 
and protocol plugins when handling sending and receiving custom smileys 
protocol feature.

I hope this explanation cleared out your questions.

Best regards!!!



Larry Fish wrote:
> is it possible to have custom smiles works for all protocols if the 
> other user is using pidgin as well?
> - Show quoted text -
>
>
> On Dec 5, 2007 6:15 AM, Mauro Sérgio Ferreira Brasil < 
> mauro.brasil at tqi.com.br <mailto:mauro.brasil at tqi.com.br>> wrote:
>
>     Hello there!!!
>
>     Considering that the message below wasn't answered by anyone, I
>     suggest that we keep the effort as it is.
>
>     The peaces are on the move, and the direction is to make the
>     custom smiley infraestructure to work on a "per-profile" basis.
>     But for now, the implementation will recognize only the main
>     (global) profile so the management of profiles could be added on
>     future releases.
>
>     Resuming, the feature will work like this:
>
>     Custom smileys will be handled by the new "Smiley API" suggested
>     by Jorge and will be stored on a global folder, meaning that they
>     will be shared by all protocols (and associated accounts) that
>     want to use them.
>     If the user adds a custom smiley, it will be available for all MSN
>     accounts he/she have.
>     In the moment the feature of sending and receiving custom smileys
>     become available for a new protocol, all the custom smileys
>     already stored will be automatically available to all accounts of
>     this protocol.
>
>     That's the main idea.
>
>     Any comments and suggestions will be welcome (hum... I don't know
>     whether the word "welcome" could be used like this, but... ).
>
>     Best regards!!!
>
>
>
>
>     Jorge Villaseñor wrote:
>>     Hi, I'm the one working on #1187 I'm on vacations so I will start
>>     working on it again but now with Mauro's help.
>>
>>     We was talking and we have some questions to you
>>     1) The custom emoticons should be managed per-account, per-service or
>>     per-profile?
>>     We think that the better way to manage it is per-service or
>>     per-profile but since purple is based on a per-account way....
>>
>>     2) As we have read the patch, we find that it's to big and adds a
>>     complete feature so, it make sense to add a Smiley API in a
>>     libpurple/smiley.[ch] and use it.
>>     Actually the smileys are associated to an account being added a glist
>>     to the PurpleAccount structure, but may be it's better to have the
>>     smileys independent to the accounts and only at the end link the
>>     account (depending on the answer to 1)
>>
>>     What do you think?
>>
>>     _______________________________________________
>>     Devel mailing list
>>     Devel at pidgin.im <mailto:Devel at pidgin.im>
>>     http://pidgin.im/cgi-bin/mailman/listinfo/devel
>>
>>
>>       
>
>     -- 
>     __At.,                                                                                                                            
>        _
>      
>     *Technology and Quality on Information*
>     Mauro Sérgio Ferreira Brasil
>     Coordenador de Projetos e Analista de Sistemas
>     + mauro.brasil at tqi.com.br <mailto:@tqi.com.br>
>     : www.tqi.com.br <http://www.tqi.com.br>
>     ( + 55 (34)3291-1700
>     ( + 55 (34)9971-2572
>
>
>     _______________________________________________
>     Devel mailing list
>     Devel at pidgin.im <mailto:Devel at pidgin.im>
>     http://pidgin.im/cgi-bin/mailman/listinfo/devel
>     <http://pidgin.im/cgi-bin/mailman/listinfo/devel>
>
>

-- 
__At.,                                                                                                                             
   _
 
*Technology and Quality on Information*
Mauro Sérgio Ferreira Brasil
Coordenador de Projetos e Analista de Sistemas
+ mauro.brasil at tqi.com.br <mailto:@tqi.com.br>
: www.tqi.com.br <http://www.tqi.com.br>
( + 55 (34)3291-1700
( + 55 (34)9971-2572

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pidgin.im/pipermail/devel/attachments/20071205/a30cd282/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1705 bytes
Desc: not available
URL: <http://pidgin.im/pipermail/devel/attachments/20071205/a30cd282/attachment.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CMMI_2.jpg
Type: image/jpeg
Size: 1705 bytes
Desc: not available
URL: <http://pidgin.im/pipermail/devel/attachments/20071205/a30cd282/attachment-0002.jpg>


More information about the Devel mailing list