Each and every aspect is vital. The heart and soul of coding consists in applying daily little choices. Let’s take into account the foremost necessary principles of this user-friendly framework:
1. Structured
Do not create points bulky and time-consuming, if they could be tiny and mobile. Simply give the tools, and let the client decide by themselves the way they want to use their choices. In Symfony, this suggests that clients begin with the foremost basic unit of information, at the time of making data structure. This method is additionally applied to the entire system. All parts of the Symfony are separate, made-to-order options, beginning with the structure of the info ending with the scheme patterns.
2. Transparency
Transparency is helpful for client. There’s a difference between usefulness and hindrance, and frequently few tricks seem to be generally the more problematic ones. The clients ought to be ready to observe, perceive and check their system. Sometimes for clients it attracts a lot of challenges than normal. However it additionally offers them a lot of power and suppleness. As an example, the template editing needs awareness of XSLT, however with this understanding, all the probabilities of language exposes, and in the end, any little bit of mark-up won't be detached without your understanding.
3. Uncomplicated
The uncomplicated answer is typically the correct one. A straightforward answer additionally permits gently sloping back or altering the path. This principle may be observed within the requirement to maintain the Symfony core as good as feasible and to attach the foremost unnecessary functions within the capability of extensions. This enables the core performing basic functions easily, developing, and Symfony framework programmers specializing in suppleness and responsiveness.
4. Relevance of Principles
Use the simplest answer, even though it isn't yours. Reward for clients will be two times: better, extra open system and also the capacity to gain knowledge. Symfony developers should be admirers of open, omnipresent, perpetually developing automated technologies. There are varieties of benefits for developers and clients of the system. As an example, the application of such customary technologies like XML and XSLT within the capability of the first language implies that the client’s information gained while using the system won't be useless in the near future. Symfony is compatible with several technologies supported by XML, like RSS, Atom, SOAP, and so on.
5. Growth
Look in front and not backside. Whereas sustaining harmony is important support for older versions, as this shouldn't hinder technological progress. Clients can profit a lot from the enhancements than from solidity. Let’s take the example of Symfony1 and Symfony2, as the backward compatibility between them was broken, however the result was a lot apt and a lot intricate system. Identical issue will certainly happen with the release of Symfony3. Whereas these transformations are not natural, they without any doubt develop the package and permit the community to progress.
