Roadmap for version 0.1 Expand all | Collapse all

96% of 64 tasks completed. 5 open tasks:

FS#65 - Issues specific to the Mac OS X Expand Collapse

There is network and probably threading/mutexes problems with the Mac Version.

See this mail on openSpeak's developper mailing list for more informations.

FS#70 - Character size, style and encodign problems on Mac OS X Expand Collapse

See this screenshot :
{{http://img228.imageshack.us/my.php?image=image1cv1.png}}

FS#75 - Building openSpeak with unicode wxWidgets fails Expand Collapse

Currently its not possible to create a unicode build on Windows. Linking oS with wxWidgets unicode libs gives several linker errors.
To solve this problem we need to take a deeper look at the wxWidgets build process and esp. the setup.h which lets you configure what parts wxWidgets buils into its libs.

FS#78 - Socket error on the server Expand Collapse

Got tons of these errors :

[06/04/08 21:17:18] [ERROR] Exception thrown: got an error while sending
[06/04/08 21:17:18] [ERROR] Exception thrown: got an error while sending
[06/04/08 21:17:18] [ERROR] Exception thrown: got an error while sending

I guess the problem is that the server has 2 IPs and the server has to bind to one, not 0.0.0.0

---

The problem still occurs after the latest patch is applied... but after a few hours.

FS#80 - Problem with sound playing on Vista Expand Collapse

A user under Vista has no sound. His logs show that he recieve the data. He is heard by the other users.
Sous playback is working well with other apps.

Roadmap for version 0.1.1

0% of 0 tasks completed.

Roadmap for version 0.2 Expand all | Collapse all

25% of 11 tasks completed. 9 open tasks:

FS#10 - add adjustment control for VAD Expand Collapse

A adjustment control for the VAD would be nice. So you can decide, if you wanna shout or whisper ;)

FS#11 - volume control for sound output Expand Collapse

A Volume Control for the soundoutput. Perhaps you want to mute your soundcard sometimes

FS#37 - Improve the netcode Expand Collapse

Improve the netcode by using uchar instead of full numbers when sending packet/user ids over the net. Instead of seperating several values by a space we're not seperating them at all. This should save us a few bytes per packet and some splitting doesnt need to be done.

FS#48 - Add a remote admin interface through simple telnet Expand Collapse

Add an easy remote interface to the openSpeak server which will allow admins to easily change the settings file and retrieve some stats (like the amount of people currently on the server).
Retrieving some simple stats could also be allowed to non-admins to provide a way to get informations for a server list or similar things.
Access to the administrative options would surely be protected through a password or later on (with a working acl) through a login.

FS#58 - Create a new client backend to seperate backend and gui Expand Collapse

Create a new client backend and seperate everything from a distinctive GUI framework like wxWidgets. This allows other people to integrate openSpeak for example into their game or simply create a custom client.

FS#59 - Choose between several available audio in-/output devices Expand Collapse

Add a possibility to choose between several available audio in-/output devices. This is especially important for people with USB headsets or with onboard and PCI soundcards.

FS#60 - Add threading support to the library through boost::thread Expand Collapse

Use the boost::thread library to add threading support to the library.
This includes: * Making classes which could be used by several threads threadsafe * Add helper classes to ease up the use of boost::thread * Add the possibility to build the library without threading support (for example to build only a threadless server)

FS#63 - Add i18n support through GNU gettext Expand Collapse

To help people who don't speak english we should add internationalization support most likely by using GNU gettext.

FS#66 - Make it possible to launch the server via the client Expand Collapse

This would be useful, in particular on Mac OS X where we'll ship an Application Bundle where executables files are not in PATH, thus making hard for a "basic" user to launch the server app.

The idea is, in a first time at least, to add an menu entry called "Launch server" which launches the server and open a windows where the server stdout will be redirected.