| Your first option is correct: the second level of zoom should just replace the outline of the building in zoom 1 with a photo of the building Sami Deen |
| Is there a way to do multiple collaborators in ECoDE? Donghan Li |
| You're right, Brett – there are really three levels. Mark Guzdial |
| . | I have moved the P3 date – my fault, it should have been longer in the first place. I have answered the issues of research vs. teaching wrt to ECoDE on the Fall 2002 Announcements page. Mark Guzdial | . |
| Absolutely. We did debug it pretty thoroughly before you got it, but 160 students will do things that a half-dozen Squeakers won't think of. We will find bugs, and Kathy and Jonathan will fix them as soon as they can. All new software is like this, and some class has to be first. Lucky you! :-) More seriously, you do have more time to get through the design now, and bug fixes will be coming out ASAP. Mark Guzdial |
| P.S. All the code is in Squeak. If you find a bug, feel free to fix it and post the fix and your explanation to the ECoDE page. I will give Extra Credit for good bug fixes with good explanations. Mark Guzdial |
| Its all from Mark. Sami Deen |
| As for the question about displaying buildings, do what works well in the UI. If cutting buildings off looks weird, do something else. If not displaying the building makes the interface feel strange, X it. Create a good look and feel design. Sami Deen |
| . | Yes, all of that in horizontal rules is mine. Like Sami said: I'm perfectly okay with showing parts of buildings. Note the differences between what I'm assigning and what the Alumni website does: You must support zooming WHERE THE USER clicks, you provide more than one level of zoom, AND you actually show something that looks like the building at the bottommost level. Mark Guzdial | . |
| . | You can choose not to be in the study, so your usage data will not be used in any studies. But I'm requiring use as the teacher. That the design process becomes longer and harder isn't really too surprising – ECoDE does require more effort in the design process, but not not more than using, say, Rational Rose. At least, that's my perception. I'd welcome some direct comparisons! Mark Guzdial | . |
| Milestone 4: Note that on milestone 4 you need to be able to zoom back out. Opening new windows for each zoom level, and then closing them does not count as being able to zoom back out. |
| P5 shouuld be able to do everything that P4 can. P6 only has to have the capabilities that we specify. P7 should be able to do everything that P6 can. Mark Guzdial |
| Turn in your whole ECoDE project. We'll grade the CRC's and Scenarios in ECoDE. Include a UML diagram for OOD. Mark Guzdial |
| You're welcome to do Wonderland however you want. I know that you don't know all the details right now – that's what makes this a design activity. Frankly, I hope that you get some of the design details wrong – that's why we require this complete design so early. I want you to learn about design by making some mistakes! WRT your questions: Yes, everything will be an actor. Yes, you can render everything, and perhaps hide the things you don't want someone to see. Make your design as detailed as you can. Mark Guzdial |