Talk:A froggy visitor
(adding my thoughts about the visitor) |
|||
| Line 2: | Line 2: | ||
Just a thought. The *[[Visitor]] pattern is great especially if you decide to export the frogs into some other format you can add another type of exporter inheriting from the exporter. It also falls under * [[Open closed principle]] I was just thinking does this kinda go against * [[You ain't gonna need it]] where in this case the only advantage of this design is extensibility. There may be other advantages to the visitor that I havent seen so any other advantages please add below. Any thoughts. I feel that in this case the OCP overrides YAGNI. [[User: Paul Williams]] | Just a thought. The *[[Visitor]] pattern is great especially if you decide to export the frogs into some other format you can add another type of exporter inheriting from the exporter. It also falls under * [[Open closed principle]] I was just thinking does this kinda go against * [[You ain't gonna need it]] where in this case the only advantage of this design is extensibility. There may be other advantages to the visitor that I havent seen so any other advantages please add below. Any thoughts. I feel that in this case the OCP overrides YAGNI. [[User: Paul Williams]] | ||
| + | |||
| + | Another advantage of the design is that it decouples the XML code from the frog's attributes and serialisation process. This has extensibility as a side-effect, but also improves the modularity of the code. --[[User:Lukas Korsika|Lukas Korsika]] 00:48, 21 October 2010 (UTC) | ||
Latest revision as of 00:48, 21 October 2010
I began this page to explore an application of the Visitor pattern to the Frogs design. Coming soon, a critique of this design (some comments from Robert would make for an excellent addition). --TK 06:47, 2 August 2008 (UTC)
Just a thought. The *Visitor pattern is great especially if you decide to export the frogs into some other format you can add another type of exporter inheriting from the exporter. It also falls under * Open closed principle I was just thinking does this kinda go against * You ain't gonna need it where in this case the only advantage of this design is extensibility. There may be other advantages to the visitor that I havent seen so any other advantages please add below. Any thoughts. I feel that in this case the OCP overrides YAGNI. User: Paul Williams
Another advantage of the design is that it decouples the XML code from the frog's attributes and serialisation process. This has extensibility as a side-effect, but also improves the modularity of the code. --Lukas Korsika 00:48, 21 October 2010 (UTC)
