 | News Feed |
Sections
|
Paul Jones:
MVC and ADR are User-Interface Patterns, Not Application Architectures
by Chris Cornutt January 26, 2015 @ 11:51:26
In response to a recent post from Anthony Ferrara about MVC Paul Jones suggests that Anthony's view that it and related structures "all pretend to be application architectures" is false.
The central mistake I think Anthony makes is near the end of this post, where he states (in talking about MVC, ADR, et al.) that "All Pretend To Be Application Architectures." That assertion strikes me as incorrect. While it may be that developers using MVC may mistakenly think of MVC as an application architecture, the pattern description itself makes no such claim. Indeed, Fowler categorizes MVC as a "Web Presentation Pattern" and not as an "Application Architecture" per se. [...] Fowler's categorization and description of MVC define it pretty clearly as a user interface pattern. ADR, as a refinement of MVC, is likewise a user interface pattern.
He goes on to talk more about the ADR (Action-Domain-Responder) pattern, how it's more of a user interface pattern as well and how that relates to using it for HTTP requests. He suggests that the definition from Anthony may be a bit too broad and proposes the alternative "All Are User Interface Patterns, Not Entire Application Architectures" to be a bit more specific.
voice your opinion now!
opinion adr actiondomainresponder mvc modelviewcontroller deisgnpattern userinterface
Coder on Code:
Design Patterns in PHP Adapters
by Chris Cornutt January 26, 2015 @ 10:46:42
The Coder on Code site has posted a new tutorial covering the Adapter design pattern in detail. They talk about what the pattern is, what it can be useful for and include some code to illustrate.
The adapter pattern also referred as the wrapper pattern, I find that wrapper is a more fitting name since it describes clearly what this pattern does; it encapsulates the functionality of a class or object into a class with a common public interfaces. [...] Adapters are one of the easiest patterns to comprehend and at the same time one of the most useful ones.
He starts with some of the basic definitions of terms involved in the pattern: client, adapter and adapteee. His example centers around a notification manager class that lets you switch types between Twitter, Email and SMS messaging. His initial code has all of the message types handled in one class method. He shows how to refactor this out to an interface and a set of child classes, each with the corresponding handling in a "sendNotification" method. These are then used by an adapter in the main class to send the given message. This simplifies the main messenger class and contributes to the overall improvement of architecture and testability of the application.
voice your opinion now!
designpattern adapter example introduction client adapter adaptee messaging tutorial
Community News:
Packagist Latest Releases for 01.25.2015
by Chris Cornutt January 25, 2015 @ 08:03:14
Recent releases from the Packagist:
NetTuts.com:
Design Patterns The Decorator Pattern
by Chris Cornutt January 23, 2015 @ 12:08:21
The NetTuts.com site has continued their series looking at design patterns and how they can be used in PHP. In this new post they focus in on the Decorator pattern, most commonly used to add functionality to a existing class (to "decorate" it).
Earlier in this series we explored both the facade and adapter design patterns in this series. Using facade, we can simplify large systems, and by implementing adapter we can stay safe while working with external API and classes. Now we are going to cover the decorator design pattern, which also falls under the category of structural patterns. We can use the decorator pattern when we just want to give some added responsibility to our base class. This design pattern is a great alternative to a sub‑classing feature for extending functionality with some added advantages.
They start with a problem that needs solving - sending an email with additional content not defined in the parent class. They show how to do something similar with child classes, but quickly find a limitation. Instead, they show how to use decorator classes and a simple interface to provide interchangeable classes that augment the contents of the email body as passed in via constructor injection.
voice your opinion now!
designpattern decorator tutorial series email body content
Zend Framework Blog:
Announcing the Zend Framework 3 Roadmap
by Chris Cornutt January 23, 2015 @ 11:57:10
The Zend Framework project has a new post to their blog today officially announcing the roadmap for version three of the popular PHP framework.
The most often-asked questions we get around the Zend Framework project include: Where is Zend Framework heading? When will Zend Framework 3 be released? What changes and enhancements should we expect? Since inception, our goal for Zend Framework has been to further the art of PHP and ensure our users concentrate on the business logic of their application rather than wasting time reinventing the plumbing. The plumbing is Zend Framework's job.
We have built an incredibly powerful framework with Zend Framework 2 that met its key goals of flexibility, consistency and testability. However, the world has changed since ZF2 was released, and the project needs to move with the times. With that in mind, we have gathered feedback from our users and core contributors to map the path forward. Zend Framework 3 will be an evolution from ZF2, concentrating on simplicity, reusability, and performance.
The post lists out a few of the things involved in this roadmap including separating components into individual, versioned projects and embracing the concept and functionality of middleware. If you'd like to get involved or just find out about the latest on this upcoming version, be sure you either join the zf-contributors mailing list or come to the #zftalk.dev channel on the Freenode IRC network.
voice your opinion now!
zendframework zendframework3 release roadmap
Stephan Hochdörfer:
Defining Phing Tasks in PSR-0 style
by Chris Cornutt January 23, 2015 @ 10:42:49
In his latest post Stephan Hochdörfer shows you how to define Phing tasks according to the PSR-0 autoloading format. Phing is a PHP-based automation tool that uses an XML configuration to execute a series of tasks.
Before anybody complains: I know that "as of 2014-10-21 PSR-0 has been marked as deprecated. PSR-4 is now recommended as an alternative." - Anyway I still think this little gem makes sense to be shared because a lot of people are probably not aware of it. I recently found out by accident that it is possible pass a task name in PSR-0 style to the "taskdef" task. In the old days you had to use the Java-like dot-style notation like this and also define the classpath to make sure the class could be loaded correct! This is ok if the task resides in the same project. If the task is located in a dependent package loaded via Composer this can get ugly.
The post is quick but provides two very handy code examples, one showing the old "dot notation" version and the other showing how to make use of the autoloader. The trick is in the classname value and using the full namespace/class name rather than the dot notation.
voice your opinion now!
phing build task psr0 classname path autoload
|
Community Events
Don't see your event here?
Let us know!
|
