Dingo Framework - ALPHA Testing Open!
View Single Post
07-30-2009, 12:08 PM
Join Date: Mar 2009
I am basing my information on the 5+ years experience I have working with PHP frameworks, this has nothing do with anything I have written.
The way errors are handled can be modified by editing the error view files. Critical errors will always stop execution of the PHP script and remove anything in the output buffer (besides what the error view puts in it).
Exceptions can be handled in the same manner as any other error and in such a way to be passed to a view.
And those developers are unreasonable in thinking I have time to explain every little thing in extreme detail.
I do not find wanting to understand the architecture for Route System unreasonable.
For your view it would not complicate things to add the theme based information into the load->view, it could simply be done by adding a if statement to prep end this path information before you pull a view script.
Btw I checked out the ACL portion of your framework and it's not really complicated at all. Actually it's quite simple compared to other aspects of a framework.
Is this for the LOC's not to get into this discussion but it performs the following...
1. Parents Checks (if exists) (Checks 1-4 For each Parent)
3. Role Specific Allow & Deny Permissions (if set)
4. User Specific Allow & Deny Permissions (if set)
It took 3 weeks development for a final version, I would like to know how you base this information?
I was not being rude to you at any point ... if this is how you see it, I'm sorry you cannot take it.
Need freelance Work?
I've been developing 5 years now, and I learn something new everyday
View Public Profile
Send a private message to ioan1k
Visit ioan1k's homepage!
Find More Posts by ioan1k