libpurple, the nullclient and AIM

View: New views
8 Messages — Rating Filter:   Alert me  

libpurple, the nullclient and AIM

by Jeremy Trammell - Setaris :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello...

I'm trying to build an MFC GUI for libpurple and after finally managing to get it built (using the excellent winpidgin-build-fetcher.sh script) I build the nullclient and ran it.  If I connect to Yahoo, all goes as expected and I can receive messages from others on the network.  If I select AIM, it only makes if through the first two steps of the connection process ("0 of 6 Connecting" and "1 of 6 Username sent").  The pidgin client has no such issue.  I'm running with debug set to TRUE, and other then the file write errors from the default '/dev/null' file path, no further messages are produced.  Any thoughts?

(16:07:12) dnsquery: Performing DNS lookup for login.messaging.aol.com
0 / 6: Connecting
(16:07:12) prefs: /purple/savedstatus/default changed, scheduling save.
(16:07:12) prefs: /purple/savedstatus/isidleaway changed, scheduling save.
(16:07:12) dnsquery: IP resolved for login.messaging.aol.com
(16:07:12) proxy: Attempting connection to 205.188.251.43
(16:07:12) proxy: Connecting to login.messaging.aol.com:5190 with no proxy
(16:07:12) proxy: Connection in progress
(16:07:12) proxy: Connecting to login.messaging.aol.com:5190.
(16:07:12) oscar: connected to FLAP server of type 0x0017
(16:07:12) oscar: Username sent, waiting for response
1 / 6: Username sent
(16:07:14) util: Writing file prefs.xml to directory /dev/null
(16:07:14) util: Error creating directory /dev/null: No such file or directory
(16:07:17) util: Writing file accounts.xml to directory /dev/null
(16:07:17) util: Error creating directory /dev/null: No such file or directory
(16:07:17) util: Writing file blist.xml to directory /dev/null
(16:07:17) util: Error creating directory /dev/null: No such file or directory
(16:07:17) util: Writing file status.xml to directory /dev/null
(16:07:17) util: Error creating directory /dev/null: No such file or directory

--
Jeremy Trammell
Chief Technology Officer
  509 East 87th St. #1W
New York, NY 10128
Setaris Corporation cell +1.518.331.5180
www.setaris.com fax +1.646.786.4370
 
INTELLIGENT SOFTWARE



_______________________________________________
Support@... mailing list
Want to unsubscribe?  Use this link:
http://pidgin.im/cgi-bin/mailman/listinfo/support

Re: libpurple, the nullclient and AIM

by Daniel Atallah-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Mon, Jul 6, 2009 at 4:07 PM, Jeremy Trammell -
Setaris<jeremy.trammell@...> wrote:

