Excellent! I have a todo list i'll work on including further class commenting, method classification on example games, ... I wanted to share what i have to get feedback. Feel free to add to the list!
About the issue on EMonsterMover i thought back and forth about having only one configurable (dynamic choices) / the four (static choices). At the moment i went with the last one because i thought that despite not nice, it eased the reading being more explicit also i wasn't completely sure of being able to remove it. Now that it's finished it can be seen that is unnecessary not beautiful. Thank you for pointing it out, i'll change it. What names do you find confusing, which ones would you use instead? Have you read the first paragraphs of the documentation (mainly class comments)? On Thu, Mar 26, 2015 at 3:22 PM, kilon alios <kilon.al...@gmail.com> wrote: > I am taking a look at your code and I dont understand something you have > in BgEatBullet package EMonster1Mover, EMonster2Mover , EMonster3Mover and > EMonster4Mover. All four classes are identical apart from the return > values in some methods. Why not use 1 class and 4 instances of that class > instead ? > > Also I second the name of the classes is confusing. >
