Author Topic: WCS ok, but there is one catch... (Read 11844 times)

String · « **on:** April 07, 2007, 05:07:31 pm »

Hi there,
i was just messing around with my Linux Ubuntu, doing something that you would call a graphic frontend
for the WCS 1.8 Linux Edition. Unfortunately there is something wrong with the KM's program !!!

My Qt 4.2 ("cutting edge") application should read the standard output of the Wcs program in order to show userlist, banlist,
primary connection, everything wasting your resources, lol, but it's not working due to a missing line in the
WCS code: fflush(stdout)

PLEASE, KM whenever you should release a new version remember to flush the output to the screen !

By the way it's named QWCS. Bye bye

KM · « **Reply #1 on:** April 07, 2007, 06:07:54 pm »

there's not much need to flush the buffer for the output to /dev/null, which is where most users are directing that output

it's a simple enough thing to add though... will be done in b10

String · « **Reply #2 on:** April 07, 2007, 11:20:06 pm »

Thanks, then i will wait for the b10.

KM · « **Reply #3 on:** April 08, 2007, 06:22:46 am »

btw, in case you planned to add the "WCS Advanced" type features in a similar way to how you did them in the initial windows WCS Advanced, don't waste time doing it that way, I have added those features to b10 for windows and done them in such a way that should make it easy for your program to do it as well for linux without needing to include a full client etc... more details when b10 is released

(it is already done, i just need to finish another unrelated change before i release it - got half way through doing one of the things on my to-do list and i had to stop and go to work...)

String · « **Reply #4 on:** April 08, 2007, 03:29:23 pm »

Mhh,
QWCS is not meant to be a pseudo "Advanced" WCS. It will provide the WCS under Linux with quite the same interface
of the Windows edition. The program will "scan" the WCS log through regular exp. and will grab info about users entering/leaving, primary conn./disconnecting, etc... There is already a tray icon.

Now i can't wait to see the b10 release.

KM · « **Reply #5 on:** April 08, 2007, 03:50:32 pm »

you better re-think it then if you didn't intend to have control of the room from the interface

String · « **Reply #6 on:** April 09, 2007, 04:15:42 pm »

OK,
everything seems to work now so i can go on. With the "exec.txt" rtick it's relly a joke to have control of the room so i'm a little re-thinking the program. This WCS is what a server is meant to be.
Great job.

KM · « **Reply #7 on:** April 09, 2007, 06:50:02 pm »

btw, there is also an undocumented debug command /dumpcore ClientList <filename to save to> that you might find useful for extracting additional user information which isn't in the normal output

although if you have ideas for better ways to get access to that sort of information then let me know because that method isn't ideal, and I think outputting it all in the log would just look really ugly for others not using the information like that

String · « **Reply #8 on:** April 10, 2007, 12:24:33 am »

Some people, when confronted with a problem, think
“I know, I'll use regular expressions.” Now they have two problems

Lol. That command is interesting too, but i prefere the server log, even though it's not complete.

I think the wcs log is a little too verbose (primary connecting/disconnecting) for the normal user even though
i would like to have more informations. Ex (access change, client, etc...). Maybe adding a new entry in the config.ini...

I don't think there is an easy way to do that without any interface.

KM · « **Reply #9 on:** April 10, 2007, 01:35:07 am »

the /dumpcore command for outputting the client information could be used in combination with checking the logs, so for example if you see someone do a /login or a /setaccess or something then refresh from the file to get their new access, that sort of thing, so the normal output is used to tell when the user information is out of date, and when it's out of date do a refresh

(btw, /hidecmd prefix would be useful to save flooding the admins when it refreshes)

trying to add it all to the output would be a problem simply because there is so much of it (and renames etc would need all the info as well)

String · « **Reply #10 on:** April 10, 2007, 11:12:16 pm »

This is a QWcs preview:

It's half working ,but there are a few problems i have to deal with... Ex. When an user gets kicked or banned i'm not able to see it from the server log, so i have to try with the /dumpcore command.

~~James420~~ · « **Reply #11 on:** April 11, 2007, 12:02:46 am »

Eh, seems like it would be easier if he just gave it a GUI for the Linux release.

KM · « **Reply #12 on:** April 11, 2007, 09:36:38 am »

if there is a kick or ban then it still shows the disconnect the same as when they leave, so they can be removed from the list then

James: any why would I do that? that would instantly exclude all servers from even being able to run it, the entire point of a linux release is to allow it to be run on a server instead of just workstations

String · « **Reply #13 on:** April 11, 2007, 11:33:17 am »

OK, forget about the kick problem, i missed it...

Apache web server doesn't have a gui and that's the way it should be.
Anyway most people now approching Linux just use it as a desktop.
So i think it's a good idea to have something like the windows thing.

KM · « **Reply #14 on:** April 11, 2007, 11:48:58 am »

that's why a separate GUI like that is a good idea, to allow those users to use it - making it a GUI program would be a very bad idea, straight off of the top of my head I can think of one room that would be unable to use it if a GUI was added... winmxworld!

I had considered a separate GUI similar to what you are doing just never got around to it

although I'd probably make a few changes to the server to accommodate the GUI to make things easier if i was doing it, that's why I asked about any ideas for things that could make it easier for other programs to interface with WCS... basically asking what you want me to add to make it easier, lol

String · « **Reply #15 on:** April 12, 2007, 10:34:59 am »

This is the very first release of QWcs. From now on i will work on the same program written in Python
using the Gtk toolkit, instead of C++ & Qt as for the QWcs. I'm sure i can do it in a simpler way and with
less code (ergo bugs) using Python. Just in case i failed i would come back to QWcs.

Indeed Qt 4.2 it's not very common yet.

String · « **Reply #16 on:** May 07, 2007, 08:31:43 pm »

Eventually i found the only surviving copy of the PyWCS on
a pendrive where maybe i've dropped it. So i will post here very soon.

maybe a cool screenshot first.

String · « **Reply #17 on:** May 08, 2007, 11:59:51 pm »

A PyWcs screenshot. The program will be soon released.

GhostShip · « **Reply #18 on:** May 09, 2007, 12:41:56 am »

Hmm, very interesting String

Nice to see you back to the grindstone and cheers from us all for working on this useful WCS interface

Victim · « **Reply #19 on:** May 09, 2007, 01:28:25 am »

Yer.. Will be looking forward to what you release.