Re: PEAR application framework

The code isn't really ready for release, not even on a cheesy webpage. There are known bugs, and everything is changing rapidly. But I'll send you a .tgz of the current sources in a seperate mail, along with some instructions. It's basically an intranet which couples all of the elements mentioned, and provides authentication, users, and groups. The code is kind of skeletal now, but once it's fleshed out, I do intend to release it, probably on one of the non-pear package sites (as monolithic frameworks that require postgres and whatnot, like this one, don't belong in pear). Hopefully it will be of interest to developers confortable with PEAR that need to build robust web applications quickly. BTW, one thing I don't like about phrame: There's no View class. I don't know what's up with that. They apparently want you to redirect to some secondary script. Some of the source in the tgz I send you that solves this is basically a ripoff from this tutorial http://www.phparch.com/sample.php?mid=10, which I recommend you read. -Ron Martin Honermeyer wrote:

Hi Ron, I read the phrame documentation and am really excited about it. It looks like the perfect framework for future projects. In combination with some pear classes, particularly Flexy and Quickforms, it could be REALLY nice. If you could make those subclasses available to the public.. Greetz, Martin Ron McClain wrote:

I guess I don't understand why neither of those packages can be used for business use. That's news to me, as I'm working on a commercial application based on phrame (though am considering submitting some of the code to the phrame developers for potential inclusion, including a View class, and FlexyView and QuickformsView subclasses). I do believe that a good framework that is tightly integrated with pear would be of interest to many developers, myself included. Don't think it should go in pear though.. there are just too many different possibilities inherent in framework architectures, so concensus will be near impossible. If you are interested in a solution involving phrame/flexy/db_dataobjects/quickforms, let me know.. I've got some preliminary work done, and would be happy to collaborate. -Ron Matthias Nothhaft wrote:

Ron McClain wrote:

There's been some discussion of this on the mailing lists, and I believe that the consensus reached was that pear is not the place for such monolithic packages because there is not likely to be a consensus on which packages should provide the functionality, so we'd likely end up with competing packages like the templates situation. I think that pear is designed to be a set of small, reusable components that can be glued together by application developers in any way they see fit.

I agree. Let application devs decide what packages to use - or what framework to use ;-)

With that said, have you looked at phrame? http://phrame.sourceforge.net. I'm using phrame with flexy templates and quickforms for the views currently, and it works pretty well. There's also phpmvc (http://phpmvc.net), but I don't know much about that one except that it's modelled after Java Struts.

Well, I think both are not really interessting for business use and I think that is the use PEAR is designed for!? In fact I do not know any application framework being open source that can be used for a business solutions without getting mad! If I'm wrong, please send me the link. But this is just my personal opinion... (and that's why I'm working on an open source "enterprise app framework" based partly on pear) Regards, Matthias

-Ron Jackson Miller wrote:

I am sure I am not the only one who is interested in there one day being a PEAR application framework package(s). I am wondering who else has been thinking about this and if anyone is working on such a project. I would like a system that glues together the best of the best packages of PEAR. This would include a Templating package(Smarty? IT?), Auth package (probably LiveUser and something more simple for sites that don't need LU), database abstraction (MDB + MDB_Query_Tool), QuickForm, some XML stuff, SOAP, the MAIL API, etc. I am thinking that the glue that could pull this together would be a base module class that provides a consistent API for having pages interact with the packages listed above. There may even be a good way to have dependencies and some sort loadable module support. I understand that what I am describing is similar to projects like MVC.php, but there is a sense of security in PEAR and the PEAR process. Has anyone else been mulling this over? Has anyone began work on such a project? Is this a stupid or immature idea? Thanks, -Jackson