Re: [PEPr] Changes in proposal for Yawp::Yawp2

Hi, Didierm

IMHO a feature that i'm looking for in a framework is a good mapping beetween requests and objects. HTML_FlexyFramework does it well.

I don't mean to mislead anyone; the only reason I call Yawp a "framework" is that there is no other good word for it. Yawp is not a framework, really, more of a foundation that aggregates or collects commonly-needed objects into a space away from the "main" part of your application. It lets you automatically configure a set of objects that you need throughout your application. It's not about controlling flow or mapping requests, only about providing a minimal but customized application foundation. Does that make sense?

The good point in yawp2 is that you can access encapsulated object and manipulate them without learning a new api (I like the concept of plugin, it lets me free).

I originally had a monolithic set of objects in Yawp, but Ian Eure had a great idea about allowing plugins; I reworked the idea, then reworked Yawp to fit it. This is the result.

I would love to find a frmwk that provides the best of the two worlds !! A pear "glue" for desired packages in a foundation framework is a real need from my point of view.

I agree; I think this new Yawp2 is generic enough to support any kind of PEAR object, and extensible enough to provide a base for a "real" framework. -- pmj