Not yet released, FLOW3 starts making noises on the mass: what’s TYPO3 up to?
As a result of the already proven TYPO3 CMS, the upcoming 5th version of the system is bringing a solid PHP framework, which can be used apart from the whole system for developing applications of any kind.
The FLOW3 subsite stats, against what’s commonly seen out there, FLOW3 is not a pick’n’mix store of motley components. It’s a framework which helps you with the infrastructure of your application. Object Lifecycle Management, Package Management, Resource Management and Security are on his home field. Real business logic is left over to third-party packages.
All the most common features we can find in other PHP frameworks are going to be provided by FLOW3, like MVC architecture, Validation, Filters, Persistence Object Manager and much more.
Next week, I’ll post a getting started with a simple application and provide my personal review of this framework, which – OMHO – is going to rock!
Sourcebits is investing efforts for making one of the best PHP frameworks even better. With a whole team of talented and skilled developers, we’re contributing to the framework using the best proven components we have developed based on our experience using the Zend Framework on our projects.
You can check out the proposals we have already submmitted for review here:
* Zend Calendar.
* Zend Template.
Hope you’ll enjoy! 
I found a very interesting article about Code Review that I’d like to share.
The article was written by Andrew Stellman and you can read it at Head First Labs in the address http://www.oreillynet.com/headfirst/blog/2008/09/how_to_hold_a_more_effective_c.html.
Enjoy!
“Well, I went pretty fine on my Object-Oriented experience. I’ve learned something about polymorphism, inheritance, encapsulation and now I really know how to extend a class! I’m ready for developing cool object-oriented applications.”
But what about the design? No, no… I don’t mean that design where you place the squares and circles in their places, draw lines, beautiful backgrounds and all those kind of stuff. I’m talking about Software Design. Design in terms of objects. Which objects to use, how and when to use, how the hierarchy would look like, which object should extend which object, when to encapsulate, when not.
It’s very common for developers to misunderstand Object-Oriented Programming with its basis concept (abstraction, inheritance, encapsulation, polymorphism, interfaces). Only because you know how to extend a class doesn’t mean that you really understand Object-Oriented Programming. It’s quite more than this.
First, let’s start with Design Patterns. Design Patterns are proven reusable solutions to solve a software design problem that other developers already faced before you. It’s not a kind of pre-cooked cake, where you just need to put in your heater for some time to get it done, but a description or template for how to solve a problem…
Subscribe to feeds