> Hello...
>
> I'm trying to build an MFC GUI for libpurple and after finally managing to
> get it built (using the excellent winpidgin-build-fetcher.sh script) I build
> the nullclient and ran it.  If I connect to Yahoo, all goes as expected and
> I can receive messages from others on the network.  If I select AIM, it only
> makes if through the first two steps of the connection process ("0 of 6
> Connecting" and "1 of 6 Username sent").  The pidgin client has no such
> issue.  I'm running with debug set to TRUE, and other then the file write
> errors from the default '/dev/null' file path, no further messages are
> produced.  Any thoughts?

Did you override the default glib io handlers (like is done in
pidgin/gtkeventloop.c)?

-D

_______________________________________________
Support@... mailing list
Want to unsubscribe?  Use this link:
http://pidgin.im/cgi-bin/mailman/listinfo/support

Re: libpurple, the nullclient and AIM

by Jeremy Trammell - Setaris :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I've done a variety of things towards that end, but to keep things simple I am now focusing on simply using the example nullclient code, as provided, which does pass a set of glib io handlers in the PurpleEventLoopUiOps structure.

static PurpleEventLoopUiOps glib_eventloops =
{
    g_timeout_add,
    g_source_remove,
    glib_input_add,
    g_source_remove,
    NULL,
#if GLIB_CHECK_VERSION(2,14,0)
    g_timeout_add_seconds,
#else
    NULL,
#endif

    /* padding */
    NULL,
    NULL,
    NULL
};


Jeremy Trammell
Chief Technology Officer
  509 East 87th St. #1W
New York, NY 10128
Setaris Corporation cell +1.518.331.5180
www.setaris.com fax +1.646.786.4370
 
INTELLIGENT SOFTWARE





From: Daniel Atallah datallah@...
To: Jeremy Trammell - Setaris jeremy.trammell@...
Sent: 07/06/2009 4:11:49 PM -0400
Subject: libpurple, the nullclient and AIM


On Mon, Jul 6, 2009 at 4:07 PM, Jeremy Trammell -
Setarisjeremy.trammell@... wrote:
  
Hello...

I'm trying to build an MFC GUI for libpurple and after finally managing to
get it built (using the excellent winpidgin-build-fetcher.sh script) I build
the nullclient and ran it.  If I connect to Yahoo, all goes as expected and
I can receive messages from others on the network.  If I select AIM, it only
makes if through the first two steps of the connection process ("0 of 6
Connecting" and "1 of 6 Username sent").  The pidgin client has no such
issue.  I'm running with debug set to TRUE, and other then the file write
errors from the default '/dev/null' file path, no further messages are
produced.  Any thoughts?
    

Did you override the default glib io handlers (like is done in
pidgin/gtkeventloop.c)?

-D
  

_______________________________________________
Support@... mailing list
Want to unsubscribe?  Use this link:
http://pidgin.im/cgi-bin/mailman/listinfo/support

Re: libpurple, the nullclient and AIM

by datallah :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message



On Jul 7, 2009, at 0:24, Jeremy Trammell - Setaris <jeremy.trammell@...
 > wrote:

> I've done a variety of things towards that end, but to keep things  
> simple I am now focusing on simply using the example nullclient  
> code, as provided, which does pass a set of glib io handlers in the  
> PurpleEventLoopUiOps structure.
>
> static PurpleEventLoopUiOps glib_eventloops =
> {
>     g_timeout_add,
>     g_source_remove,
>     glib_input_add,
>     g_source_remove,
>     NULL,
> #if GLIB_CHECK_VERSION(2,14,0)
>     g_timeout_add_seconds,
> #else
>     NULL,
> #endif
>
>     /* padding */
>     NULL,
>     NULL,
>     NULL
> };

That isn't going to work like that - g_input_add on glib >= 2.8 runs  
into the problem you're seeing. You need to use the version in  
libpurple (which is based on an older glib version).

-D

_______________________________________________
Support@... mailing list
Want to unsubscribe?  Use this link:
http://pidgin.im/cgi-bin/mailman/listinfo/support

Re: libpurple, the nullclient and AIM

by Jeremy Trammell - Setaris :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

glib_input_add() looks identical to pidgin_input_add() to me.  I'm pretty sure they compile to the same code.


Jeremy Trammell
Chief Technology Officer
  509 East 87th St. #1W
New York, NY 10128
Setaris Corporation cell +1.518.331.5180
www.setaris.com fax +1.646.786.4370
 
INTELLIGENT SOFTWARE





From: Daniel Atallah daniel.atallah@...
To: Jeremy Trammell - Setaris jeremy.trammell@...
Sent: 07/07/2009 1:28:35 AM -0400
Subject: libpurple, the nullclient and AIM




On Jul 7, 2009, at 0:24, Jeremy Trammell - Setaris jeremy.trammell@... wrote:

I've done a variety of things towards that end, but to keep things simple I am now focusing on simply using the example nullclient code, as provided, which does pass a set of glib io handlers in the PurpleEventLoopUiOps structure.

static PurpleEventLoopUiOps glib_eventloops =
{
    g_timeout_add,
    g_source_remove,
    glib_input_add,
    g_source_remove,
    NULL,
#if GLIB_CHECK_VERSION(2,14,0)
    g_timeout_add_seconds,
#else
    NULL,
#endif

    /* padding */
    NULL,
    NULL,
    NULL
};

That isn't going to work like that - g_input_add on glib >= 2.8 runs into the problem you're seeing. You need to use the version in libpurple (which is based on an older glib version).

-D

_______________________________________________
Support@... mailing list
Want to unsubscribe?  Use this link:
http://pidgin.im/cgi-bin/mailman/listinfo/support

Re: libpurple, the nullclient and AIM

by datallah :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Tue, Jul 7, 2009 at 8:06 AM, Jeremy Trammell -
Setaris<jeremy.trammell@...> wrote:
> glib_input_add() looks identical to pidgin_input_add() to me.  I'm pretty
> sure they compile to the same code.

They don't.  Look at the #ifdef _WIN32 stuff.

-D

_______________________________________________
Support@... mailing list
Want to unsubscribe?  Use this link:
http://pidgin.im/cgi-bin/mailman/listinfo/support

Re: libpurple, the nullclient and AIM

by Jeremy Trammell - Setaris :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Oh yes, sorry, I've been playing around with this for so long now I forgot about that!  Yes, I've tried including the WIN32 code with no change in the results (double checked it right now just to be sure).  I still get to "Username sent" and then nothing else for AIM.


Jeremy Trammell
Chief Technology Officer
  509 East 87th St. #1W
New York, NY 10128
Setaris Corporation cell +1.518.331.5180
www.setaris.com fax +1.646.786.4370
 
INTELLIGENT SOFTWARE





From: Daniel Atallah daniel.atallah@...
To: Jeremy Trammell - Setaris jeremy.trammell@...
Sent: 07/07/2009 8:41:37 AM -0400
Subject: libpurple, the nullclient and AIM


On Tue, Jul 7, 2009 at 8:06 AM, Jeremy Trammell -
Setarisjeremy.trammell@... wrote:
  
glib_input_add() looks identical to pidgin_input_add() to me.  I'm pretty
sure they compile to the same code.
    

They don't.  Look at the #ifdef _WIN32 stuff.

-D
  

_______________________________________________
Support@... mailing list
Want to unsubscribe?  Use this link:
http://pidgin.im/cgi-bin/mailman/listinfo/support

Re: libpurple, the nullclient and AIM

by Jeremy Trammell - Setaris :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Oops, after a little more investigation I realized that whenever I imported the WIN32 def'd code, nullclient wasn't actually compiling, so I had never *actually* tested that change!  Once I got it to compile with the win32 specific code in it, AIM worked like a charm.  Thanks so much for your help!  The trick was including win32/win32dep.h, which had declarations for some of the functions used in the win32 specific code.


Jeremy Trammell
Chief Technology Officer
  509 East 87th St. #1W
New York, NY 10128
Setaris Corporation cell +1.518.331.5180
www.setaris.com fax +1.646.786.4370
 
INTELLIGENT SOFTWARE





From: Jeremy Trammell - Setaris jeremy.trammell@...
To: Daniel Atallah daniel.atallah@...
Sent: 07/07/2009 9:14:22 AM -0400
Subject: libpurple, the nullclient and AIM


Oh yes, sorry, I've been playing around with this for so long now I forgot about that!  Yes, I've tried including the WIN32 code with no change in the results (double checked it right now just to be sure).  I still get to "Username sent" and then nothing else for AIM.


Jeremy Trammell
Chief Technology Officer
  509 East 87th St. #1W
New York, NY 10128
Setaris Corporation cell +1.518.331.5180
www.setaris.com fax +1.646.786.4370
 
INTELLIGENT SOFTWARE





From: Daniel Atallah daniel.atallah@...
To: Jeremy Trammell - Setaris jeremy.trammell@...
Sent: 07/07/2009 8:41:37 AM -0400
Subject: libpurple, the nullclient and AIM


On Tue, Jul 7, 2009 at 8:06 AM, Jeremy Trammell -
Setarisjeremy.trammell@... wrote:
  
glib_input_add() looks identical to pidgin_input_add() to me.  I'm pretty
sure they compile to the same code.
    

They don't.  Look at the #ifdef _WIN32 stuff.

-D
  

_______________________________________________ Support@... mailing list Want to unsubscribe? Use this link: http://pidgin.im/cgi-bin/mailman/listinfo/support

_______________________________________________
Support@... mailing list
Want to unsubscribe?  Use this link:
http://pidgin.im/cgi-bin/mailman/listinfo/support