Off-topic,
Like me from small to high dozen 0 separated people, write articles, really is impatient, sorry.
Although I also cottage many PHP framework, but was the object of the cottage, the favorite is windframework.
Yii is actually better, but too chatty.
Windframework is a lightweight PHP open source framework, with component factories as its core, providing applications such as MVC, data persistence, and view template engines.
Its front-end controller, the concept is more complex.
Model-view-controller (MVC)
The wind framework provides the underlying web MVC support (see Component Package wind/web/).
Wind MVC provides a clear, loosely coupled implementation based on the framework's core technology. It uses the front-end controller mode and supports a powerful interception filter chain strategy. It is easy to centralize control logic in a completely loosely coupled manner. In addition, wind MVC provides features such as ' template-driven ', ' request redirection '.
Directory path aliases and import class loading
We can register the directory path to the system and use aliases for its definition. The wind framework loads the class via the Import method (only supports class loading) and provides autoload support. Using the path alias and import mechanism simplifies the use of the path, the project deployment, that is, the loading mode greatly improves the efficiency of class loading.
Component Factory mechanism
The component factory mechanism is the foundation of the wind framework core. It is based on the technical implementation of IOC control inversion and Dependency injection, which provides a loosely-coupled component management mechanism for the entire framework, separating the dependencies and configuration of classes from the program logic. The component factory mechanism provides rich feature support: component (Create, logout, get) management, multi-life cycle, configuration resolution management, Proxy mode, lazy-init delay load, etc. The component factory mechanism unifies and simplifies the development and use of components.
View management, multi-template engine support
Based on the powerful component mechanism of the wind framework, view management provides support for multi-template engines. The Wind Viewer package provides a ' windnormalviewerresolver ', ' windviewerresolver ' two view rendering engine. It also supports third-party rendering engines such as ' Smarty ' and so on. The framework defaults to view rendering with ' Windviewerresolver ', which supports template compilation and label expansion.
Themes and Skins (themes)
The wind framework supports simple themes and skin management, and the app can easily implement multi-style support and switching by setting themes for the view.
Layout Management of template Views (layout)
Layout management implements a unified layout that can be a template by defining a layout template file for your app. The wind framework supports defining a layout template for the entire application, as well as defining a different layout template for each operation. By default, the system does not turn on layout management, and you can turn on layout management by setting up layout files.
Template Label Support
The wind framework defaults to the ' windviewerresolver ' view renderer, which supports template compilation and configuration-based custom label extensions. Developers can customize the template tags as needed. The wind framework implements several common tags by default: Action, echo, Lang, template, token, and so on.
Data output security filtering and data formatting support
Based on the template labeling system, the wind framework enables powerful data output support: Safe output filtering, data formatting, and more. Based on this feature, developers can easily make variable output in the desired format on the page without worrying about security issues or data formatting issues.
Cache
The wind framework provides the cache component and cache support by default. The cache component uses an interface-oriented component design approach, providing the cache user with a standard cache interface definition, as well as implementation of a variety of cache scenarios.
Db
Simple and efficient Data persistence layer scheme ' windconnection ', which is a PDO-based data persistence solution. It supports the ' windconnection ' simple link, ' Windconnectionmanager ' Distributed link management of the two link modes. The two options allow for seamless switching.
preprocessing and post-processing of requests (filter chain)
The wind framework uses the Interception filter mode to support the interception and policy deployment of request preprocessing and post processing. The developer can easily use this feature to add, delete, and modify control logic code in the preprocessing or post-processing location of the request, based on the configuration.
Routing protocol chain, multi-routing protocol support
Routing is an important component in wind MVC, and the wind framework provides routing support, which is implemented in the filter chain mode, where a router can mount a variety of routing protocols. The program loads the routing protocol in the order in which it is mounted until it finds a routing protocol that can handle the current request.
Form form Objects & validation
Web MVC provides support for form processing by default. The developer can create a form object for a request, and the system will initialize the form object and complete the form validation before processing the specific operation. Developers do not need to manipulate large amounts of validation of form data in code logic, simplifying development.
ErrorHandler Custom error Handling handles
A custom error handle is another feature support provided by Web MVC. The wind framework defaults to MVC, which provides the error handling handle ' Winderrorhandler ', and the default error page points to ' Web/view '. Developers can use the configuration to point to a custom error handling handle, define ' ErrorHandler ' for each module, or customize ' ErrorHandler ' for each action. The wind framework provides powerful and flexible support for custom configurations.
Anomaly System and Logger log
Two basic types of exceptions: ' Windfinalexception ', ' windexception '. The former is the ultimate exception, throwing the class exception means that you do not want the exception to be handled directly by the system, the latter is a generic exception type, most custom exceptions need to inherit the exception type, the exception will be handled by the system's error system. Logger components, by invoking the logger component developers can easily output log information, support classification, packet output. Only localized file log records are currently supported.
Multiple Development mode support
Wind_debugwind_debug supports multiple modes: window, log, Window&log. Developers can define wind's operating mode by setting the value of the constant ' wind_debug '.
Internationalization (i18n)
Simple internationalization support: variables, language templates, and more.
Safety (Security)
Input-output security filtering, which transparently handles data security through built-in component management. The wind framework also provides security safety kits such as encryption, decryption, token, and so on.