Send custom emoticon patch and utillitary methods...

[Mauro Sérgio Ferreira Brasil]

Hi guys!!!

I agree with you that we should choose two possibilities here:

1- Work with a different libpurple root path for our application using 
the util method "purple_util_set_user_dir" to change the place our 
libpurple instance access it's persistent data (I mean, work with a 
different ".purple" folder location);
*** Please let me know whether this method "purple_util_set_user_dir" is 
not intended to do this.

2- Accept that we will work with the same ".purple" folder used by 
Pidgin, and implement a logic similar to that used on the Pidgin's 
interface part of the patch to manage the smileys inside the graphic 
user interface of our application;

Unfortunately we were not able at that moment to follow any of these 
options, and the faster solution to our problem here was to create this 
configuration, so the Pidgin and our application could work with 
different custom emoticon configuration paths (by configuration I mean 
"smileys.xml" configuration file and the persisted custom emoticon images).

Now the question I make to you is:

Does you guys see any problems or do you feel uncomfortable on any way 
with this implementation ?

Because if a problem exists, we need to decide now to make the necessary 
changes, and maybe I can convince our customer to make the necessary 
changes on our application and eliminate this configuration from "Smiley 
API".
I say that, because I have just provided Jorge with the patch to this 
implementation, but warned him to wait until the end of our discussion 
to apply this patch.

Please let me know what you think about this, so we can get this done as 
fast as possible.

Thank's and best regards,
Mauro.




Richard Laager wrote:
> On Fri, 2008-02-15 at 16:45 -0200, Mauro Sérgio Ferreira Brasil wrote:
>   
>> Could I ask you the problem on provide such configuration option ?
>>     
>
> Sure. Nobody has justified its existence. ;)
>
>   
>> And besides that, I think it should not be desirable anyway that two
>> applications share the same "Smiley API" configuration and image
>> files.
>>     
>
> Why not? More to the point, why would you want to share the other stuff
> that's in .purple and not this "Smiley API" stuff that you talk about?
> On that point, what exactly is this data? Is it the custom smiley image
> files and emoticon string to image mappings, or something else?
>
> Richard
>   

-- 
__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/20080218/76961a05/attachment.html>
-------------- 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/20080218/76961a05/attachment-0002.jpg>