This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I have one more question about OO design. In my previous post "Class relations mass" I got great assistance from Pete Stein. Thank You Pete, once more for that. Here I have similar problem, and I don't know how to apply entirely suggested logic. I will appreciate help on this.
Now I have class View, where GUI is implemented.
I want to do caesar encryption, and a few more.
I was thinking to create Caesar class, Playfair, ..., Encryption class,
and View. Is this a good thinking, or do I need only Encryption class
and put all cipher implementations in that one ?
This is the Encryption class, but I am not sure how to define encryption, to
say so ? Could You, please, help me somehow ?
Maybe I like a bit more second approach.
I will go with it!
This is not purely the decorator pattern though
Sorry, this is new concept for me. I google it, but haven't find much.
Could You, please, give me a short explanation of it ? After that I suppose
I will see why this is not a "purely decorator pattern".Thanks!