Hello,
Deurk recently asked about the possibility to make use of a protocol prefix for qw. I did some googling and found it was possible to register your own protocol prefixes such as http:// or ftp:// in the windows registry. Passed that info on to deurk who tried registering qw:// and he got it working with ezQuake (except there was no support for it). This support makes it possible to have qw-urls on webpages, or paste them on irc or whatever. When clicked they will launch the associated program.
So I decided to add a new command /qwurl that parses qw-urls, which have the following format:
Examples:
Deurk added a "Play now!" button to his QTV where you can try it out => http://qw.deurk.net:27599/nowplaying
Also to make it simple to register ezQuake as the qwurl-protocol handler, I added a command /register_qwurl_protocol that registers the currently running exe in the registry.
Also the default behaviour on startup is to check the registry if the current exe is the registered one, and if not, shows a warning message in the console. Behaviour for this can be changed using this cvar:
cl_verify_qwprotocol:
0 = Don't check
1 = Check
2 = Don't check, always register the current exe.
Another added feature that also includes demo playback and .qtv-files. Before when you ran a demo file in explorer it would start ezQuake and play it. But! if there was already a client running you'd get a message "qwcl is already running". The new behaviour is to play the file in the currently running ezQuake instead.
Note that this was just added to CVS, to be able to use it you need a 1.9 alpha build that was built 2007-10-13+
http://uttergrottan.localghost.net/ezquake/dev/nightlybuilds/
Deurk recently asked about the possibility to make use of a protocol prefix for qw. I did some googling and found it was possible to register your own protocol prefixes such as http:// or ftp:// in the windows registry. Passed that info on to deurk who tried registering qw:// and he got it working with ezQuake (except there was no support for it). This support makes it possible to have qw-urls on webpages, or paste them on irc or whatever. When clicked they will launch the associated program.
So I decided to add a new command /qwurl that parses qw-urls, which have the following format:
qw://server:port/[join, connect, spectate, observe, qtv]
Examples:
Connect to server (same behaviour):
qw://server:port/
qw://server:port/join
qw://server:port/connect
Observe:
qw://server:port/spectate
qw://server:port/observe
QTV:
qw://channel@qtvproxy:port/qtv
qw://server:port/
qw://server:port/join
qw://server:port/connect
Observe:
qw://server:port/spectate
qw://server:port/observe
QTV:
qw://channel@qtvproxy:port/qtv
Deurk added a "Play now!" button to his QTV where you can try it out => http://qw.deurk.net:27599/nowplaying
Also to make it simple to register ezQuake as the qwurl-protocol handler, I added a command /register_qwurl_protocol that registers the currently running exe in the registry.
Also the default behaviour on startup is to check the registry if the current exe is the registered one, and if not, shows a warning message in the console. Behaviour for this can be changed using this cvar:
cl_verify_qwprotocol:
0 = Don't check
1 = Check
2 = Don't check, always register the current exe.
Another added feature that also includes demo playback and .qtv-files. Before when you ran a demo file in explorer it would start ezQuake and play it. But! if there was already a client running you'd get a message "qwcl is already running". The new behaviour is to play the file in the currently running ezQuake instead.
Note that this was just added to CVS, to be able to use it you need a 1.9 alpha build that was built 2007-10-13+
http://uttergrottan.localghost.net/ezquake/dev/nightlybuilds/