TalkPHP - View Single Post - Dingo Framework

xenon · 03-24-2009, 05:09 PM

Quote:

Originally Posted by ETbyrne

I built the framework with all of that in mind. Placing the core functions in the $dingo sub-class allows you to have much more freedom than having all the sub-classes extending off the controller class. Dingo is very easy to use and is very powerful. Just because it doesn't work exactly like CI, doesn't mean it is bad.

You made a lot of blind assumptions in your post, if you ever saw a real Dingo application (like a shopping system, yes I made one) then you would understand why it works the way it does.

Sometimes being strictly controlled by a concept isn't such a good thing.

Btw, you weren't supposed to be able to access the site, looks like CPanel FAILED on the authentication. OK, I fixed the authentication, only authorized users can access now.

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.

Again, just to make it clear, it's not generally wrong that you extend the "core" library. It's that you "include" things that you never use. That's not the purpose of a library. At some point, that core class of yours will become larger than it is now, and all that functionality will not be required in every class you extend from it. Apart from that, the whole application will become visibly slower as its size increase if it doesn't have its base well thought.

I didn't make blind assumptions, I commented on the code I have read, and I tried to advise you as a subjective software architect. If you can't (or you don't want to) understand certain topics, then don't ask for feedback.

Your initiative is good, you just need to be more open to other people ideas (especially web developers - because they are your target).