Dingo Framework - ALPHA Testing Open!
View Single Post
03-24-2009, 07:02 PM
how quixotic are you?
Join Date: Dec 2007
Location: Lapeer, MI
Well, I never said that every library must extend the controller (why on earth would you want to do that?!), I said exactly the opposite. Second of all, I never mentioned CI, nor any other framework. You just made an assumption, which, obviously, is wrong.
OK, I think I'll just have to admit that your post confused me a little. It all kinda ran together and was a little hard to decipher exactly what you where saying. For example, I have no idea what this means:
Second, every plugin and class you write - including Config?! - (you assumed) it must extend the DingoCore class, which is wrong.
It's that you "include" things that you never use.
Give me an example of this. The only thing that I can think of would be the MySQL settings, but that's only one small four key array. Hardly enough to bog an application down. Everything else is optional.
Perhaps you mean the routes and plugin configuration files? I could just put those in application/config/config.php but that might get a little messy. Worth a couple extra includes if you ask me.
I'm sorry if I sounded a bit rude, perhaps I should avoid responding to critical feedback while at school.
Actually I appreciate your feedback very much! Your views are a little different than my own so it kinda balances it out. If you want the user name and password to access the site (and documentation) say so and I'll PM that to ya.
Dingo Web Systems >
My Website >
View Public Profile
Send a private message to ETbyrne
Visit ETbyrne's homepage!
Find More Posts by ETbyrne