|
This requires some collaboration with the browser and/or OS. When you click on a link in a browser, the browser first looks at the protocol field (before the colon) to decide what to do with it. We'd need to establish a protocol name that wouldn't collide with those already in use. I don't know if there's a length limit, but using "teamspeak:" would probably be ok.
You then need to configure the browser and OS to know that when you click on a link with that protocol, the browser launches TS and gives it the URL to parse. I don't know if 2.0 has the ability to accept a URL like this, but it would be straightforward to add. I'd suggest using a special switch (say "--url teamspeak://user:password@ts.myclan.org/channelname", which is similar to what IRC and Roger Wilco uses for their URL's).
|