| M1 says to display 5 generations in total. It merely uses the 3-2 rule as an example of how to separate the 5, but you could do it as 4-1 or even 5-0...likewise, 0-5 and 1-4 are valid too. The whole idea was that you could construct a visualization matrix flexible enough to wrap around points in a geneology tree. Chris Verges |
| Not that I'm aware, but you can easily create one. Chris Verges |
| Hmm...interesting question. I would say that the precedence set by M2's rules needs to be followed: that is, whatever M2 says should be what goes when adding people using the GeneologyMap with: statement. But when adding people with the GUI, as long as you state HOW to add the people, you should be okay. Can the prof/another TA back me up on this, please? Chris Verges |
| You do need for "GeneologyMap new open" to work, but this should not be a real constraint on the design. Your GeneologyMap class can have just the two or so required methods on it if you want. -Lex Spoon |
| Lex answered this on the newsgroup. I'll recap here. If you need the full answer check the newsgroup. The emphesis will be on M4 documentation. Thats what we will be looking at. That said, you can submit your full documentations ( M3 documentation) with additional details added to the M4 part if you want to. Sami Deen |
| Yes. Sami Deen |
| The interface to the system is your decision. If the user can enter, manage, and view his or her information effectively, then your on the right track. In other words if it works, and is usable your ok. Sami Deen |
menu add: (person getName) target: self selector: #(doSomething: person).
| Good point. Sami Deen |
| You can use any messages you want. The key is that your system needs to be able to recreate the family tree from the exported messages. Sami Deen |
| We're looking for a working GUI. Your grade will be based on how well your GUI functions. This means a fully functioning integrated front-end (the GUI) and back end ( your previous code and export). It needs to all work together correctly. Don't have a GUI come up that does little, or nothing, and fully functioning previous milestone code sitting in the background. Work at integrating as much as possible, thats where your grade will come from. If you have a time constraint, the critical step will be having some kind of reasonable graphical representation on the screen. Once this is done, you have some options as to what you want to implement. Without this step nothing more can get implemented in terms of this milestone. For example, once you have your graphical interface you can decide, if you want to implement, export (5%), graphical representations of name and aliases, gender, family relationships, marriage relationships, birth and death information, and miscellaneous information ( 4% each), a working check button, or other similar gui control (10%), and so on. Sami Deen |