Comments on: A simple C++/SDL_net chat server & client rewritten

By: alexoffspring

alexoffspring — Tue, 24 Apr 2012 11:48:48 +0000

Tnx for the answer. Or probably storing temporarily the input using a simple scanf can be a nice solution.

I was wondering if SDL can be used to create a socket to a client passing through a proxy. I did not find any documentation about it yet.

By: r3dux

r3dux — Sun, 22 Apr 2012 05:15:06 +0000

Hmm, you’ll prolly need to look for the ASCII code for backspace (8) in the getUserInput function and remove the last character from the message when you detect it.

There’s also the issue of moving the text carat back one character, which you could get around by re-displaying the prompt each time, but that’s not very elegant. It’s all do-able, it just might be a little fiddly to nail it with a nice cross-platform solution.

By: alexoffspring

alexoffspring — Fri, 20 Apr 2012 15:27:49 +0000

Nice job.
I downloaded it and i’m actually enjoying ‘customizing’ it

I have some problems when using BACKSPACE. Any idea for solving it?

Tnx
alex

By: r3dux

r3dux — Mon, 27 Feb 2012 10:22:57 +0000

Oops! My bad – fixed!

Glad you like =D

By: FOX51

FOX51 — Mon, 27 Feb 2012 02:12:28 +0000

Nice work man, really good job, only one thing, can you put the windows download link corrected? and thanks for sharing

By: r3dux

r3dux — Fri, 24 Feb 2012 06:16:10 +0000

Cheers, Reilly

By: reilly davis

reilly davis — Fri, 24 Feb 2012 06:04:15 +0000

wow nice work there al

By: Su

Su — Sat, 26 Nov 2011 14:36:30 +0000

for this time the coding is a bit different and weird( for me) because the ss and cs but the function is the same with the previous one. what type of coding u use to make it very simple..

you are so nice sir.. however i’ve finish my presentation and of course using your code…the presentation went smoothly.. thanks a lot.. i will visit u more often to learn about coding and will never forget what u have teach me… i will remember u always..

By: shetboy

shetboy — Fri, 25 Nov 2011 13:48:21 +0000

Yes, absolutely. The term I believe you are scratching for is loosely coupled code. It takes longer to design and write code adhering to these principles, but the benefits are massive time savings down the line in the current project and/or future projects.

By: r3dux

r3dux — Fri, 25 Nov 2011 11:19:42 +0000

Hehe – I love that comic =D

Thanks for your kind comments – I worked really hard on it (did you know you can’t define structs in headers? I didn’t!). Just hope it makes socket programming more do-able for my students, and maybe anyone else trying to knock together some socket stuff!

Really, the socket server has gone up from 250 to around 500 lines, and the client from 313 to around 600 lines. But I guess the payback comes when you can use it to actually do something useful in less than 100 lines of code, and modify and extend it with ease now that the mains are now almost purely “business logic”.

Really happy with it =D