PDA

View Full Version : Sdk


xavier
10-02-2003, 07:09
I'm sure it's been asked before, but since one cannot search on the phrase "SDK" in the site search....*shrug*

What of it? Is there one? Are there plans for one? Can I help in any way?

Along those lines, when are y'all going to give in and let the world development community help you get this thing done and out the door? That is, open source. Put the source on www.sourceforge.net for the world to access. Then, instead of answering the question "when are you going to get the OSX port done?" a thousand times a day, you can say "feel free to do it if you want it that bad". :) The great thing about open source is that you do not have to give up any control over the project at all, while getting the added benefit of the talent and experience of software engineers the world over. If you were selling TeamSpeak then I could see keeping it closed-source. Since you are not, do yourselves and everyone a favor and open-source this thing.

I need to be able to access the server via SDK or scripting engine support, and I see no way of doing that, even though your feature list says there is an SDK.

Finally, rebuilding the system in C++ is not as difficult as it sounds IF there is a clean design. Syntax is syntax; the operating system support doesn't change. If you need to build up to a certain level of library support to match that which you get in Delphi/Kylix, well, that's where the open-source community comes in handy.

Back to my question...is there an SDK at all at present?

Thanks
Xavier

Cstar_maxim
10-02-2003, 20:56
check in your teamspeak client directory. The SDK is there. Be gental its basic but useable. I am at present doing some work with it.

xavier
11-02-2003, 01:41
That would explain why I couldn't find it in the server directories. ;) Thanks, I'll look there.

At any rate, y'all can add my name to the ranks of those that would like to see this open-sourced.

Cstar_maxim
11-02-2003, 01:49
Ya, I think most everyone could tell that was your prefferance. I don't think you are going to have to much luck there tho, dispite the advantages to opening it.

xavier
11-02-2003, 01:55
Hmm, ok, I have looked in the client directories and cannot find the SDK. What exactly am I looking for?

Cstar_maxim
11-02-2003, 01:57
C:\Program Files\Teamspeak2 client\client_sdk

xavier
11-02-2003, 01:59
Hmm, definitely do not have that one. I am running 2.0.13.13...am I behind the times?

xavier
11-02-2003, 04:08
k, installed latest, whipped up a C-language header for it, it links and runs just fine, except....how do I set the user login info before I call tsrConnect()?

N. Werensteijn
11-02-2003, 18:31
you can set that in the url. read the client manual for more info

the parameters are:
nickname, loginname, password, channel, subchannel, channelpassword

basicly its like "teamspeak://server:port/nickname=MyNick?loginname=mylogin?password=mypassw ord"

I'd like to ship the c header with the next releases.

xavier
11-02-2003, 18:39
You want the C header then open-source this project!!!! :p

just kidding, of course. ;)

BTW, with the C header it is not necessary to provide the two DLL/library loader functions, as the runtime loaders in both Windows and *nix will pick up the shared object or DLLs just fine. Let me wrap the function declarations with the LINUX/WINDOWS ifdef's and then do some comprehensive testing and then I'll forward it to you.

Greg

Mozrin
20-08-2003, 16:30
Is the current version of the SDK immutable? I assume the headers are not the actual ones in use, but rather a santitized encapsulation.

Why am I asking? ;) I spent a number of year before my recent retirement as a systems architect for a commercial product that has over 80 million seats. The biggest regret they had was the quick hack-and-deploy they did on a version 1.0 API to please a few that they then had to live with through the years (15 of them).

I hear a lot of people asking for open-source and for an API. Perhaps you can accomplish both of these tasks at the same time and still keep the core intellectual components of the source code private.

If you were to create a robust API for this product that could actually be used to write a TeamSpeak server and client, this would allow you to massage and release components of the source code into the public domain and keep the engine private. It would also open your product up significantly to ancillary markets.

I am not sure how your company is structured today, but if volunteer work is something you frequently use ... I am pleased to provide my skills if needed. The only caveat is; I do not accept any form of payment for my work these days, except the occasional key lime pie. ;-)

Finally, if you already do all of this ... please accept this post as a lonely rant from a retired middle aged nerd. :D

kind regards,
Mozrin Caer
mozrin@mozrin.com