2020-05-07 04:11:54 +08:00
|
|
|
---
|
|
|
|
|
layout: pattern
|
|
|
|
|
title: Component
|
|
|
|
|
folder: component
|
|
|
|
|
permalink: /patterns/component/
|
|
|
|
|
categories: Behavioral
|
|
|
|
|
tags:
|
2020-05-24 17:14:42 +08:00
|
|
|
- Java
|
|
|
|
|
- Game Programming
|
|
|
|
|
- Decoupling
|
2020-05-07 04:11:54 +08:00
|
|
|
---
|
|
|
|
|
|
|
|
|
|
## Intent
|
|
|
|
|
|
|
|
|
|
> Allow a single entity to span multiple domains without coupling the domains to each other.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Applicability
|
|
|
|
|
1.You want to keep decoupled from each other in a class which contains multiple domains.
|
|
|
|
|
2.A class is too big and massive.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Reference
|
|
|
|
|
|
|
|
|
|
* [http://gameprogrammingpatterns.com/component.html]
|
