The Build Process
MappingOnce we have the idea, the design and the direction all planned out for our website or application.Next we need to map everything according to dynamics, like user control, data control and logic. With this in mind, we would become quickly lost if we do not have a method outside of the framework to make this easier. The sites pages, links, controllers, models and views are just a few. We still have forms, routing, data connections, libraries, images. EssenceOne does all this for you.
Unlike other Php Frameworks EssenceOne provides a Alphanumeric way to handle the entire file system outside of the Framework. This way it does not have to take up space with many extra tools, files and scripts you do not need within the framework. Frameworks like Zend and Codeigniter even though very powerfull are way to bulky and over run with scripts to be of any practical use for a dynamic site build. Many applications using these Frameworks are either too slow or extremely too difficult to learn or to be used fore rapid custom developments.
The Logical Build Process
EssenceOne allows you to efficiently and effectively develop applications still using Object Oriented Programming, but does it more in a non obtrusive way. Within EssenceOne the Routing is all done Alphanumerically Using Oop, but with a more basic approach to adding Modules, Views and Controllers. Everything is easily and rapidly staged for each Module you wish to add.
Modules are added simply by naming convections as numeric while the folders are staged alphabetically. This makes it both Alphanumeric and very easily managed. The procedure is very simple in that all you need to do is to copy and paste the new Class_Router into the next "m" folder and add the Modules numeric value at the end of it. We have three within the folders now as m1,m2,m3, so now we would add m4. Lets say we wish to add a Module for a Social Site for Albums. We know that Albums will need several pages for albums-list, album-create, album-delete, album-update, image-list and image-view. This will require 6 pages. So we will add a Class Router to a new folder named m4 and then add and stack our pages into the new Router. It is that simple.
Adding Dynamic Control
Now with the routing all done we can easily know where to place Models, Controllers and Views within the new Albums Class Router. This too is very easy in which we can stage and stack the the Controllers above the needed Views within the Class Router for automatic inclusion. And this allows us not to have to place includes methods above every single file to manage them. Now we can simply add the single Class Construct Method line into each view to execute the scripts needed for that View section. And that is all there is too it Folks !
Making Changes and Maintenance
Now with all files and folders managed Alphanumerically we can make changes fluidly. We can add a Albums Title and Description Controller by knowing that our new module m4 has Controllers in c4, and Views in v4. We create the View page, add the single class contruct line to it, we create the class to do the logic, and then add both their links into the Albums Class Router list with the Controllers Link placed above the Views Link to do it automatically for the new page. And that is it. It does not get easier or faster than this.
Now you have the tools to develop Dynamic and Custom applications easily and rapidly. Now let us think of a Teams Build Process. Now a Team Member can easily now that we have started a new Module named Albums. And he or she will know that it is in the files and folders as m4,c4,v4,l4, etc. And all they need to do is refer too the Albums Class Router to see everything in action and go from there.