zambr123
commented
11 years ago Better explanation:
The chat type-in box (where you enter text) could act as a command shell.
So for example, you could type:
/login (user)(pass) /kill all - useful for admin to kill users, to apply a critical svn update
If the server goes down (for svn update or just down). the GUI stays on the screen and the users do not have to display the login box, but instead they will auto-reconnect after a specified time (e.g auto reconnect try after XXX mins).
Also useful for people that time out of the server, as they will get re-connected after XXX mins too. As this happens a lot, a process such as this, will help prevent the hub from being empty.
Prinygod
Just like QMC2, have the log file displayed permanently at the bottom right of the screen, ideally a 2nd tab on the user list (see pic).
This will come in very handy indeed, especially when user has issues, such as emulator runs, then quickly stops for no reason (hence look up issue, missing files, etc easily), which happens hell of a lot.
This will also become very useful later on when the cmd screens on the login process are finally removed and instead adopt a similar login procedure to MIRC (e.g launch MAMEHub, immediately presented with the GUI, goto top menu option 'login', and whilst all this is happening, the log file is updating in real time via the tab - hence similar in design to QMC2 and MIRC).
PLUS: having option to login via chat edit box would be useful (same feature as MIRC) /login (user) (pass) and when a user disconnects, time's out, MAMEHub could automatically reconnect the user with a design like this very easily (same way MIRC reconnects timed out users).
PLUS: user would be able to play games offline.
PLUS: if people are idle in hub / away, etc, and server goes down, they get automatically reconnected when its back up, as MAMEHub client will try every XXX seconds to reconnect.
SVN Updates: I like the idea also, where when DG has an SVN update ready, he can kick all users /kick all, and then they automatically reconnect, perform SVN update and then automatically login to hub directly after.
Obviously, any changes to the GUI screen objects / menu's with this model, will require a fresh install of MAMEHub. So such changes would only be added for a major version release.