- ThinkPHP Network |
- ThinkPHP
- Enterprise LAMP Support
- Mayflower
- PHP Training
- PHProjekt
- PHP-Center
- ThinkForge.org
Quicksearch
PHProjekt 6 - Developers Blog
What's new, part 2: New Features for developers
Friday, April 4. 2008
What's new, part 2: New Features for developers
While part one of What's new was dedicated to users, part two will give you a short overview what developer can expect from PHProjekt 6.
As a result of the long-lived, procedural and hard to mantainable code from earlier PHProjekt versions, we especially had developers in mind when creating the initial architecture of PHProjekt 6 last year. Thus, PHProjekt is based on well-known technologies including Zend Framework and Dojo. PHProjekt 6.0 is implemented using an model, view, controller architecture, with PHP in the backend and a rich-client frontend based on dojo, giving you a much easier to use interface. And for sure it's PHP5.
As a result of the long-lived, procedural and hard to mantainable code from earlier PHProjekt versions, we especially had developers in mind when creating the initial architecture of PHProjekt 6 last year. Thus, PHProjekt is based on well-known technologies including Zend Framework and Dojo. PHProjekt 6.0 is implemented using an model, view, controller architecture, with PHP in the backend and a rich-client frontend based on dojo, giving you a much easier to use interface. And for sure it's PHP5.
To make it easier for developers to access entries from the database, we implemented a ruby-on-rails like ActiveRecord pattern. This enables us
to create customized modules, featuring a simple "create, read, update, delete" actionset (also known as CRUD), very fast. Upcoming blog entries will
give you a detailed introduction.
Learning from the mistakes of earlier versions, we work hard to create a easy to access object-orietend layer, helping developers to add
tagging, search and filter features.
Not only the PHP site separates between data, and the actual view, but also the dojo client. To make the effort to build own modules small, we implemented a set of that are needed for basic modules, in the dojo frontend. So the developer doesn't have to touch much javascript and particurarly not the the actual data exchange with PHP using AJAX.
Let's give you a small overview:
We hope that we are able to give developers a good environment to extend PHProjekt to fit special needs.
In upcoming blog entries, I'll give you a detailed developer introduction into the structure of PHProjekt and explaing
our Active Recrod implmentation in details as well as talking about the advantages and drawbacks of the
new architecture.
David
to create customized modules, featuring a simple "create, read, update, delete" actionset (also known as CRUD), very fast. Upcoming blog entries will
give you a detailed introduction.
Learning from the mistakes of earlier versions, we work hard to create a easy to access object-orietend layer, helping developers to add
tagging, search and filter features.
Not only the PHP site separates between data, and the actual view, but also the dojo client. To make the effort to build own modules small, we implemented a set of that are needed for basic modules, in the dojo frontend. So the developer doesn't have to touch much javascript and particurarly not the the actual data exchange with PHP using AJAX.
Let's give you a small overview:
- Separation between code and content based on MVC
- Easy to extend module architecture
- Easy to access database tables using Active Record
- Fully object-oriented, based on Zend Framework
- Well documented API
We hope that we are able to give developers a good environment to extend PHProjekt to fit special needs.
In upcoming blog entries, I'll give you a detailed developer introduction into the structure of PHProjekt and explaing
our Active Recrod implmentation in details as well as talking about the advantages and drawbacks of the
new architecture.
David
Trackbacks
Trackback specific URI for this entry
No Trackbacks