1.5w+
社区成员
- 全部
- VC综合技术
- 互联网技术
- MFC AppLauncher
- .NET 技术
- 界面
- 进程
- 算法
- 硬件/系统
- 数据库
- VC++技术资源
關于設計模式和分析模式
各位﹐我目前正巧接触了Design Patterns的一些東東﹐感覺很實用。但這方面的資料很少﹐無法深入了解。另外也很難找到有關Analysis Patterns 的資料.請大家一起探討﹗
...全文
当前发帖距今超过3年，不再开放新的回复
发表回复
Cline 2001-07-12
剛接觸,不太懂,聽課.
littleme741 2001-07-12
VirtualAlex，需要你的OICQ和MAIL以便有空一起探讨，你所讨论的问题我个人很感兴趣。
VirtualAlex 2001-07-12
另外還有Analysis Patterns的話題﹐請關注。
littleme741 2001-07-12
我只是提出几个问题吧：
1。bridge技术和接口技术各自的优缺点是否值得探讨？
2。如何从singleton技术出发考虑程序中pool的设计，比如在内存中建立缓冲池，在多网络连接时建立socket池，比如多线程设计中建立线程池等等。
3。希望大家结合自己实际的设计体会能举一些实际使用设计模式的例子。
这个帖子很好。
关注。
1。bridge技术和接口技术各自的优缺点是否值得探讨？
2。如何从singleton技术出发考虑程序中pool的设计，比如在内存中建立缓冲池，在多网络连接时建立socket池，比如多线程设计中建立线程池等等。
3。希望大家结合自己实际的设计体会能举一些实际使用设计模式的例子。
这个帖子很好。
关注。
y_pro 2001-07-12
要学这些东西，E文一定要好，因为大多文档都是E文的。
模式，其实是高级熟练工给低级熟练工用的东西^o^
模式，其实是高级熟练工给低级熟练工用的东西^o^
FG_Hope 2001-07-12
gz
bzshow 2001-07-12
Introduction
Design Patterns are intended to provide solutions to recurring design problems. Design Patterns play a major role in the design of complex systems using Object Oriented methods. Patterns help designers to decompose the system into set of co-operating objects instead of decomposing objects and trying to find relationships between them. In fact, most of us are reusing class relationships and object collaborations in our design without even realizing that we are actually using Design Patterns. Even though Design Patterns are available for a long time, the credit goes to Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides (Gang of Four -GoF) for coming out with a good collection of Patterns for common Design Problems. Their book, Design Patterns: Elements of Reusable Object-Oriented Software by Erich Gamma et al. (Addison-Wesley, 1995) was one of the first and best works done on Patterns.
In this article, we will be seeing what a Design Pattern is, followed by GoF's classification of Patterns and then jumping directly into the main topic of the article, MFC and Design Patterns. Portions of this article are extracted directly from GoF's book and throughout this article, I will be using the terms from their book.
Design Patterns
As mentioned earlier, the goal of Design Patterns is to provide solutions for recurring design problems. Design Patterns are meant to provide a common vocabulary for communicating design principles. They help designers to share their design using a common language. For example, you can tell your friend who knows pattern vocabulary that you have used Bridge Pattern in your design without explaining the details of class relationships.
So, how it all started? When Christopher Alexander and his colleagues tried to explain the architecture of buildings and cities, they used a Pattern Language. According to Christopher Alexander, "Each pattern describes a problem which occurs over and over again in our environment , and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice". This principle is not only applicable to the construction of building and cities, but it can also be extended to software construction using Object Oriented Design. When patterns are applied to software design, they take the name of Design Patterns. To summarize, Design Patterns provide proven solutions to recurring design problems.
**********************MFC and Design Patterns************************
As we all know, MFC is one of the popular class libraries used by C++ programmers. Nowadays, more and more commercial and business applications are developed using MFC. In fact, MFC and Visual C++ are the backbone for most of the recent Microsoft Products including Visual C++. The success story behind MFC is its class architecture and design principles adopted by the developers of MFC, which makes it one of the popularly reused library.
This main topic of this article is to show how patterns are used in MFC. We will be seeing the usage of three patterns in MFC library.
Creational : Singleton Pattern
First step in any MFC application is the creation of application object (object of class derived from CWinApp). There should be only one application object in an instance of MFC application. CWinApp is designed to make sure that only application object is present in a given instance. CWinApp and its descendants are called Singleton Classes. A class (CWinApp or its descendant) that assures a maximum of ONE object of its type at a given time and provides a global access point (AfxGetApp() method) to this object is a Singleton class.
As this principle is applied over and over again to solve recurring object "creational" problems, this becomes a pattern. Singleton Pattern ensures that a class only has one instance and provides a global access point it. The article Creating Singleton Objects using Visual C++ talks about different approaches for implementing Singletons.
Structural : Bridge Pattern
Bridge Pattern is all about decoupling an abstraction (interface) from its implementation so that the two can vary independently. In MFC, the process of storing/retrieving an object to/from a persistence mechanism (like a file) is called Serialization. MFC uses the Bridge Pattern to implement Serialization. CArchive and CFile classes implement object Serialization. CArchive class provides the interface for writing/reading an object to/from a persistence mechanism whereas the CFile and its sub classes provides implementation for different persistence mechanisms such as memory, disk file, sockets etc.
A CArchive object is configured with an object of class CFile (or a derived class) during its construction, from which it obtains the necessary information for serialization, including the filename and type of the requested operation (a read or write). Client performing the Serialization operation can use CArchive object without regarding the persistence mechanism implemented by CFile classes.
Behavioral : Observer Pattern
The Observer Pattern is intended to "Define a one-to-many dependency between objects so that when one object changes state, all its dependents are notified and updated automatically". An object that is subjected to change is called a Subject and an object that depends on the Subject's state is called an Observer.
MFC uses a Document/View variant of the Observer Pattern. MFC's famous Document/View architecture uses this variant. A document contains the data object and acts as a Subject. A view is a window object through which the user updates the document and it acts as an Observer. A document can have multiple views. Whenever the data in the document is changed by one of the views, it updates the document by calling UpdateAllViews method, with optional hint about the modification. To inform about the change to other views, the document object calls OnUpdate method for each view attached to it (except the view that called UpdateAllViews). Derived view classes can override the OnUpdate method and update themselves by querying the data from the document.
The article Applying Observer Pattern in C++ Applications talks about Observer pattern in detail.
Summary
Design Pattern provides a common language for designers and helps them to decompose systems into a set of cooperating classes and objects. They provide proven design solution to recurring problems. In this article, I have introduced the design pattern and how MFC is using some of the patterns in its design. We can easily find more and more patterns when we dig into MFC and its classes.
Design Patterns are intended to provide solutions to recurring design problems. Design Patterns play a major role in the design of complex systems using Object Oriented methods. Patterns help designers to decompose the system into set of co-operating objects instead of decomposing objects and trying to find relationships between them. In fact, most of us are reusing class relationships and object collaborations in our design without even realizing that we are actually using Design Patterns. Even though Design Patterns are available for a long time, the credit goes to Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides (Gang of Four -GoF) for coming out with a good collection of Patterns for common Design Problems. Their book, Design Patterns: Elements of Reusable Object-Oriented Software by Erich Gamma et al. (Addison-Wesley, 1995) was one of the first and best works done on Patterns.
In this article, we will be seeing what a Design Pattern is, followed by GoF's classification of Patterns and then jumping directly into the main topic of the article, MFC and Design Patterns. Portions of this article are extracted directly from GoF's book and throughout this article, I will be using the terms from their book.
Design Patterns
As mentioned earlier, the goal of Design Patterns is to provide solutions for recurring design problems. Design Patterns are meant to provide a common vocabulary for communicating design principles. They help designers to share their design using a common language. For example, you can tell your friend who knows pattern vocabulary that you have used Bridge Pattern in your design without explaining the details of class relationships.
So, how it all started? When Christopher Alexander and his colleagues tried to explain the architecture of buildings and cities, they used a Pattern Language. According to Christopher Alexander, "Each pattern describes a problem which occurs over and over again in our environment , and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice". This principle is not only applicable to the construction of building and cities, but it can also be extended to software construction using Object Oriented Design. When patterns are applied to software design, they take the name of Design Patterns. To summarize, Design Patterns provide proven solutions to recurring design problems.
**********************MFC and Design Patterns************************
As we all know, MFC is one of the popular class libraries used by C++ programmers. Nowadays, more and more commercial and business applications are developed using MFC. In fact, MFC and Visual C++ are the backbone for most of the recent Microsoft Products including Visual C++. The success story behind MFC is its class architecture and design principles adopted by the developers of MFC, which makes it one of the popularly reused library.
This main topic of this article is to show how patterns are used in MFC. We will be seeing the usage of three patterns in MFC library.
Creational : Singleton Pattern
First step in any MFC application is the creation of application object (object of class derived from CWinApp). There should be only one application object in an instance of MFC application. CWinApp is designed to make sure that only application object is present in a given instance. CWinApp and its descendants are called Singleton Classes. A class (CWinApp or its descendant) that assures a maximum of ONE object of its type at a given time and provides a global access point (AfxGetApp() method) to this object is a Singleton class.
As this principle is applied over and over again to solve recurring object "creational" problems, this becomes a pattern. Singleton Pattern ensures that a class only has one instance and provides a global access point it. The article Creating Singleton Objects using Visual C++ talks about different approaches for implementing Singletons.
Structural : Bridge Pattern
Bridge Pattern is all about decoupling an abstraction (interface) from its implementation so that the two can vary independently. In MFC, the process of storing/retrieving an object to/from a persistence mechanism (like a file) is called Serialization. MFC uses the Bridge Pattern to implement Serialization. CArchive and CFile classes implement object Serialization. CArchive class provides the interface for writing/reading an object to/from a persistence mechanism whereas the CFile and its sub classes provides implementation for different persistence mechanisms such as memory, disk file, sockets etc.
A CArchive object is configured with an object of class CFile (or a derived class) during its construction, from which it obtains the necessary information for serialization, including the filename and type of the requested operation (a read or write). Client performing the Serialization operation can use CArchive object without regarding the persistence mechanism implemented by CFile classes.
Behavioral : Observer Pattern
The Observer Pattern is intended to "Define a one-to-many dependency between objects so that when one object changes state, all its dependents are notified and updated automatically". An object that is subjected to change is called a Subject and an object that depends on the Subject's state is called an Observer.
MFC uses a Document/View variant of the Observer Pattern. MFC's famous Document/View architecture uses this variant. A document contains the data object and acts as a Subject. A view is a window object through which the user updates the document and it acts as an Observer. A document can have multiple views. Whenever the data in the document is changed by one of the views, it updates the document by calling UpdateAllViews method, with optional hint about the modification. To inform about the change to other views, the document object calls OnUpdate method for each view attached to it (except the view that called UpdateAllViews). Derived view classes can override the OnUpdate method and update themselves by querying the data from the document.
The article Applying Observer Pattern in C++ Applications talks about Observer pattern in detail.
Summary
Design Pattern provides a common language for designers and helps them to decompose systems into a set of cooperating classes and objects. They provide proven design solution to recurring problems. In this article, I have introduced the design pattern and how MFC is using some of the patterns in its design. We can easily find more and more patterns when we dig into MFC and its classes.
linux网络内核书合集01 本合集是本人搜集的关于linux网络内核的书籍，都是经典，包含：（1）Linux网络体系结构：Linux内核中网络协议的设计与实现.chm （2）Linux网络内核分析与开发.pdf （3）嵌入式Linux网络体系结构设计与TCP／IP协议栈.pdf （4）深入理解LINUX网络技术内幕.pdf 第一本是英文版chm格式，其余三本均为中文版，扫描清晰
HTML5经典中文教程大全-从入门到精通-含html5案例代码 HTML5经典中文教程大全
html5从入门到精通
含html5案例代码
HTML 5结构元素
这真是大快人心。目前，我们定义结构只能通过一个“万能”的div, 试图通过设置它的特性id的值如header, footer, sidebar等来分别表达头部，底部或者侧栏等。有了它们，代码编写者不再需要为id的命名费尽心思，对于手机、阅读器等设备更有语义的好处。HTML 5增加了新的结构元素来表达这些最常用的结构：
非常好验证码自动识别代码-C# OCR光学识别数字识别率达100 可用的验证码自动识别
非常好验证码自动识别代码-C# OCR光学识别数字识别率达100
自动识别邮政快递EMS验证码
自动识别顺风快递验证码
(亲测正确版)ASP.NET-c#-捕捉网页快照-网站截图-网站缩略图 (亲测正确版)ASP.NET-c#-捕捉网页快照-网站截图-网站缩略图
★★★★★★★★★★★★★★★★★★★★★★★★★★★
建立网站缩略图源码
网页快照ASP.NET网站截图
网页快照ASP.NET c# 输入网址获取网站图片
★★★★★★★★★★★★★★★★★★★★★★★★★★★★★★★★
网上流传了很多网站缩略图的asp.net,但是都无法使用，本人亲测，该代码进行优化，速度快，效率高，占内存非常少。
win7/8/10 CSF文件专用播放器——科健csf播放器 很多人反馈在win10下无法正常播放csf文件，附件中为科健最新CSF文件播放器，可以支持Windos7/8/10 系统，可以在win10下正常播放
中南大学大型数据库技术实验一、二 实验一：根据要求建立表，插入3个专业，每个专业不小于10个人，其中包括自己的信息。测试相关的完整性约束，并注意保留出错的提示，分析出错的原因。为每个学生建立相关用户，实现权限控制，每个学生可查询自己的信息，班长可查询本班所有学生信息； 为每个专业负责建立用户，每个专业负责可查询本专业所有学生信息。
实验二：设计与建立上课考勤表Attend_???。建立个人考勤汇总表stud_attend与专业考勤表major_attend。建立触发器，当对考勤表Attend表进行相应插入、删除、修改时，对stud表的sum_evaluation 数值进行相应的数据更新。
建立过程，生成某专业某时段（起、止日期）的考勤汇总表major_attend中各字段值，并汇总相应专业，将考勤分值的汇总结果写入到major表中的sum_evaluation中。
《无人驾驶车辆模型预测控制》电子书+matlab全代码 详细介绍了应用模型预测控制理论进行无人驾驶车辆控制的基础方法，结合运动规划与跟踪实例详细说明了预测模型建立、方法优化、约束处理和反馈校正的方法，给出了Matlab仿真代码和详细图解仿真步骤。
Activiti 工作流入门到大神 什么是流程、工作流作用、Activiti背景简介、Activiti流程设计器安装、Activity环境搭建、通过HelloWorld掌握 Activiti操作流程的步奏、常见API使用、流程部署管理(发布流程、查看流程定义、删除流程、查看流程附件)、流程实例管理(启动流程、查看任务、认领任务、办理任务、查看流程状态) 什么是流程、工作流作用、Activiti背景简介、Activiti流程设计器安装、Activity环境搭建、通过HelloWorld掌握 Activiti操作流程的步奏、常见API使用、流程部署管理(发布流程、查看流程定义、删除流程、查看流程附件)、流程实例管理(启动流程、查看任务、认领任务、办理任务、查看流程状态) QQ:362969068
