5.9-SERIESSupport for PHP 5.3.12 / 5.4.2at 2012-05-04 in 5.8-SERIES, 5.9-SERIES, PHP5 by friebe With the release of PHP 5.3.12 and PHP 5.4.2, the current 5.8-SERIES's supported PHP versions now include all of PHP 5.2.10 through PHP 5.4.2. The 5.9-SERIES supports all PHP versions between PHP 5.3.0 and PHP 5.4.2. New util.UUID classat 2012-04-23 in 5.9-SERIES by friebeIn the course of implementing RFC #0229, the UUID class from the old org.ietf package was moved to the XP Framework. At the same time, its API was changed and now not only implements time-based UUIDs (v1), but also name-based (v3, md5 and v5, sha1) as well as random (v4) UUIDs. For details on the new API, see here. Heads up: If you have previously used the old UUID class, please be aware that you will need to change your code! RFC #0210 prerequisitesat 2012-04-15 in RFCs, 5.9-SERIES by friebeA while ago we blogged about the cleanup work in xp.contrib. This was now structured in three different pull requests: Renaming This is handled in pull request #12 and includes renaming of the ecma, xmlrpc, img, google, microsoft and cyrus packages. Removing This is handled in pull request #13 and includes removal of the ajp, tar and gettext packages. IETF package split RFC #0229 consists of two parts:
Split xp.contrib's "ietf"at 2012-04-15 in 5.9-SERIES, RFCs by friebeScope of Change The UUID class will be merged into XP Framework core (as util.UUID) and the ietf package will be renamed to punycode. Rationale The "ietf" module contains both PunyCode and UUID implementations, which are completely unrelated. Read the full RFC here 5.8.4RC3: JSON, Configuration, Properties and FCat 2012-02-03 in 5.8-SERIES, 5.9-SERIES, Announcements, Releases by friebeWe would like to announce the immediate availability of the third release candidate for XP 5.8.4. On top of the second RC, we have included JSON serialization for objects, the possibility to supply multiple configuration sources for both XPCLIs and web applications based on RFC #0221, extended the util.Properties class to be case-insensitive when parsing boolean values and added a method lang.reflect.Field::getTypeName() for forward compatibility with the upcoming 5.9-SERIES. You can download and install as always: $ cd ~/xp Enjoy RFC #0210: Separate contrib & framework versions - vote please!at 2012-02-01 in RFCs, 5.9-SERIES by friebeWe've worked on RFC #0210: Separate contrib and framework versions, the goal of which is to separate framework and contrib. library versions. While today, all libraries are versioned alongside the framework, e.g. xp-rt-5.8.4 and xp-contrib.stomp-5.8.4, the libraries will have separate versions in the future and instead a pointer to the framework version (range) they depend on. We've therefore gathered all the current libraries inside the xp.contrib repository and have reconstructed their changelog from SVN and Git commit history. The RFC includes these and the version numbers we can derive from that for each library. Now while we were doing that, we also noticed quite a bunch of deprecated, badly named, unmaintained and otherwise outdated libraries. For the most obvious, we've created RFCs on how to further proceed with them. Please give your votes by adding "+1" or "-1" (and optionally, a reason) as to these proposals in the issue comments.
Thanks! RFC #0218: Parameter annotationsat 2012-01-28 in 5.9-SERIES, RFCs by friebeScope of Change Annotations on method parameters will be allowed. Rationale Originally motivated from XP Framework's pull request #33 - Stubbles IoC container and dependency injection. Read the full RFC here. RFC #0231: Remove xp.contrib's "dba" moduleat 2012-01-22 in 5.8-SERIES, 5.9-SERIES, RFCs by friebeScope of Change The module "dba" will be completely removed. Rationale The io.dba classes where deprecated in the 5.8-SERIES and moved to the ports repository (what is now "xp.contrib") for backwards compatibility on 2010-02-14, almost two years ago at the time of writing. Read the full RFC here RFC #0184: Drop SAPI feature alltogetherat 2012-01-21 in 5.9-SERIES, RFCs by friebeRationale The sapi feature was initially introduced to offer a way to extend the XP framework's core code, provided by lang.base.php, in a manner similar to that file, eg. without having to encapsulate that code in a class. Now, we think code should always be loaded as a class, which bring several features like having an associated classloader. Functionality Functionality provided by one of the XP framework's sapi files will be migrated to be provided by regular classes, preferrably backwards compatible. Read the full RFC here PHP Namespaces and the XP Frameworkat 2012-01-06 in RFCs, PHP5, Examples, 5.9-SERIES by friebeWith the implementation of RFC #0222, we have added optional PHP namespaces support to the XP Framework. Optional means the XP Framework itself will neither depend on PHP 5.3 (still supporting PHP 5.2.10 upward at least for the 5.9-SERIES) nor will it change any of its classes to use them. That doesn't mean you can't use them, though Here's a quick-start guide:
As an example, if we have the following in de/thekid/tools/SQL.class.php: namespace de\thekid\tools;To run this class, use xp de.thekid.tools.SQL ... as you would with a non-namespaced class. |
|