Dingo Framework - ALPHA Testing Open!
 

Today I launched http://www.dingocode.com for my new Dingo PHP Development Framework. Right now the site is only open to ALPHA testers. If you want in on the ALPHA testing then just leave a comment here, I will then send you a PM with the user name and password to access the site.

All feedback is much appreciated! :-D

You can also follow Dingo on twitter > http://twitter.com/dingocode

I believe you tried to assemble an OOP system there, but it looks like you have left all the OO concepts behind. For example, there is no abstractization. Second, every plugin and class you write - including Config?! - (you assumed) it must extend the DingoCore class, which is wrong. I'll give you an example: you want to create a logging "plugin". In that case, you would need to extend the DingoCore class, right? Well, in the case of a logging plugin, you wouldn't need the templates methods and all that stuff in the core class. That's useless overloading, thus longer loading times. Same applies to the config class. You don't need to parse templates or load models or plugins in a config file, do you? I wouldn't go there, anyway, but probably you have a different motivation and config files mean something else to you that they mean to me.

This is just a scratch of the surface, I'll probably be back with more later...

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).

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:


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.

Can i get a alpha code?

Sure thing tego!

I don't really wanna be an alpha-tester(what exactly do they do??).
However I would really love to see how it looks and see if it's worth putting my head into it. I'm about to start some projects, so I'm checking out some various frameworks.

Basicly - I wanna be alpha-tester, but not actually "bug test" the framework, if you see the difference

Tanax, you can be a committed as you want. I'm not going to force anyone into giving feedback or doing intense testing. I wasn't really expecting anyone to bug-test the framework. I think that after personally building many complex websites with it I can say with confidence it is relatively bug-free. I'm mainly looking for constructive feedback on possible changes, additions, or things that should be taken out.

I'll shoot you over a user name and password right away!

Is this going to remain closed source? I'd like to take a look.

I intend the Dingo Framework to remain somewhat not open source, but always free. You can look at the license page (http://www.dingocode.com/framework/other/license) and see all the details. I know, it seems like a strict license for this sort of thing, but I just can't stand the thought of someone copying my work... Happened once already.

Salathe, I'll shoot you the login information, check your PM box.

Thanks everyone for the help!

Can I grab a login, I'm intrigued.

Ouch. A vanilla install shouldn't look like this:



P.S. Where would you rather have feedback? Ideally a place where multiple people can participate and collaborate.

Right here would be fine.

@sketchMedia Sure thing, I'll send you one right away

Hey everyone, just a heads up earlier today I added two new libraries/classes to the framework. A file manipulation one and an email one. They are located in the system/classes folder and can be loaded like so:

shoot me a pm I'm curious

Edit:

I believe you have forgotten to include the necessary variable checks, in E_STRICT mode variables not previously set cannot be called without err.

Edit:

The post, get, files, cookies, request functions are all rather superfluous if they've no option to clean them of sql injection or xss attacks. Also, they do not check to see if the variable is actually there. This shall cause errors in certain servers.

Edit:

Is it my understanding that calling a variable within a class which has not been previously declared is slow then calling a variable which has already been declared but only by a slight ammount still it is best practice to declare variables you shall use.

I'd like to check it out :) I started to when you accidentally left it un-password protected. =D

Good catch, will do.

Those functions are there for forward compatibility, in other words I'm planning on adding xss filtering or something of the sort in the future.

OK, I'll see about that. I've developed a bad habit of not declaring variables in classes. Do you mean in the controller functions, or just in general?

Sure thing

I wouldn't mind to have a look and see I can spot anything the others havn't, if you could email me the login it would be faster as I check my email more offen than my pm inbox here =D

kalle at php dot net

Offtopic- How did you get @ php . net mail? 8-)