i’m java programer who accidently have to jump to PHP. I’m used to use some java framework and i see that sitemesh have it’s php version. But i still looking for display tag’s php version.

but i see that PEAR used widely here, also savant :D

did anyone tried zend framework? it’s look promising :D

i’ll take a try :D

thanks all

MDB2
HTML_TEMPLATE_IT
a few of those xml (serializer, util)

I like those.

This thread really got me to look up some things.

thanks guys/girls.

PEAR::DB for database abstraction. Yeah, it’s like killing a mosquito with a bazooka, but it’s easy to implement. (http://pear.php.net/)

PEAR::IMAGE for doing amazing dynamic graphs, very cool once you get it going!

DB_DataContainer for object persistence, although the project and website could use a lot more documentation. I am having trouble figuring a few things out, like sequencing ID’s. If anyone knows of another object persistance class that easy to implment, uses PEAR::DB, and doesn’t require a bunch of xml configuration, PLEASE post a link! (http://www.appelsiini.net/~tuupola/php/DB_DataContainer/)

BTW, cool site.

really like your site.

Just getting around to using PDO for my current project.

I use Code Igniter as framework (and basic templating sometimes) from the creators of the ExpressionEngine and pMachine.

And the fantastic Tiny But Strong templating system. Just one file and tons of possibilites, specially for work with designers.

Also I use:
PEAR::DB
PEAR::Date
phpMailer

What I like about using the libraries is that you have a development team on each project. This gives me a lift as we have just started looking at Authentication and Permissions for our software development. We designed exactly what we wanted from this and found out that LiveUser does exactly the same and as there is no reason to re-invent the wheel we decided on LiveUser. Four people work on developing this tool (we don’t even have 4 developers on our own software). Although the manuals (as with most opensource stuff) for PEAR are terrible spending time working out using it is less in developing something thats already freely available.

From a Business and Consultancy point of view using these libraries on small projects is a great idea. We used our own code on a few small websites a couple of years ago and now they need much more extensive functionality (i.e one needs LiveUser) and trying to integrate it in is proving a nightmare. Goingback over code that was done 2 years ago and not well documented is tough. The HTML Templating is so time consuming. Even though the projects were small, we didn’t think long run and thats the big mistake in development and roadmap of any software. Developing for now only gets you in trouble.

How easy would it be if for example if LiveUser were integrated but you were only utilizing small amounts of its functionality, but then in 6 months your client has grown and need you to help with permissions. Or the DB layer needs a connection to an Oracle DB rather than just MySQL or MSSQL.

I will not pay a developer to re-work his own work. If for his £45 -£55 per hour he could not build something forward thinking enough the first time I would not employ his so called expertise again. Obviously not everything can be built like that 100%, but I would expect a expensive developer to think forward.

PEAR in my Business Consultancy and Web Development Management eyes is forward thinking for many of the PHP functions that you would ever want to write. Utilize them even in small projects and your future upgrade/reworking for clients will be minimal.

Dont need to use the PEAR::Date think again and imagine you were 1 year down the line. Think about the client needs in 6 - 12 months and decide what its requirements will be. We did this with our software development of a Shopping Cart and CRM Backend Application and PEAR fits in now and will in the future (we hope). When we created the Cart it didn’t need the whole and extent of functionality that many of the PEAR Tools we integrated (i.e. we only need small pieces from PEAR::Date or the other various tools), but when we released “Our Cart Corporate Enterprise Edition” taddah, it took very little re-working to get a larger edition developed and working with bigger clients.

We use PEAR:
DB
Date
Template_IT
LiveUser
Liveuser_admin
SOAP
HTTP_Session

Also looking at
Web_Services_Google for one project