If you using an IDE Javadoc browser then it is sufficient, but if you're viewing the online HTML documentation then each method needs to contain a brief description -- even if it's identical to the contents of @return tag -- for the sake of the "Method Summary" section. I've seen some Xith classes with methods such as getLLC(). Granted, that's just a getter but I have no clue what LLC means.
I've checked the online JavaDoc and you're right. There should be brief method descriptions even for getters.
PS: I wouldn't be surprised if there was a way to avoid this duplication. I haven't look into it.
This would be very useful. Please report back, if you find anything about it.
I agree that duplicating the @return text sucks, but it should still be done. The original source-code comments are not what matters, the rendered result *is*. The same can be said for Javadoc comments that contain HTML (the Java core APIs are full of this!). If you look at the comments in the source-code they are hard to read, but when you look at the resulting HTML output it is absolutely great and that's what matters. Just my 2 cents
I personally perfer it the other way round. I never look into the online JavaDoc, since it is very uncomfortable to use while IDE internal JavaDoc is very easy to use and is accessed in no time. If you checkout the SVN trunk and bind the project to yours, you can even jump into the methods and read the code for even more information. But I do agree, that both IDE and HTML JavaDoc should be good. I will try to improve it when I have time (it's on my list).
I remain a bit skeptical of tracking bugs using the forum, but I guess I'll have to take your word for it
What is the average turn-around time between a bug being reported and getting fixed?
It depends on how much time I/we have. If I have plenty of spare time, I usually fix reported bugs very shortly (sometimes within minutes). But this is still a project developed in free time. So nobody can guarantee you, to have the necessary amount of spare time. Just browse these forums and you will see, that very most bugs have been fixed within a very short time.
Does anyone offer commercial support for Xith3D in case we run into problems (or find a bug) and need a quick resolution?
AFAIK this has never been done before. But we can make an appropriate arrangement, it is not impossible.
I strongly encourage you to do some first steps using the engine. You will see, that it is very easy to use. Also read the main documentation XIN
as well as the InputSystem's documentation