Design Patterns in ActionScript–Facade

本文讲述了GUI的历史及其背后的故事,从Xerox PARC的创新到苹果公司的商业化成功。同时介绍了Facade设计模式,它如何简化复杂子系统的使用,并通过汽车加速踏板的例子进行了说明。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

Have you ever heard Xerox PARC (Palo Alto Research Center, @see http://en.wikipedia.org/wiki/PARC_(company) )? This research center has many great innovations. GUI (Graphical User Interface) is one of them.


 

The history of GUI is an interesting story. After the PARC invent the GUI, they didn’t put this into business immediately. Sometimes later, a young man visited this center, and was shocked by the great innovations including the GUI. When the young man backed to his company, he put those ideas into their product, Macintosh, the first commercially successful product using GUI. And the young man, the CEO of that fruit company, began his legend in Silicon Valley.

 

OK, let’s turn to our topic today. Have you ever think about something under the GUI? Such as, when you click a button, how the computer will do? I mean the way, not the result. For example, when you click “open”, maybe it will show you a file chooser dialog. The file chooser dialog is the result, and the way to get the result maybe very complex. I think this is the great of GUI, you needn’t know the way, and you just need to know the result. All the details were covered by the system.

This situation was very common in our daily life. When you drive your car, you just put your foot on the accelerator pedal. Of course, you don’t know the details how the cat started, except you’ve ever studied it.

There is a pattern corresponding to these situations. It was called Façade.

Provide a unified interface to a set of interfaces in a subsystem. Facade defines a higher-level interface that makes the subsystem easier to use.

– By THE GOF BOOK

 

In the car example, you don’t know the inner structure of the car. And the car supplies you a higher-level interface, the accelerator pedal. Let’s mimic this example.

In order to make it easier to understand, we will only use three classes to illustrate this example, the Car, CarEngine and CarWheel.

You can see the diagram below.

clip_image002

< click to see oraginal image file>

Also, it can be described as blew.

clip_image004

< click to see oraginal image file>

From the client side, the car is a subsystem. And the client doesn’t need to know the internal structure of the car. All he need is the high-level interfaces.

You can see the source code for more information(download Download Full Project ).

As you see, this pattern is mainly use for reduce the complex of the subsystem, when you want to use some function provide by a subsystem. You don’t need to know the details about the subsystem, if you use this pattern. You just need to know the interfaces. It’s very helpful when you cooperate with others.

Enjoy!

内容概要:本文档定义了一个名为 `xxx_SCustSuplier_info` 的视图,用于整合和展示客户(Customer)和供应商(Supplier)的相关信息。视图通过连接多个表来获取组织单位、客户账户、站点使用、位置、财务代码组合等数据。对于客户部分,视图选择了与账单相关的记录,并提取了账单客户ID、账单站点ID、客户名称、账户名称、站点代码、状态、付款条款等信息;对于供应商部分,视图选择了有效的供应商及其站点信息,包括供应商ID、供应商名称、供应商编号、状态、付款条款、财务代码组合等。视图还通过外连接确保即使某些字段为空也能显示相关信息。 适合人群:熟悉Oracle ERP系统,尤其是应付账款(AP)和应收账款(AR)模块的数据库管理员或开发人员;需要查询和管理客户及供应商信息的业务分析师。 使用场景及目标:① 数据库管理员可以通过此视图快速查询客户和供应商的基本信息,包括账单信息、财务代码组合等;② 开发人员可以利用此视图进行报表开发或数据迁移;③ 业务分析师可以使用此视图进行数据分析,如信用评估、付款周期分析等。 阅读建议:由于该视图涉及多个表的复杂连接,建议读者先熟悉各个表的结构和关系,特别是 `hz_parties`、`hz_cust_accounts`、`ap_suppliers` 等核心表。此外,注意视图中使用的外连接(如 `gl_code_combinations_kfv` 表的连接),这可能会影响查询结果的完整性。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值