> By poor design, I mean it sometimes looks some of the > code was created as a prototype and when it was complete no > one went back to refactor it.
Code design is very subjective. Why don't you provide us with concrete places where you think refactoring needs to be done. > By poor documentation I mean that most source code files have > absolutely no comments in them and the variable and method > names are so short that unless you were the original author > you'd have no way of knowing what the heck the code does or > why. You have been told over and over again that you are more then welcome to provide patches for javadoc or any other documentation. So far I havent see any... > The point isn't whether or not you could find this out > by sitting down and analysing it for a few days. The point is > that you shouldn't have to. You still don't understand that this is a community effort and we do this in spare time of which we have very little. Do you think I would rather write javadoc or spend time with my wife and my daughter? So instead of bitching about it why don't you contribute! -Igor ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
