Decorator pattern

In object-oriented programming, a decorator pattern is a design pattern.

Contents

1 Introduction 2 Motivation 3 Applicability 4 Example 5 See also 6 External links

Introduction

The decorator pattern allows new/additional behaviour to be added to an existing method of an object dynamically. This is done by wrapping the new "decorator" object around the original object. This is generally achieved by passing the original object as a parameter to the constructor of the decorator, with the decorator implementing the new functionality. It should be noted that the interface of the original object needs to be maintained by the decorator.

Decorators are alternatives to subclassing. Subclassing adds behaviour at compile time where as decorators provide a new behaviour at runtime.

This difference becomes most important when there are several independent ways of extending functionality. Since (in most object-oriented programming languages) classes (computer science) cannot be created at runtime and it is typically not possible to predict what combinations of extensions will be needed at design time, a new class would have to be made for every possible combination. By contrast, decorators are objects, created at runtime, and can be combined on a per-use basis. A superb example of the decorator pattern is the Java I/O Streams implementation.

Motivation

As an example, consider a window in a windowing system. To allow scrolling of the window's contents, we may wish to add horizontal or vertical scrollbars to it, as appropriate. Assume windows are represented by instances of the Window class, and assume this class has no functionality for adding scrollbars. We could create a subclass ScrollingWindow that provides them, or we could create a ScrollingWindowDecorator that merely adds this functionality to existing Window objects. At this point, either solution would be fine. (Another solution is to simply modify the existing Window class, but this is not always possible—we might not have access to its implementation, or we might be adding storage overhead for new functionality that the majority of objects will not use.)

Now let's assume we also wish the option to add borders to our windows. Again, our original Window class has no support. The ScrollingWindow subclass now poses a problem, because it has effectively created a new kind of window. If we wish to add border support to all windows, we must create subclasses WindowWithBorder and ScrollingWindowWithBorder. Obviously, this problem gets worse with every new feature to be added. For the decorator solution, we need merely create a new BorderedWindowDecorator—at runtime, we can decorate existing windows with the ScrollingWindowDecorator or the BorderedWindowDecorator or both, as we see fit.

Applicability

Consider the webpage you are currently viewing. The webpage itself displays the information you need, but your web browser knows nothing about the content. It is likely that this webpage doesn't fit in the entire browser area and a scrollbar is required to show the information. The web browser doesn't need to assume that all webpages will require a scrollbar and it certainly should never assume a scrollbar is never needed. Mozilla and Netscape browsers will display the scrollbar only if it is necessary and hides it if it is unnecessary. In this case, the scrollbar is the "decoration" to the webpage. It takes care of whether or not it should be displayed dynamically as opposed to statically forcing the webpage display to be a subclass of the scrollbar display. Thus, it is up to the scrollbar to decide whether or not it should display itself (instead of trying to force that responsibility on the webpage or on the external parts of the web browser).

Example

FIXME

See also

• Abstract class
• Abstract factory

External links

• Description from the Pattern Digest (http://patterndigest.com/patterns/Decorator.html)
• Description (http://home.earthlink.net/~huston2/dp/decorator.html) by Vince Huston
• Sample "Chapter 3: The Decorator Pattern (http://www.oreilly.com/catalog/hfdesignpat/chapter/ch03.pdf)"
• Sample Chapter "C# Design Patterns: The Decorator Pattern (http://awprofessional.com/articles/article.asp?p=31350&rl=1)" by James W. Cooper
• A PHP approach (http://phppatterns.com/index.php/article/articleview/30/1/1) and "Redecorated (http://phppatterns.com/index.php/article/articleview/92/1/1)"
• A Delphi approach (http://www.castle-cadenza.demon.co.uk/decorate.htm)
• Article "Three approaches for decorating your code (http://www.javaworld.net/javaworld/jw-04-2004/jw-0412-decorator.html)" by Michael Feldman
• Article "Using the Decorator Pattern (http://www.onjava.com/pub/a/onjava/2003/02/05/decorator.html)" by Budi Kurniawan
• Article "The Decorator Design Pattern (http://exciton.cs.rice.edu/JavaResources/DesignPatterns/DecoratorPattern.htm)" by Antonio García and Stephen Wong
• Application (http://javalab.iai.uni-bonn.de/research/gilgul/tutorial.html#1) with Gilgulde:Dekorierer

es:Decorator (patrón de diseño)