PÃ¡draic Brady's Blog:Doing that thing called PEAR - Packaging Source Code for PEAR Distribution
524454
PÃ¡draic Brady has followed up his last post on PEAR. This time he's covered the method to package and distribute source code using the PEAR installer.  All right then! You read the last blog entry advocating PEAR (or found it during the week ;-)) and you want to know all about packaging code so your users can install your library or application using the PEAR installer. A few things first:  1. You don't need to propose a package to PEAR to do this. 2. You don't need to create a PEAR "channel" although it's very much recommended (another future blog post no doubt). 3. You don't need a whole lot of effort.  Taking your source code, and generating a PEAR package is a relatively simple task.  He covers the process at lengths with easy to follow steps.
466365
Cameron Olthuis wants to share the tools that he finds th emost useful with the entire web, so he's posted them here on his blog.   His list includes libraries from all different technologies, not just PHP. Several are Javascript-related, but it's always good to have a complete toolkit on hand when trying to tackle some of the more difficult things.   Included in his list are things like:  Moo.fx - a Javascript effects library Swat - an open source web application toolkit PEAR - the PHP package repository Mochikit - lightweight Javascript library    Be sure to check out the post and its comments for more great resources!
357182
In a new post to his blog, Chris Hartjes, spurred on by an article in the latest edition of php|architect magazine (covering protecting your code), has shared a few opinions starting with a certain paragraph near the end.   To start, I will focus on the paragraph above. What I get out of that is that if only your source was closed and hidden from prying eyes, it would not have bugs in it. Which is, of course, total nonsense. Code has bugs because it's open and they feel safer? There are two kinds of bugs: application bugs (which is the code I would write) and system bugs (in this case, bugs that that appear from PHP itself). I'm sorry, but there is nothing I can do if there is a bug in PHP that causes my application to crash except to point this bug out to the people who have the ability to fix it.   He goes on to talk more about how protection like this (the article talks about using the IonCube Encoder) will not stop someone if they're really determine to get at the code underneath the encryption. His only suggestion is to make an application good enough that people wouldn't want to try to steal it as much and would rather pay for their version.   Encode your stuff if you want, but be aware that the minute you choose to do that you are telling your customers "I don't trust you" and I have a hard time understanding a business model that assumes people are going to want to steal the stuff you sell.
144022
A few more of the International PHP Conference slides have surfaced for your enjoyment:  Sandro Zic - A comparison of PEAR Installer, Phing, and ZZ/OSS Installer alan@akbkhome.com - PEAR and PHP 5 (blog entry)
705698
Over on Codewalkers.com today, there's a new software review posted concerning the PHPAudit Distribution Management package.
654370
Pierre-Alain Joye has a little reminder posted to his blog today about two posts from planet-debian and Apache that refer to clones/references in PHP4 and PHP5 and some of the misconceptions presented there.   Reading planet-debian and Apache (from Sven and David), I catched two posts about clones and references in php4 and php5. I do not think it is worth to explain again everything here as Sara wrote a very good post already, check it out here.   He mentions his annoyance with articles/posts like these and the impact that it has on PHP as well as the person posting.   I wonder when the OS community in general will be mature enough to stop bitching at each other. And that's valid for PHP developers, gnome-kde and other well established wars.
685152
Joshua Eichorn has posted some slides that he presented at a local PHP User Group meeting just passed that serve as an introduction to PEAR.   I'm hoping to improve the slides a bit and give this presentation at lots of other places. If any PHP User groups on the west coast would like me to do a presentation about PEAR drop my a line.   To help further the cause of PEAR, he's also offering the slides in an archived file for presentation anywhere.
248750
This is a followup on Marco Tablini's discussion of the PHP programmer availablity and my earlier attempt at defining enterprise PHP.
43294
On the PEAR blog today, they're asking for thoughts on some of the standards for the coming PEAR2 development environment:   Please read the following document and post your comments on the wiki using the discussion page. Comments are opened for a period of two weeks. It is very important that you comment as these standards will define PEAR2.   The standards can be found here and include everything from the base requirements and package approach down to specific package-related rules (for things like directory structure, class-to-file conventions and handling dependencies).
489348
To prepare the way for the upcoming PEAR book from Packt Publishing correctly, Stoyan Stefanov has posted this info about the book and where to find the latest details on it.    Here's the link to publisher's page dedicated to the PHP Programming with PEAR. Guess who wrote the chapter for MDB2? ;)   It's an honour to me to be in the company of the other authors, people who have done a lot for the PEAR community    He also mentions some of the topics that the book will contain, including accessing databases with MDB2, creating and parsing XML documents, and accessing web APIs. The book is coming out in September, so keep on the lookout for it at your local bookseller soon.
632891
Popular posts from PHPDeveloper.org for the past week:Job Posting: WorldNetJobs.com Seeks Expert PHP Developer (Multiple Locations - FL/MD/NY)Stefan Reuter's Blog: Profiling PHP ApplicationsRich Zygler's Blog: People work with WS-* web services in PHP? Why?PHPBuilder.com: Securing Data Sent Via GET RequestsKore Nordmann's Blog: Comparision of PHP image librariesJim Wynia's Blog:  WebDAV, PHP and YouPadraic Brady's Blog: Namespaces (or Yet Another Pointless Opinion Piece)Christopher Jones' Blog: PHP 5.2.5 RPMs with OCI8 and PDO_OCI are availableZend Developer Zone: PHP Abstract Podcast Episode 29: PHP Women Podcast (Recorded Live)Evert Pot's Blog: PHP WebDAV Integration Library
641738
In a new post to his blog, Robert Swarthout about a PHP frontend he's been developing for working with Subversion repositories:   The frontend needed to be designed in such a way that each developer could access their working copies and make the full range of actions against them. I decided to also use an AJAX setup so that pages would be quickly loaded and updated by a single toggle of a folder.   A few issues popped up, including tracking edits correctly through the interface. His solution revolved around an Apache MPM that could serve different pages to different users and groups. With this solution in place, the functionality could be built up, a list of which he provides including:  create working copy from repository (svn checkout) svn blame svn delete search files (via a grep/find combination, omitting .svn folders) svn rename
402184
Continuing on with his look at his OpenID library and its implementation, Padraic Brady has two new posts with more of the story.   From the first post:   As a follow on from my previous entry about OpenID in the Zend Framework, I've been in brief contact with Dmitry Stogov across a scattering of emails. Dmitry posted his OpenID proposal for the framework over at the Proposals Wiki earlier in the week. [...] It's actually very hard to comment constructively rather than simply handing over my code which probably says a lot more all by itself. [...] Anyway, I've agreed to port my OpenID library to PEAR as a PHP5 package. I checked with the mailing list, and the approach I've taken in splitting the library across a number of freestanding components hasn't seen any objections. On the flipside, it does help by providing upgrades to existing PEAR Encryption packages which are not yet migrated to PHP5 versions.   And from post number two:   Over the weekend, I managed to grab a few hours to dig around my OpenID library with the ultimate development tools: patience and experimentation. [...] What I've refactored towards is a splitting of the OpenID process based on three categories: Request, Redirect, Response.
449834
Sebastian Bergmann has posted the results of some benchmarking on the compilation he's done on the branches of PHP from version 3.0 all the way up to 5.3-CVS.   As people keep asking me for an update to my previous benchmarks (PHP / GCC / ICC Benchmark, PHP 5.1 / GCC Benchmark (Update), and PHP 5.1 Performance, I quickly ran a new benchmark today.   He rendered the results out into a series of charts defining the number of total seconds taken for the compile and how long each of the components took. It's impressive to see how much of a jump there was between the 3.0 series and 4.3.   He also includes his compile settings (and machine information) as well as the numbers for the results if you'd like to graph them out yourself.
404297
Latest PEAR Releases:PHP_CodeSniffer 0.1.1Net_UserAgent_Mobile 0.28.0Structures_DataGrid_Renderer_HTMLTable 0.1.1Structures_DataGrid_DataSource_XML 0.1.1Structures_DataGrid_Renderer_XML 0.1.1HTML_Table 1.7.3Spreadsheet_Excel_Writer 0.9.1PHP_CompatInfo 1.4.0XML_Query2XML 0.6.1Console_Color 0.0.4PEAR 1.5.0a1Crypt_XXTEA 0.8.0
495913
From the PEAR blog today comes a new post talking about the introduction of a much requested option when accessing the PEAR source code - SVN over CVS.   As part of the PEAR2 project we are making that happen. I'm happy to announce that we now have an SVN repo ready for testing. Web access at http://svn.pear.php.net with the SVN url being http://svn.pear.php.net/repo.   The access isn't quite available yet, but it will be as soon as they figure out how they want people to be able to access the parts of the PEAR2 source code. Keep an eye on the PEAR Blog for the latest.
767738
Greg Beaver points out the numerous releases that were made in the PEAR community today - including an update to the PEAR website itself.   OK, today's release party wins.  I've just uploaded the 8th package for release, and it's a very significant day of releases.   The three updates made today are:  An update to the PEAR website that allows for patch tracking in the bug tracker The latest version of PHP_ParserGenerator - version 0.1.5 and the release of the first, full-featured parser for PHP - PHP_Parser along with a "companion", PHP_Parser_DocblockParser