Bookmarks

Yahoo Gmail Google Facebook Delicious Twitter Reddit Stumpleupon Myspace Digg

Search queries

dbf2mysql parameter, WWWXXXAPC, wwwxxxAPC, How to unsubscrube from dategen spam, docmd.close 2585, WWWXXXDOCO, nu vot, dhcpd lease file "binding state", WWWXXXDOCO, how to setup procmail to process html2text

Links

XODOX
Impressum

#1: I just don"t have a great feeling about diving into ZF

Posted on 2008-01-06 10:05:22 by jonKushner

So, after the long debate about using ANY sort of external packaged
library besides my own hacked scripts, I decided to dig through the
source code of ZF and peek around. I was pretty impressed. It reminded
me a whole heap of college, specifically with Java and the zillions of
classes I would build with eclipse :)


Here's what I liked :

1/ Singleton patterns - Neat. I can see how this is quite resourceful.

2/ Definitely one of the best MVC Implementations I've seen...

3/ Double - confirmed why I love Zend Studio so much,


I really would like to use this package - and I could definitely see
it's benefits at work if we had it amongst a memcache server, but for
small jobs - there's just a whole other side of me thats aching
K.I.S.S.

Anyone ?

Report this message

#2: Re: I just don"t have a great feeling about diving into ZF

Posted on 2008-01-06 17:27:06 by todofixthis

Heya, Jon.

Including ZF with your project is fairly non-intrusive, as you can
include() what you need and not what you don't.

Projects do tend to grow over time, and it would be better to just
include the framework for when you need it rather than try to reinvent
the wheel for those "few times" when it might come in handy.

Report this message

#3: Re: I just don"t have a great feeling about diving into ZF

Posted on 2008-01-06 21:25:10 by jonKushner

On Jan 6, 8:27 am, todofixthis <inspi...@pbmods.com> wrote:
> Heya, Jon.
>
> Including ZF with your project is fairly non-intrusive, as you can
> include() what you need and not what you don't.
>
> Projects do tend to grow over time, and it would be better to just
> include the framework for when you need it rather than try to reinvent
> the wheel for those "few times" when it might come in handy.


Yeah. I think the problem is that ZF doesn't come off as a product of
individual packages but one entire solution that you must conform to.
I am going to treat it the same as the rest of my third_party folder.
We'll see how that goes :)

Report this message