Zend Framework Critique

First Impressions

Loved the Filter and InputFilter, but then I realized that some parts weren’t finished and I told myself that I don’t have time for this crap. The code was several levels above my own, because I had no idea on how to use some of the components.

The first two I mentioned were easy enough to understand, but everything else fell into the category of ‘not going to be used’ or ‘interesting if I knew what the code meant’.

To spend a few weeks learning the framework and making it my own or create my own implementation that I would understand and actually probably use. I choose the latter, which I don’t regret, but the former would have been a far better usage of time.

Oh, Sweet Irony

I became curious on the progress made so far, so I took a look at it recently. To my surprise I found configuration classes that matched my development some time back.

Well, I had planned for the classes, but never finished the XML or INI one. I believe I will take a look at the classes later and once I am approved, I look forward to submitting patches for it.

I think I might give my database one. I would have to seriously change it to match the other classes. It would be interesting to see if anyone accepts it.

Yadis and Zend Framework

The Zend Framework has HTTP client classes that match the ones in the other Yadis Libraries. It wouldn’t be difficult to create a service and add it to the Zend Framework. However, I would have to write a proposal, which would have to be critique and then accepted.

I am currently using the Zend Framework to develop the Yadis Service. Going through the HTTP classes and the URI classes has kind of left me in thought shock. It is a lot to think over and I’ll probably have to create a few tests with the HTTP classes and see the interaction between the HTTP and URI classes to create the Yadis Service.

Bugs?

The biggest issue is whether or not there are bugs in the framework that I will have to immediately fix. I want the HTTP classes to just work and focus my attention on the Yadis Service.

I could give a patch of the bug fix, but it would have to be over the Mailing List until I sign the license and send it in.

Even if there aren’t any bugs, it is still my fear that I’ll probably run into them later.

Incomplete Components

I don’t like that some parts of the InputFilter and Filter are missing. I don’t feel like spending the time to implement the missing part and then have the code replaced later by another’s code.

What I’m saying is that I can justify spending (or wasting) time implementing my own wheel over fixing the wheel that already exists.

It will be hard to change, but from all of my reading, I would save a great deal of time using the Zend Framework, instead of creating my own wheel each time.

Browser Game Engine Using Zend Framework

Not yet, but I believe a time will come when I finish all of my other projects when I will consider it. After all, if I start using it now, then it won’t be a new thing that I have to learn when I start using it for the browser game.

The learning curve will be raised for the other developers that wish to work with it. However, it should be up to me to make it so that the others can implement features and mods as easily as possible.

That can be done built upon a layer of already created, tested, and tried Framework.

Ez Components?

I am not ready yet for Ez Components.

I am going to follow Ez development and see if any components interest me. If there comes a object based template system that replaces Smarty, then I’ll be completely up for it. I may even make it myself, but if I do, it will be proposed for the Zend Framework.

Once I master the Zend Framework, any others shouldn’t as difficult as they would be right now.

Possibly Related Posts:


2 Comments.

  1. Almost a year since this post, have you got any thoughts on when to choose Zend Framework and when to choose Ez Components?

  2. It would depend on your needs. I can’t tell you which to choose. I’ve since used Zend Framework a great deal and Ez Components, not so much.