Various problems.

[Prin]

Server
--------
The system of save all data is obsolete, can be improve with database in sql lite, this will be better for administration and development new tools.

Clients
--------
When internet line drop, client is disconnect but haven't reconnect for connect when internet line is up, that can be improve with tab in Settings that have number of retrys and delay betwen retrys for reconnect to server.

Configuration of admins groups
-------------------------------------
Whichever with access to "User Edit" can grant any privilege.
For example, if i make group "Admin" with all privilege, and i make second group "Sub-Admin" with "User Edit, Kick, Ban" can modify his permissions to all privileges himself or get superadmin inclusive.

Chats
-------
Anyone can do flood in chat system.
Channels haven't chat, for people that want send notice for his channel but no for all server.

PTTs
------
It's curious do a PTT for player, but there is a problem when disconnect because loss configuration of PTT and Channels can't be associated to PTT that is a problem, too is a problem that one key must be for one because a lot of times it's required say the same at same times to various users. Other possibility will be create tab with personal configuration of PTT's for users and channels that appear as user configuration.

Colors
-------
The white background is very annoying and can't be modified in settings.

Icons
------
It's neccesary a icon for mute microphone and other for mute headphone, because people dont know who is muted. Also It's interesting put a color to icon while user is talking for fast visualization.

Channels
--------
Comments of channels must be in properties in a new tab for do more intuitive.


Refresh
-------
While people are talking, the tree is refreshing continously and generate a bit lag to users.

[thantik]

I'm going to try and decipher this:

Server: You want configuration and settings all in a single SQLite database, or possibly multiple SQLite databases? -- I doubt that will happen, there is no need for this overhead at all. The config file is small, and text files are standard practice in Linux for configuring services.

Clients: Auto-reconnect -- You want to be able to auto-reconnect when your connection is dropped and be able to specify the number of retries/delay between retries. -- I believe this is in the working. There really is no point in allowing setting the number of retries, as it should always be continuous, if you don't want to reconnect, you close the program.

Configuration of Admin groups: -- You want to be able to delegate a hierarchy of admins, who themselves can grant admin powers to those below them with equal or lesser privileges? -- I'm unsure of exactly what you're asking here but I have a feeling that you won't see a change on this any time soon. Changing the system for permissions can get hairy and I'm sure Chris doesn't really want to delve into that any time soon.

Chats: People can currently flood the chat system - Good suggestion for some sort of rate-limiter and/or auto-kick functionality. I think this could be implemented quite easily and don't be surprised if you see it sooner rather than later.

Individual chat channels: I'm not sure how likely this is to happen.

PTTs: I have no idea what your problem is here except for that you're suggesting some sort of configuration tab for PTT.

Colors: Skin-ability would be nice, but it won't be happening. The background color change on the other hand, *could* -- I actually think, however, that chris will run into some issues with wxWidgets and the container he's using for that specific area of the client though. I suspect he'll be working in this soon though due to something you mention later in your post

Icons: People that are globally muted or muted individually should have a marker next to their name already. Am I wrong on this?

Refresh: I've noticed this as well, there seems to be some sort of redraw lag between updates of the control. When you have many many people in a server I can see where this could get out of hand quickly. Chris if there is any way you could take a look at this? (Maybe some sort of tool that generates a bunch of VC client instances, and loads them up with fake clients and just queues some sort of sound data at random? -- this would be a good testing tool later on as well)

[ChrisW]

Oh boy, this is a biggie...


Server config: Thantik is correct - I don't have any plans to store server configs in a database. I don't see a need for it, but I am not afraid to admit that I'm wrong.

Auto-reconnect: I agree that this needs work. I'd like to make it continuously try to reconnect along with some sort of GUI feedback that it's reconnecting and a way to cancel (without closing the program).

Configuration of admin groups: Not sure what you mean here.

Chat flood protection: There is flood protection, but it may not be stringent or apparent enough. If you're the one flooding, your messages will still appear in the chat window but will not be sent to the other clients. There is currently no feedback for when you trigger a flood (which should be changed somehow)

Channel chats: You can create a phantom in a channel and any messages sent through the phantom will be sent to that server.

PTTs: I think I understand what you're suggesting, and I think it would be useful for those that use PMs or phantoms a lot. Good suggestion.

Colors & Icons: Colors can't currently be changed, but icons can. If you're feeling ambitious or know an artist, I'm happy to evaluate a new set of icons for inclusion (either as the default or as an alternate skin)

Refresh: I've noticed this too. It only seems to happen on windows, and my initial investigation into the issue didn't turn up any clues. I was hoping that it was just me or that it was being caused by an external source, but I fear that may not be the case. I'll have to look deeper into this.