info/DesignPatternsPHP
1
0
Fork 0
mirror of https://github.com/DesignPatternsPHP/DesignPatternsPHP.git synced 2025-05-13 18:05:36 +02:00
Code Issues Projects Releases Wiki Activity

added README for Command pattern

Browse Source
This commit is contained in:
Dominik Liebler 2013-09-24 09:46:18 +02:00
parent 9e624afc26
commit c64c344f0f
2 changed files with 18 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
Command/CommandInterface.php
View File

@ -3,25 +3,7 @@
namespace DesignPatterns\Command; namespace DesignPatterns\Command;
/** /**
* Command pattern * class CommandInterface
*
* Purpose: To encapsulate invocation and decoupling
*
* We have an Invoker and a Receiver. This pattern use a "Command" to delegate the
* method call against the Receiver and presents the same method "execute".
* Therefore, the Invoker just know to call "execute" to process the Command of
* the client. The Receiver is decoupled from the Invoker
*
* The second aspect of ths pattern is the undo(), which undoes the method execute()
* Command can also be agregated to combine more complex commands with minimum
* copy-paste and relying on composition over inheritance.
*
* Examples:
* - A text editor : all events are Command which can be undone, stacked and saved.
* - Symfony2: SF2 Commands that can be run from the CLI are built with just the Command pattern in mind
* - big CLI tools use subcommands to distribute various tasks and pack them in "modules", each of these
* can be implemented with the Command pattern (e.g. vagrant)
*
*/ */
interface CommandInterface interface CommandInterface
{ {

17
Command/README.md Normal file
View File

@ -0,0 +1,17 @@
# Command
## Purpose
To encapsulate invocation and decoupling.
We have an Invoker and a Receiver. This pattern use a "Command" to delegate the method call against the Receiver and presents the same method "execute".
Therefore, the Invoker just knows to call "execute" to process the Command of the client. The Receiver is decoupled from the Invoker.
The second aspect of ths pattern is the undo(), which undoes the method execute().
Command can also be aggregated to combine more complex commands with minimum copy-paste and relying on composition over inheritance.
## Examples
* A text editor : all events are Command which can be undone, stacked and saved.
* Symfony2: SF2 Commands that can be run from the CLI are built with just the Command pattern in mind
* big CLI tools use subcommands to distribute various tasks and pack them in "modules", each of these can be implemented with the Command pattern (e.g. vagrant)