May I say that there is a documentation but that you have to run doxygen yourself to get our documentation (except from some network stuff I wrote and that isn't included by doxygen). There are also plenty of examples in the SVN tree, which you don't want to obtain because you are to lazy to do it. May I also note that I was only around for about 4 months and that I managed to get an subversion server running for us and that it has actual code on it and that YOU who has been around for much more time (4 years what I make from your post) hasn't made ANYTHING and that the only thing I found in the old CVS repository were some experiments by someone else (can't recall his name ATM).
As I said, lousy job. Your PR sucks.
There are also running examples of what TRoS is capable of ATM, although they are semi hacked because some functionality isn't in TRoS yet. If you would have taken the time to download some 40-50MB from the SVN server and followed some instruction in a small file you would actually have noticed this. It is actually harder to test your code as someone would have to download some 500MB of dependencies and try to compile it, and that is just when you are able to get the code which is actually the hard part as someone would have to contact you who is barely online to get the code, TRoS' SVN server is online 99% procent of the time and always responding to your requests immedeatly.http://www.google.de/search?hl=pl&q=ope ... j+w+Google
Pick and choose. Virtually all of them provide the same - and, as I might point - they have so called _documentation_. It is not the same as "running doxygen". And all of them have features not actually hacked into.
And frankly - all of them will work well in TE.
May I point out that this decision was made end october/november, which is only around 4-5 months ago, which is also less significant time than your 4 years of just hanging around and doing nothing. I would also like to point out that it is very rude to just shove the effort that Hyronymus put in this project aside. Hyronymus has tried really hard and spend many of his little spare time (from what I heard) on this project.
Dunno if there is anyone who has gobs of spare time, let alone wants to spare it on TE. And I shoved aside anyone's effort. Including mine.
If you want me to use TRoS, and I really have nothing against it, then it is your job to prepare the following:
1. What tha engine can do (graphically, input, output, sound, timing etc), without anything hacked into.
2. What is its design philosphy, how each part operates with another
3. eis_os is 100% right. Without a licence I will not touch TRoS with a 10 foot pole.
As an example - take a look at SDL documentation. Imvho it is a perfect example of how to make a doc to an api. Notice - it is not made out of doxygen files.
Simply put - make a freaking SDK. Noone in their right mind will use your engine if they have to mow through Doxygen babelfish. Doxygen is for you as a developer, not for me as an user.
BTW - you honestly do not want your engine's part to be interdependant. Ie - if I (or anyone else for that matter) wnat to use TRoS for networking and sound, then I should do that without the rest being used.
Purno has your answer. We are still something that resembles a team. Imho you did pretty good job trying to manage it, but still you are managing a zombie. Even you saw that when in the status report you calimed that you have grown sick of nothing being done, and lost enthusiasm.
And the cancellation is the effect of Pioneeer Law. Since I am the one who writes the engine, I make the decisions. If Xeryous, Hellfire, Rein, PJayTycy, Fujitsu or anyone else delivers an engine earlier, his engine will be used. Clear and simple.
You are right. I came up a bit arrogant. How are those letters going?
GEt this discussion to ANNOUNCEMENT - usurpation topic. This one is for me to report progress.
1. Client now correctly talks to server
2. Terrain is properely created
Next: Display the terrain.