 | News Feed |
 | Jobs Feed |
Sections
|
| feed this: |  |
PHPImpact Blog: Propel 1.3 uses PDO instead of Creole
by Chris Cornutt August 25, 2008 @ 10:22:23
On the PHP::Impact blog Federico points out a new feature/update that the Propel team has made to help with performance - a change from Creole to the based PDO layer that PHP includes.
This change has a number of implications, particularly for those who are executing SQL directly. PDO's API is loosely similar to Creole's, so this change shouldn't require any major re-architecture.
New features that come along with this move you might have to upgrade for include the newer DSN format for build/runtime properties, the removal of the mysqli adapter, SPL autoload integration and a few API changes you'll have to look out for. You can find out more information on the Symfony framework's support for these changes on the sfPropelPlugin and DbFinderPlugin pages.
voice your opinion now!
pdo creole proel change symfony sfpropelplugin dbfinderplugin
Matthew Turland's Blog: Goodbye WordPress, Hello Habari
by Chris Cornutt June 23, 2008 @ 09:36:17
Matthew Turland has said goodbye to Wordpress and hello to Habari - a "next-generation free software blogging platform". He also includes one of the more helpful tips for those thinking on doing the same:
So after eventually getting fed up with WordPress, especially after the WYSIWYG editor disappeared in the 2.3.3 update, I finally decided to bite the bullet and migrate my blog over to Habari. Once I'd been through the process, I thought I'd write a short blog entry about the experience.
The two tips he mentions are about exporting the old content (made simple from the WordPress admin interface) and making Habari support his WordPress URL scheme (so as not to loose links to any content out there). He found this to help on that front.
voice your opinion now!
habari wordpress change wysiwyg migrate blog software
PHPImpact Blog: Open-source PHP applications that changed the world
by Chris Cornutt May 23, 2008 @ 08:47:44
On the PHP::Impact blog, Federico has written up a bit of a "history of PHP applications" since 1998 that have changed the community (and the online world) by being released.
From managing databases to shopping, writing blogs to sending emails. Ten years of passion, great software architectures, team work and revolutionary ideas. Here are the most influential open-source PHP applications to date.
Among those on the list are things like SquirrelMail (1999), phpBB (2000), Drupal (2001) and WordPress (2003). More lately things like frameworks and content management systems have been popular and are being developed with more structure and better standards than some of their predecessors.
voice your opinion now!
opensource application change community blog cms ecommerce
Helgi's Blog: New features and changes in pear.php.net
by Chris Cornutt January 08, 2008 @ 12:50:00
Helgi has posted about the updates that have recently been made to the PEAR website (pear.php.net) to help correct some issues and bring in some new features.
I just did a new release of pear.php.net which has a bunch of new features and bug fixes, most of which you can see here.
Some of the updates include:
- One column design instead of the 2 column design
- Usage of the YUI CSS reset + fonts
- The package list on http://pear.php.net/packages.php doesn't highlight deprecated packages anymore
- Now developers can see bug reports by unconfirmed accounts
- The RSS feeds now contain new line breaks!
- Patch uploading during ticket creation now works
He also specifically mentions some of the feedback he's gotten on certain things (like the new layout, the CSS of the site and the DES passwords) and explains some of the rationale behind their update/use.
voice your opinion now!
pear website update feature change layout password css pear website update feature change layout password css
Michael Kimsal's Blog: Continued sad state of PHP development
by Chris Cornutt December 27, 2007 @ 10:25:00
Michael Kimsal has posted some more thoughts on what he calls the "sad state of PHP development" pointing out some of the practices of the PHP group surrounding the development of the language.
Every few months there's a release, whether large or small, which introduces new features and bug fixes. However, with every release also comes fears of tiny, sometimes undocumented, changes that break existing code, and often for no solid reason other than someone with commit access decided they liked the 'new' way better than the old way.
He points out a specific example, get_object_vars and how its return values were changed in an earlier release as well as the update to glob made recently to change its return types.
In his opinion:
No changes should be made to the PHP core without an issue being opened, either in the 'bug' tracker or some other issues tracker.
Be sure to check out the comments for other great opinions on the topic.
voice your opinion now!
development language state sad change commit development language state sad change commit
|
Community Events
Don't see your event here? Let us know!
|