Design Patterns: Difference between revisions
Mr. MacKenty (talk | contribs) No edit summary |
Mr. MacKenty (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
[[file:Hierarchical-structure.png|right|frame|Design Patterns<ref>http://www.flaticon.com/</ref>]] | [[file:Hierarchical-structure.png|right|frame|Design Patterns<ref>http://www.flaticon.com/</ref>]] | ||
{{#incat:not_yet| | {{#incat:not_yet| | ||
<center> | |||
<blockquote style="padding: 5px; background-color: #FFF8DC; border: solid thin gray;"> | |||
[[File:Exclamation.png]] This page is not ready for student learning. It may have been created by a student, used as a placeholder by the teacher, or the teacher hasn't had time to review it. | |||
</blockquote> | |||
</center> | |||
|}} | |||
Revision as of 10:36, 22 February 2017
Design Patterns[1]
This page is not ready for student learning. It may have been created by a student, used as a placeholder by the teacher, or the teacher hasn't had time to review it.
Design patterns are solutions to recurring problems; guidelines on how to tackle certain problems. They are not classes, packages or libraries that you can plug into your application and wait for the magic to happen. These are, rather, guidelines on how to tackle certain problems in certain situations. Design patterns are solutions to recurring problems; guidelines on how to tackle certain problems[2]
This is a placeholder page. This content is not done yet