The Big Picture
Posted: Fri Jun 30, 2006 9:48 pm
Gunter, here are my thoughts on the big picture.
I'll tell you some of this, and anyone is free to add-in thoughts or ideas.
The "Big Picture" is not all about the hub, but the hub concept will be integral I think in the long term.
Here I go ... this framework will help explain how the future is going to shape out.
1. There will be a "super" Quake Launcher. It will support the following engines ProQuake, JoeQuake, QRack and DarkPlaces.
These are the only engines with an NAT fix, which basically means they can connect if someone is using a router. If FitzQuake gets an NAT fix, it will be added.
2. The super Quake Launcher will have wild functionality. These launchers will be rolled out in waves. The first wave launchers will be client specific with either the QRack or DarkPlaces one likely coming first and have "lite" functionality.
After those are out, it is likely that the JoeQuake Launcher will come next, which will have a great deal of functionality and then followed by an all Quakes Launcher.
The above could all vary depending on what/when I decide to work on.
The ultimate final product launchers will have a server browser, a "Quake updater" which keeps you current on maps and heavy technical support capabilties (no more asking people "what client are you using" and a million other things, they can paste a "diagnostics" into a forum).
These aren't pie in the sky ideas, most of this code was written by me in August/September 2005 and, in fact, I was about ready to release the JoeQuake Launcher when Joszef released JoeQuake 0.15 which changed many cvar names and 0.15 had some "issues" that were later fixed (all zeros in the ping display) ... but that kind of put me in limbo at the time.
CONTINUED ....
I'll tell you some of this, and anyone is free to add-in thoughts or ideas.
The "Big Picture" is not all about the hub, but the hub concept will be integral I think in the long term.
Here I go ... this framework will help explain how the future is going to shape out.
1. There will be a "super" Quake Launcher. It will support the following engines ProQuake, JoeQuake, QRack and DarkPlaces.
These are the only engines with an NAT fix, which basically means they can connect if someone is using a router. If FitzQuake gets an NAT fix, it will be added.
2. The super Quake Launcher will have wild functionality. These launchers will be rolled out in waves. The first wave launchers will be client specific with either the QRack or DarkPlaces one likely coming first and have "lite" functionality.
After those are out, it is likely that the JoeQuake Launcher will come next, which will have a great deal of functionality and then followed by an all Quakes Launcher.
The above could all vary depending on what/when I decide to work on.
The ultimate final product launchers will have a server browser, a "Quake updater" which keeps you current on maps and heavy technical support capabilties (no more asking people "what client are you using" and a million other things, they can paste a "diagnostics" into a forum).
These aren't pie in the sky ideas, most of this code was written by me in August/September 2005 and, in fact, I was about ready to release the JoeQuake Launcher when Joszef released JoeQuake 0.15 which changed many cvar names and 0.15 had some "issues" that were later fixed (all zeros in the ping display) ... but that kind of put me in limbo at the time.
CONTINUED ....