NYCPHP Meetup

[Petros Ziogas]

Actually I am referring to those exact features.
Zend decided to change the way a project is deployed using Zend Bootstrap,
Loader and Zend Tool.

So suddenly all documentation refers to code that looks completely different
than the code I wrote 6 months ago.

Zend has done a great job documenting all their classes but simply leaves
out the proccess of gluing those parts together. As I was developing a site
in 1.6 I managed to read my way through it and finally get the framework to
start and my classes to communicate and autoload. After that it was just PHP
as usual and I loved it.

So I get back to develop something completely different and I realise that
on 1.8 there is Bootstrap and Loader that completely change the way a
project should start. Also I must use a command line tool to add actions.
And the documentation just fails to mention what I can do if I don't want to
use Zend Tool. So now I have to read again to find out what Zend wants me to
do to get the application of the ground.Thank God there are people bloging
about it.

In my opinion changing the fundamental details that makes a framework
difficult to use, is a very bad move, and to be honest I thought that Zend
would do better than that.

Most challenging thing on Zend is to find out how to start (Bootstrap) and
get a simple page up showing (View) a database record (Db) to people that
have access to it (Auth and Acl). If you change a great part of that every 6
months what's the point?

note: I think there is great potential in using frameworks that is why I
used Zend framework and will use it again. I am just a little frustrated
these days with Zend_Tool and Bootstraping.

Petros Ziogas
http://www.royalblue.gr




On Sun, Jul 26, 2009 at 3:48 AM, Jake McGraw <jmcgraw1 at gmail.com> wrote:

> On Sat, Jul 25, 2009 at 6:39 AM, Petros Ziogas<petros.ziogas at gmail.com>
> wrote:
> > I have the exact same problem.
> > I find it a little immature to change the way a framework is deployed and
> > the setup after 6 months.
> > I created a nice CMS based on Zend 1.6 and now I see that 1.8.4 is
> > completely different and nothing works.
> > I am one step from going back to my own framework where I kept everything
> > under control.
>
> What do you mean nothing works? I'd be interested to hear what your
> issue is since I've been developing apps in using Zend Framework MVC
> since 1.5 and the only changes I've had to make are associated with
> Zend_Loader and adding support for Zend_Application_Bootstrap. I use
> the unofficial/official PEAR channel (http://pear.zfcampus.org/) to
> keep up to date.
>
> - jake
>
> > Petros Ziogas
> > http://www.royalblue.gr
> >
> >
> >
> > On Fri, Jul 24, 2009 at 9:12 PM, Ajai Khattri <ajai at bitblit.net> wrote:
> >>
> >> On Fri, 24 Jul 2009, Brian D. wrote:
> >>
> >> > This causes an issue with applications that have a long life-span.
> >> > They age very poorly. You basically have two choices:
> >> > 1. Upgrade your application to fit new framework API changes. This
> >> > leads to an inordinate amount of time upgrading, which means less time
> >> > you can devote to actually improving the application itself. You're
> >> > stuck upgrading existing functionality broken by new upgrades. In my
> >> > experience, frameworks tend to be brittle.
> >> > 2. Don't upgrade. You may miss out on security fixes or new
> >> > functionality. You may even have to patch the framework code to fix
> >> > security issues without breaking other functionality, which means now
> >> > you have undocumented changes. Documentation for past frameworks may
> >> > even be difficult to find (assuming it's even online).
> >> >
> >> > How do you guys handle this?
> >>
> >> I think it depends on the framework. symfony for example released 1.0
> >> in 2007 and announced they would support it until 2010. Even after 1.1
> and
> >> 1.2 were released, they introduced a compatibility option which required
> >> no porting of code even when running on the latest 1.2 code base.
> >>
> >>
> >> --
> >> Aj.
> >>
> >> _______________________________________________
> >> New York PHP User Group Community Talk Mailing List
> >> http://lists.nyphp.org/mailman/listinfo/talk
> >>
> >> http://www.nyphp.org/show_participation.php
> >
> >
> > _______________________________________________
> > New York PHP User Group Community Talk Mailing List
> > http://lists.nyphp.org/mailman/listinfo/talk
> >
> > http://www.nyphp.org/show_participation.php
> >
> _______________________________________________
> New York PHP User Group Community Talk Mailing List
> http://lists.nyphp.org/mailman/listinfo/talk
>
> http://www.nyphp.org/show_participation.php
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nyphp.org/pipermail/talk/attachments/20090727/7ca9ee92/attachment.html>