Re: [bme-develop] Development issues

[Simon T. <sim...@ga...>]

> Hello.
> 
> > Hi,
> > 
> > Daniel - is your CVS server just hosted on your machine? I think we 
> > should begin making use of the CVS server at sourceforge. If you do 
> > not 
> > want to check in all the GUI code, maybe we could at least work on 
> > the 
> > network code in CVS, and we can add the GUI files there as we 
> > create 
> > them.
> Yes, the cvs server is just hosted on my machine. I agree with you, 
> it's time to go open source with the project. I don't have a problem 
> importing the whole thing, do you? I prefer to have everything there 
> because we will be working with protocol and GUI, as Mik is doing 
> now. 
> What do you think?

Yes, put all of it on sourceforge if you're happy doing that.

I will probably start the new GUI from scratch, so maybe we could split 
the code into folders:
-Network
-OldGUI
-NewGUI

I think it is quite hard to get stuff deleted from CVS.

Renaming might also be a problem, so I will ask now: Is there any 
reason for the "B" on the start of the network classes? 

> > 
> > Website; Something simple will be fine - php + mySQL would be good 
> > (submit a sf.net service request if you still can't access the DB 
> > Tim), 
> > otherwise plain-vanilla HTML will suffice for a while.
> > 
> > I'm going to start on the GUI soon, however first I would like to 
> > get 
> > to the bottom of the strange network code bugs (me + tim 
> > experienced 
> > the messages not arriving phenomenon the other day). A text log can 
> > be 
> > useful, but it isn't live - I'm going to create a class derived 
> > from 
> > BNetEndpoint that creates a BWindow with a BListView when 
> > constructed, 
> > and any bytes sent or received will be instantly logged to the 
> > BListView. Then if we can arrange a time to test, one of you can 
> > log 
> > in 
> > with the official client and we can play around for a bit, while 
> > I'm 
> > looking at a "live" view of the actual network traffic.
> I like your idea for the live view of network traffic. It will come 
> in 
> handy when debugging the protocol code and file transfers.
> Have you heard complains from other users about this issue (messages 
> not arriving)? I ask because it does not happen to me, but I can't 
> say 
> I use MSN that much now, nor that I have tested it that much, just 
> curious if anyone else has these problems.

I think other people have mentioned it. I just often get the feeling 
that less people reply to me when I'm on BeMSN, I guess that's due to 
messages not arriving.

Also, mik was on BeOS and I was using MSN 6, and we experienced a few 
times where we didn't get each others messages.

I will sign up for a new "testing" passport account, and then we can 
try and arrange a time for some serious network debugging when I've got 
the live view BNetEndpoint working properly.

> > 
> > Simon
> > 
> 
> Thanks,
> Daniel