It’s time to release a new P4A 3 preview package! This mainly is a bugfix release, but we’ve a few interesting things out there, I started coding the new exception based error management and started porting some P4A components to it (or to “trigger_error” depending on the specific case). Zend Framework was updated to 1.0.4 and this raised a few issues I fixed (hope I found them all). Due to high demand I also worked on P4A_Sheet, supporting anchoring for text strings and re-creating the setFree method.
Here you have the full changelog:
– P4A_Toolbars code was refactored using P4A chainability
– a bug with P4A_Full_Toolbar and P4A_Simple_Toolbar about delete was solved
– a bug with P4A_DB_Source::deleteRow was solved
– P4A_Widget::requireConfirmation() now trigger an error if addAction wasn’t called before
– P4A_Exception class was added
– P4A_Exception_Handler now replaces PHP’s default exception handler
– a part of P4A_DB_Source error management was ported to the new error handlers
– Zend Framework was updated to 1.0.4
– P4A_DB_Source::load() now returns $this thus is chainable now
– P4A_DB_Source::_composeSelectCountQuery() now always encapsulate the complete select query (without order clause) in a second count query
– translations were synched with launchpad
– P4A_DB::query() method was added
– P4A_Mask error management was ported to exceptions
– p4a/libraries/standard.php was renamed p4a/functions.php
– P4A_DB_Select class was removed ’cause unused
– code reference was organized in packages
– P4A_Sheet was ported to the new error handling
– P4A_Mask::setFocus() method now checks if the passed object is an instance of P4A_Object, otherwise does nothing
– P4A::getFocusedObjectId() method now checks if the “active_mask” object exists, otherwise returns null
– P4A_Sheet::anchor() method now supports text strings and not only widgets
– P4A_Sheet::setFree() method was added
You know P4A has a new fantastic spanish community, they created a new forum on google groups. I has a discussion with some users saying that sourceforge forums are ineffective because of the answers orders and few other things. We’ve to consider that, with P4A 3, 99% of the forum posts will become outdated, so the question is should we move P4A forums to google code or another service?
We always used SF forums because it’s one of the best ways to make the project activity rate raise and let P4A be one of the most active project all over SF. Moving the forum elsewhere will drop this positive effect. We also have to keep this is mind.
Please let me know your considerations!