Hi all,
I decided to release sources to my Qt-based TLCV-compatible client, perhaps it may be useful to someone.
I don't plan to work on it anymore (nothing stellar - in fact I hacked it together rather quickly some time ago).
I'm not sure if I cleaned up the source properly so there may be some unfinished pieces of code that can be safely removed.
The link is here: https://github.com/kmar/livius
License is zlib.
There is one annoying bug (going out of sync) that needs to be fixed (workaround is to simply reconnect in that case).
As for the protocol, I RE-d it so I'm not sure if it's ok to release the sources, but I will risk it. I'm ready to close the sources should there be legal problems,
but I hope Thomas wouldn't mind as he's no longer active...
Have fun.
Oh and the default piece set is ugly but I'm not an artist.
livius sources (a TLCV-compatible client)
Moderator: Ras
-
mar
- Posts: 2671
- Joined: Fri Nov 26, 2010 2:00 pm
- Location: Czech Republic
- Full name: Martin Sedlak
-
aturri
- Posts: 85
- Joined: Wed Dec 30, 2009 11:35 pm
Re: livius sources (a TLCV-compatible client)
Thank you for your work, a pitty you won't keep working on it. I hope it is for good reasons!
-
mar
- Posts: 2671
- Joined: Fri Nov 26, 2010 2:00 pm
- Location: Czech Republic
- Full name: Martin Sedlak
v1.1 update
A minor update that fixes IPv6 issues (thanks to Felix Braun);
precompiled binaries (Windows only - sorry) can be found here: http://www.crabaware.com/livius
Unix users have to build from source (github link still valid)...
- source is now compatible with latest Qt5.6 (removed dependency on QtWebKit); but can still be built with 4.8.4
- fixed some msvc2015 compatibility issues
- removed incoming packet port validation (a bad idea - in fact plain wrong)
precompiled binaries (Windows only - sorry) can be found here: http://www.crabaware.com/livius
Unix users have to build from source (github link still valid)...
- source is now compatible with latest Qt5.6 (removed dependency on QtWebKit); but can still be built with 4.8.4
- fixed some msvc2015 compatibility issues
- removed incoming packet port validation (a bad idea - in fact plain wrong)
-
cdani
- Posts: 2204
- Joined: Sat Jan 18, 2014 10:24 am
- Location: Andorra
Re: livius sources (a TLCV-compatible client)
Very nice!! Thanks! Will be fun to play with the code.
Daniel José -
http://www.andscacs.com
-
Guenther
- Posts: 4718
- Joined: Wed Oct 01, 2008 6:33 am
- Location: Regensburg, Germany
- Full name: Guenther Simon
Re: v1.1 update
Hi Martin,
Is there a way to test it with localhost? Giving 127.0.0.1 and the used
port at least did not work. IN TLCV there is a special swich for local mode.
It looks great BTW.
Guenther
Is there a way to test it with localhost? Giving 127.0.0.1 and the used
port at least did not work. IN TLCV there is a special swich for local mode.
It looks great BTW.
Guenther
-
mar
- Posts: 2671
- Joined: Fri Nov 26, 2010 2:00 pm
- Location: Czech Republic
- Full name: Martin Sedlak
Re: v1.1 update
So much traffic here that I almost missed your message 
I've never tested it with localhost, I assume you plan to broadcast?
Some time ago I made a project communicating via UDP, there are two problems with UDP and localhost:
first you have to enable reuse address flag and I was only able to run server and client on the same machine by using two sockets and two ports per app.
On Win you also have to run the server first IIRC.
There were other problems with UDP (maximum packet size was significantly smaller on OSX, then I learned about MTU which is usually 1.5k and the underlying
layer is fragmenting datagrams anyway which I didn't know before).
So I may look into it (are you using TLCS?) I assume TLCS also has a localhost flag.
I've never tested it with localhost, I assume you plan to broadcast?
Some time ago I made a project communicating via UDP, there are two problems with UDP and localhost:
first you have to enable reuse address flag and I was only able to run server and client on the same machine by using two sockets and two ports per app.
On Win you also have to run the server first IIRC.
There were other problems with UDP (maximum packet size was significantly smaller on OSX, then I learned about MTU which is usually 1.5k and the underlying
layer is fragmenting datagrams anyway which I didn't know before).
So I may look into it (are you using TLCS?) I assume TLCS also has a localhost flag.
-
mar
- Posts: 2671
- Joined: Fri Nov 26, 2010 2:00 pm
- Location: Czech Republic
- Full name: Martin Sedlak
Re: livius sources (a TLCV-compatible client)
V1.2 has been updated on github: https://github.com/kmar/livius
thanks to Rasmus for submitting a patch that saves window layout in the config file
thanks to Rasmus for submitting a patch that saves window layout in the config file