On Wednesday 14 May 2003 14:41, Robin wrote:
Welcome to the two of us, hehe :-)
this must be the smallest mailing list I've ever been subscribed to, but I
suppose it makes sense to have these discussions in public, so it's archived
on the sourceforge site, and you or others can draw on the wisdom that is
going to be collected on this very list ;-)
> > [Tim wrote earlier:]
> >I'll think of some things that need to be done in the
> >JavaGUI, and post them to the mailing list later or
> >tomorrow, with as much detail as I can think of,
> >so that you have something to start experimenting with.
>
> Thanks, what would be useful is a small list (hints) on
> what had to be changed in gtk-gui to support the 0.47 core
> versions. Maybe it won't be too difficult to add this
> support, isn't it ?
well, thing is that I don't have a very good memory, and that I usually keep
adjusting the GUI to the current core cvs versions. Sometimes I don't even
know when a new core comes out, so it's hard for me to pin down the exact
changes that were necessary. Also, ed2k-gtk-gui has had overnet support for a
while, so that might have something to do with it too.
As I said, I'll think of things (and check the ed2k-gtk-gui source code) that
I know need to be taken into account.
> I'm not sure, but if i'm not wrong, the Controller was
> working with the 0.47 core, and after upgrading to 0.48,
> it stops working. I tried to clean the temp directory and
> to relaunch the 0.47, and this didn't work anymore. (it could
> be between 0.46 and 0.47, and it could be wrong, I don't
> remember very well).
>
> So, any hint is welcome, if you don't have the time, I'll
> inquire by myself...ah, just a thing that could help me to
> start:
> the first thing with the new core is that te
> controller doesn't see that the core is connected to a server
> thus prevent it to launche a search, do you remember if this
> was the same thing with the gtk-gui, and what has to be
> changed?
ah, yes. I struggled with that as well, until someone else solved this. The
eDonkey2000 core does not send an initial 'connected to' gui-core protocol
message to the GUI when the GUI connects and the core is already connected to
a server.
However, it sends a normal 'status message' message with a text line that goes
like this:
Connected to: <IP>
Apparently it always sends an IP even if it has the server name. I'm not sure
if that is a space between the ':' and the IP or a tab, but that should be
easy to figure out.
So that should solve this problem - the GUI just needs to parse the status
message protocol messages (CORE_STATUS_MSG, msg 180 decimal) for that string
to know whether the core is connected or not. :-)
More to come...
Cheers
-Tim
|
