This page will be helpful for early adopters of the framework, ash.MVC.
- Do I need a framework at the first place?
- Are there any other PHP programming frameworks that exist?
- Why do I need yet another programming framework?
- Why do I use MVC design pattern in ash.MVC?
- What are the highlights of ash.MVC framework?
- What are the advantages of using this framework?
Do I need a framework at the first place?
Is there a need for a framework for programming when the language itself helps? Why should I learn about a framework additionally or abide by it when I am proficient with the language, and I can exploit the power of the language well. This point will require volumes to answer, and particularly controversial and challenging to computer scientists all along. So, I am not going to delve into this general question; instead would like to narrate the following situation that PHP programmers deal with in their daily life.
PHP Programmer’s “Dusk Dilemma”: After working the whole day with undistracted attention, the programmer withdraws at the dusk to feel uncertain and worried about the scalability and security of application, and its maintainability. People say, PHP scripting inherently encourages swirling code base and induces fallibility in the long run if the concerned programmer does not give adequate (or rather additional) personal attention to the structure of code. And it is difficult! Isn’t it?
I hope the above example sets the tone and makes a point to justify the need of a framework.
Are there any other PHP programming frameworks that exist?
Now that there is an appreciation of the need of a framework (ref: previous FAQ item), we may now look if there is a framework that exists. Alas! So many if we make a simple search at Google (if you were not convinced of my above reasoning (ref: previous FAQ item), you may now be tempted to accept).
Yes, there are numerous frameworks that exist and are in action with various real-life applications.
Why do I need yet another programming framework?
This new framework brings in those advantages that are not either present or are not easily realized in practice with other frameworks: Simplicity, flexibility, scalability, and short learning curve.
In reality, most of the available PHP frameworks are modeled after those for java even though the architecture and programming practices are widely different. In such cases, the schemes require a long learning curve, and are full of “only-applicable-to-this” tricks. Moreover, existing models are tightly integrated with a set of rigid rules, use numerous predefined files -- thus limiting themselves to fulfill specific requirements on case-to-case basis; also require significant time for desired customization for a new situation of application design.
In short, the new framework is overdue. After all, every programmer feels the need of a simple programming framework to produce a code base quickly without sacrificing the quality and robustness of the end application.
Why do I use MVC design pattern in ash.MVC?
MVC, Model-View-Controller, is a successful design pattern (a set of general rules regulating the program design and implementation process to achieve a programming task). The design of PHP language, particularly PHP5, encourages MVC pattern. So, we adopt MVC – it is as simple as that.
What are the highlights of ash.MVC framework?
In the recommendations of this new framework using MVC pattern, effort has been made to incorporate a generic approach towards application development, and simple and easy-to-understand set of guidelines. Highlights of ash.MVC are:
- No proprietary templating; instead, simple PHP print statements, simple loops or control statements are used. It is to be noted that adopting a proprietary templating rules requires higher learning curve and time.
- A few broad guidelines are provided about adopting folder structure, naming and coding conventions. This helps to make the communication between programmers using ash.MVC framework easier (to avoid chaotic situation resulting from individual preferences and coding styles), and above all, it helps to keep code base readable, maintainable and clean.
- Clear and easy-to-learn schemes are provided for critical areas of application development like security, user authentication, control of data flow, and scalability.
- The framework guidelines are applicable in case of developing searchable public web pages too.
What are the advantages of using this framework?
Advantages are many and are quite important for a PHP application development project.
- Security setting, role-based privilege is properly implemented at Controller level.
- Business logic is separated from Presentation logic successfully.
- Well-defined execution path determined by the Controller requires least number of lines of code to achieve certain tasks.
- Business logic class makes data handling more secured.
- Easy presentation management as we don't need any special framework like SMARTY (not all web servers’ support) or Fast Templates.
