|Ⅰ||This article along with all titles and tags are the original content of AppNee. All rights reserved. To repost or reproduce, you must add an explicit footnote along with the URL to this article!|
|Ⅱ||Any manual or automated whole-website collecting/crawling behaviors are strictly prohibited.|
|Ⅲ||Any resources shared on AppNee are limited to personal study and research only, any form of commercial behaviors are strictly prohibited. Otherwise, you may receive a variety of copyright complaints and have to deal with them by yourself.|
|Ⅳ||Before using (especially downloading) any resources shared by AppNee, please first go to read our F.A.Q. page more or less. Otherwise, please bear all the consequences by yourself.|
|This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.|
Design Patterns (written by 4 internationally recognized experts in the field of object-oriented software design) has become one bible or must-have dictionary for object-oriented technicist. 23 patterns with the most valuable experiences it summarized and concluded from OOD have become the essential basic knowledge and vocabularies of software development technology exchange.
Design Patterns described a set of well designed and clearly expressed software design patterns in a classification way, which are especially useful in practical environments. Therefore, we can regard it as the beacon to guide readers through all kinds of mazes in software design, which condensed the essences of software development industry with dozens of years of design experience.
AppNee suggests readers: when reading this book, you’d better use all of it in the actual production, just see how patterns make our life easier, and make our products better. Otherwise, at last, you would think “I am sure few people could finish reading and understand this book. It is just like doctors’ graduation thesis, which is never written for human”.
BTW, you’d better be familiar with C++, and this book may require you to read dozens of times. Finally, when you were able to answer under what circumstances and why they need a pattern, you really spelled over this book.
// Table Of Contents //
- 1. Introduction
- 2. A Case Study: Designing a Document Editor
- 3. Creational Patterns
- 4. Structural Pattern
- 5. Behavioral Patterns
- 6. Conclusion
- Appendix A. Glossary
- Appendix B. Guide to Notation
- Appendix C. Foundation Classes
// Book Example Codes //
// Download URLs //
|If some download link is missing, and you do need it, just please send an email (along with post link and missing link) to remind us to reupload the missing file for you. And, give us some time to respond.|
|If there is a password for an archive, it should be "appnee.com".|
|Most of the reserved downloads (including the 32-bit version) can be requested to reupload via email.|