Talk:Frogs design
From CSSEMediaWiki
(Difference between revisions)
m |
m |
||
| Line 1: | Line 1: | ||
Adding [[avoid "becomes"]] as one of the heuristics broken in this Frogs design --- [[User:Johannes Pagwiwoko|Jojo]] 01:53, 23 July 2008 (UTC) | Adding [[avoid "becomes"]] as one of the heuristics broken in this Frogs design --- [[User:Johannes Pagwiwoko|Jojo]] 01:53, 23 July 2008 (UTC) | ||
| − | I think we should take out the ''exportXML()'' from ''Frog'' and also take out the ''display()'' from the ''Move'' and put them together in a class...but I cant think of a name for that class...''FrogManager''? ''FrogTagger''? I feel suspiciously unsure about this naming. I got a feeling that in Cosc224 we shouldn't name class like that. --- [[User:Johannes Pagwiwoko|Jojo]] 02:08, 23 July 2008 (UTC) | + | I think we should take out the ''exportXML()'' from ''Frog'' and also take out the ''display()'' from the ''Move'' and put them together in a class...but I cant think of a name for that class...''FrogManager''? ''FrogTagger''? I feel suspiciously unsure about this naming. I got a feeling that in Cosc224 we were thought that we shouldn't name class like that. --- [[User:Johannes Pagwiwoko|Jojo]] 02:08, 23 July 2008 (UTC) |
Revision as of 02:09, 23 July 2008
Adding avoid "becomes" as one of the heuristics broken in this Frogs design --- Jojo 01:53, 23 July 2008 (UTC)
I think we should take out the exportXML() from Frog and also take out the display() from the Move and put them together in a class...but I cant think of a name for that class...FrogManager? FrogTagger? I feel suspiciously unsure about this naming. I got a feeling that in Cosc224 we were thought that we shouldn't name class like that. --- Jojo 02:08, 23 July 2008 (UTC)
