As the web grows, we developers have to write applications that are not location centric but rather develop applications that can be viewed by anyone around the world. Any developer that had to write such software probably has used GeoIP and has encountered issues when the time came to test their application. The only real way to test your application, without setting up servers around the world, is to assume that your code works and that the GeoIP database is working correctly.

(more…)

As some of you may know from the tweets I’ve been posting for nearly 3 weeks now, I was invited to attend the very first edition of the JumpInCamp organized by Microsoft in April 2010.

The goal of this camp was to get the European PHP community leaders together and learn about the new products and new ideas Microsoft are working on. For those of you who read about the Microsoft web developer summit that took place in Redmond in December 2009 you might think it was the same thing however you would be utterly wrong.

While the camp in Redmond was very informative and we are learnt a great deal of new features coming up with Microsoft, it was vastly different than the JumpinCamp in Zurich where the focus of the camp was to get the developers to interact with the actual Microsoft developers instead of only learning about new features. The point of the JumpinCamp was to get your hands dirty in code so we all got a few hours of lectures, then sat down and worked on either implementing those solutions into our respective Open Source projects or even discussed and raised concerns we might have regarding some of their products.

I thought it might be nice to share some of the projects I’ve started working on while I was over there and what I had interests in:
(more…)

Introduction

At echolibre we’ve been trying to organize our sales and customer relationship in a more efficient way as the company customer base is getting larger and larger. That’s natural process for any growing company. In order to help us organize how we do everything related to customers (Sales, Leads, Relationships, etc) we are giving Capsule CRM a good run.

Capsule CRM is basically a nice CRM tool that takes the boring part out of CRM’ing. Moreover (And the whole reason of this blog post), it has an API and as you all know, we LOVE APIs.

Therefore, we realized that we needed to integrate Capsule with some online services we have and so we built a PHP wrapper for their API to give developers the ability to place requests and use the web service as they wish using PHP

Services_Capsule is now being proposed to PEAR however you can already get the code from http://github.com/davidcoallier/Services_Capsule and start using it. The lack of end-user documentation may be the greatest lack in the package right now so I figured it might be good to post a few usage examples in a post.

(more…)

Last week our very own Helgi was at ZendCon in San José, California. He was there as a speaker to talk about Frontend Caching and “PEAR2 and Pyrus”

The first talk I gave was about frontend caching and how you can get the most speed out of your website by optimizing the various bits of the frontend.

Make sure to catch “The aftermath” on Helgi’s blog as you may get a better idea of what we do in conferences and what happens in general!

Introduction

A few weeks ago, Helgi and I attended PHP|Tek 2009 in Chicago, as both representatives of echolibre and The PEAR Group.

This post will briefly discuss the formation of a Recommended PHP Standards Group, as put forward by a meeting of PHP developers at the conference. As would be expected, a bit of controversy surrounds this proposal, but my hope would be that it would be accepted and grow within the global PHP community in the coming years.

As posted by Travis Swicegood, a group of community project representatives came together to discuss naming standards for PHP 5.3 and above. (I would like to take the opportunity to publicly thank the staff of the PHP|Tek conference for providing us with a large meeting room with little more than 2 hours notice).

(more…)

The other company we collaborate with on short.ie has released a private beta of a new application a short while ago. The web application is basically a business collaboration tool that allows someone to keep a consistent tracking over projects and clients, management of tasks, management of documents (online document manager) and much more.

I would seriously recommend people (managers, developers, etc) to look at it and register for the BETA version because having been granted access to test and give feedback, we, as private beta testers, found it really nice, insightful and simple to use.

This web app has a huge potential (internationally) and is developed following a solid architecture. Being strong PEAR contributors we are of course happy to take a look at what helped the footprintapp.com team achieve such a great product. So I went ahead and asked a few questions to Iarfhlaith Kelly from webstrong.

Q: How long have you been using PEAR?
A: I dabbled with a few of the PEAR packages back in college (2001-2005). Mostly I used the database abstraction packages like DB and MDB2. It was great to use on object oriented approach to interact with a database. After college though, from 2005 onwards, I ventured much deeper into the PEAR packages because as a freelance developer I was getting a lot more requests from clients.

Q: How does PEAR help you in your daily development life?
A: Using PEAR has greatly reduced the amount of code I’ve needed to write on the ‘heavy lifting’ areas of web development. This lets me focus on the flow of the system and spend more time building features that make my app unique, rather then re-inventing the wheel on some of the more common features often needed in most modern web apps.

Also, because of PEAR’s command line interface for installing and updating packages (both locally and remotely) it has made maintaining the code packages a lot easier then if I had to download and upgrade each one manually. This saves a lot of time during system upgrades.

Q: What do you use it for (packages you use)
A: Well, like I mentioned before I started off by using DB and MDB2 in college, but once I started using PEAR on client projects I quickly learned about the XML parsing libraries, HTTP requests, MS Excel generation, encryption, authentication, and email. I used a number of key PEAR libraries without which I would still be building it today. These were:

* Auth_HTTP for HTTP based authentication
* MDB2 for database abstraction

The system also communicates with a number of other web services, such as Amazon’s S3 service and authentication services via the OpenID format. To communicate with these, I use:

* XML_Parser for processing the returned information
* HTTP_Request for sending commands and data to the web services

Because of the standard approach to documentation across all PEAR for these packages allowed me to hit the ground running on new packages.

This is yet another great experience by PEAR users and we are glad to be helping and best of luck to webstrong and footprintapp for the future!