Okay I need a todo list. I get a lot of ideas in my mind and then forget them as I think of more, so I'm writing them down here. It's also to give people an idea of what to expect coming from this project.
-The change log-
Change textbox background color to something non-black so things are actually readable. (Table and Lobby)
Implement a response to keyword 'stuci' to identify program within lobby or chat
Adjust program title to new name -- Using STUCI Windows (Logged in as zappa_engine)
Help menu (About screen for version info and simple quick usage help)
-To Do-
Implement the moves list on the table
Splash screen
Update the chessboard colors and chess piece graphics
Store scoring and ponder information to be available for table chat access (score, engine, offered even on viewable tables)
Adjust table chatter to display in correct tables (when multiple tables are open)
Login screen automatically popping up on start (and closing on successful connect)
Save username and password option, auto-login option (just enter captcha when you start program)
Show invitations, draw offers, and save offers, undo offers
A way to grab player information (win/lost etc)
Ping response
Auto-start fix (again with another program!)
Display a message when someone joins or leaves the table
Anti-idle timeout
Display a connected/disconnected to server info in lobby chat
Check for failed captcha entries and allow another attempt
Lobby user list
Basically clone Yahoo's java or flash interface
Table view filtering (show only people above certain rating, show only games with certain time controls, etc. A visual "seek" functionality)
Update/refresh ratings in table observers after each game
The Kibitzer channel - Details: It scrambles/decodes messages sent to the table so it looks like junk to casual observer but is prefixed. A STUCI client or any client at supports it will decode the message when it sees the prefix and display the information to a kibitzer channel. In this way, you can emulate chatter that the actual players don't see, but observers can comment on the game. The client wouldn't decode the message if it was an actual player (although it could... for unfair advantage?)
Blacklist changes: The client would announce spammed blacklist to the user in table chats or possibly lobby chat too. But if many users are using this program that would produce a lot more spam in the lobby with the notice. If people really aren't spamming they can type in the unlock code mentioned that is a unique generated keyword for their ID to un-blacklist themselves. There will be an option to boot or not boot when the blacklisted user joins a table. If the program is not auto-booting, the client can print a message with unlock code if the option is wanted. Also, the client can notify user that they are on ignore on join, again with the optional display unlock code. True automated spammers will probably not unlock themselves. A manual spammer probably could if they typed in the unlock code but it's unique to every user so they'd have to type in lots of unlock codes if they were blacklisted by many people for spamming, a pointless effort on their part. Another way to manage the blacklist publicly would be to display it in lobby if someone types in blacklist. It would only display a list of blacklisted users online. Then if they typed in 'unlock code' in the lobby, it would print the unlock code for them. Of course this is all on a timer so as to prevent the client from spamming. All other messages from those blacklisted users are ignored.
Internal Polyglot .BIN book read support without the need for polyglot (thanks to open source of polyglot)
That's just a starter list I suppose. Later on will check to see if there are any retro commands from STUCI Classic I want to implement.
mocklogin.jpg
You do not have the required permissions to view the files attached to this post.
