After reading the reference guide on Zend_Translate I decided that we were going to use “gettext” as our translation adapter. PHP has support for gettext right our of the box, and with the Zend_Translate it’s easy to change adapters, if you decide that you want to use a different adapter.

Assuming that you already have the latest version of Zend Framework (1.10.*) installed in your server, I’m going to explain and guide you guys on how I got it all working.

First you need to get a tool that we will use to parse your project files to create the translation dictionaries. I’m using PoEdit which is free and supports multiple platforms.

Now let’s put some code down in your index.phtml file of you application. This one should be located in /yourapp/application/views/scripts/index/
If it’s not there, then just create one, but make sure you have to corresponding controller and action.
Inside of this file we are going to put the following:

<?php
$t = new Zend_Translate(
	'gettext',  //the adapter
	APPLICATION_PATH.'/translation', //where the lang files will be stored
	'auto',  //set to auto include .mo files
	array('scan' => Zend_Translate::LOCALE_FILENAME) //set to scan lang files
);

echo $t->_("This is my first translation")."<br/>";
?>

Before this piece of code works, we need to generate our translation files, else it will throw an error stating that the application can’t find the corresponding language files.

We need to create a new folder in your application folder. I’m calling it lang, but you can call it anything you want. This folder will be used to store your language files. So you should have something like “/yourapp/application/lang”.

After this, you need to open up PoEdit:

1. Go to File->Catalog Manager

2. Click on the “Create new translations project” icon

3. Give your project a name

4. Select the directory to store your translation files (“/yourapp/application/lang”) and hit OK

With a newly crated project, we can now generate our language file.
To do this,  close the Catalog Manager window

1. Go to File->New Catalog

2. Give it a project Name and/or version and be sure to feel in the appropriate information. Be sure to select Charset  ”utf-8″

3. Now, click on the paths tab. Here you will have to add all the dir paths that point to the files that you want to parse for translation. (/yourapp/application/views/scripts/index/index.phtml)

4. Finally, click on the Keywords tab, and make sure you include the keyword the parser will use to identify the text that needs translation. In our example we will put an underscore “_”  since in our code we have echo $t->_(“This is my first translation”);

5. Hit OK and make sure that you save the file with a name such as mylang_en.po. The _en is crucial, since Zend_Translate will scan the appropriate language file and use this naming convention to load the appropriate file

Since by default the PoEdit PHP parser handles files with .php extension. We need to modify the preferences so that it allows other types, such as .phtml files.
To do this, go to Edit->Preferences->Parsers  When you get to parsers select PHP and then click on the EDIT button. In the parser setup window we need to add *.phtml extension to the “List of extensions” field in the Language section, separated by semicolons. The field should be something like this: *.php;*.phtml
Then, in the Invocation section, you need to add  -L php to the parser command. This should look like this  xgettext --force-po -o %o %C %K %F -L php

Once you have completed this, a pop up screen will show the progress of the catalog update and then list you all the parsed strings. Hit OK and then you will be in the translation view. Just select the string you would like to translate save and you are good to go.

Once you’ve completed the following steps just copy the .po file and create additional one’s for the languages you want to do translation. Remember the naming convention discussed on the steps above.

In your code to switch languages, you need to put the following line $t->setLocale('es'); This for example will switch the locale to Spanish and will try to load a file with “_es”

<?php
$t = new Zend_Translate('gettext', APPLICATION_PATH.'/translation', 'auto', array('scan' => Zend_Translate::LOCALE_FILENAME));

echo $t->_("This is my first translation")."<br/>";

//change locale to spanish
$t->setLocale('es');

echo $t->_("This is my Second translation")."<br/>";
?>

New Major Features:

• Create multiple galleries
• Ability to put a caption to each image
• Added Multi-Language support

Also you will find this version to be better integrated into GetSimple, by using another plugin I created called “Admin Tab Loader” that is really more intended for GetSimple Plugin developers.

If you want to see what a image gallery created with the plugin click to view the demo.

CSS border radius generator for lazy people

This simple site gives you a quick an easy way to generate the CSS code for the awesome border-radius property.

CSS3 Sandbox

Here you would find a bunch of cool tools to try out. They have XRAY and MRI that are aimed more to the developer that wants to debug and  get quick information related to the page elements. But, If what you are looking is for CSS3 code generators, then explore the CSS3 Sandbox. It features code generators for Gradients, Shadows, CSS transform, CSS text stroke.

Last but not least, you should check out CSS3.Info. They have a lot of good resources and information on everything related to CSS3.

Enough rambling!

Simple Image Gallery, is a new plug-in created to include a much needed functionality to Get Simple CMS. It uses the build in file manager to manipulate and upload new images to the server, then, just go to the plugins tab and click on the Simple Image Gallery link. The only thing you need to do here, is select the images you want to display in your image gallery. Once you have selected all the images you want to display in your page. Go to the pages manager and select the page you want to include the gallery. Once in the page editor, open the page options and select “Enable Image Gallery” and save the page and you are done!

Installation is pretty simple. Just download the plugin, unzip it, upload the unzipped content to the plugins directory.

Download: Simple Image Gallery Plugin - v1.1.0

As always, if you have suggestions, concerns, you find bugs or just want to comment on how great the plugin is. Feel free to do so.

This is my first attempt at creating plugins for Get Simple CMS, an awesome CMS system I’ve been playing around lately. So, I recommend you guys check it out, if you are looking for a “Simple” content management system for your next project.

This plugin allows you to easily add TweetMeme’s reTweet Button to the content pages in GetSimple. It also includes a settings panel in the settings section of the administration area when you can customize the plugin.

Some of the available settings are:

• Change the URL shortener
• Change the size of the button (compact/expanded)
• Change the @username who will be reTweeting the post
• Disable the button for specific pages

Download: TweetMeme reTweet GetSimple Plugin - v1.0

Feel free to give feedback and let me know if you encounter any problems.

This week I had the chance to play around with Google’s charts API, and let me tell you that I’m loving it. In the past couple of years I’ve had to integrate charts into the different projects. I have used everything from Fusion Charts, to PHP/SWF Charts, and DOJO’s charting engine. But, since I learned that Google provided developers with an API to create charts on the fly, I wanted to give it a try.

To create static bart chart is as simple as:

<img src="http://chart.apis.google.com/chart?
cht=bvs
&chs=200x125
&chd=t:10,50,60,80,40|50,60,100,40,20
&chco=4d89f9,c6d9fd
&chbh=20&chds=0,160"/>

Let me break out the parameters for you into:
// this is the chart type
cht=bvs
//this is the bar colors
chco=4D89F9,C6D9FD
//this is the chart values
chd=t:10,50,60,80,40|50,60,100,40,20
//chart dimensions
chds=0,160

In the Google Charts API website you can find more info regarding this simple but useful chart api. But, that’s not all. They also have the Google Visualization API where they actually give you more advanced and dynamic set of visualization tools. They pretty much opened their entire library of data visualization helpers to allow developers like yourself create user interfaces that contain elements that some of your users will be used to seeing, since graphs, charts and other elements you will find in this API is already being implemented in google products.

I encourage you to check both, the more simple and straight forward Charts API, or the more advanced and dynamic Visualtization API.

Feel free to let me and the readers know on the exiting ways you are utilizing those API’s

Today I tried to install Zend Studio 7.0 on the latest 64-bit version of Ubuntu (9.10). Initially, it would just throw an error. (exec: 2481: /tmp/install.dir.2855/Linux/resource/jre/bin/java: not found). Since, the error was related to the installer not being able to find the java JRE that came bundled with the installer, I decided to install with the system’s JRE using:

./ZendStudio7_0_0.bin LAX_VM /usr/bin/java

That seemed to do the trick, but, once the installer had finished. Trying to open Zend Studio would give me an error (Failed to execute child process “/usr/local/Zend/Zend Studio-7.0.0/ZendStudio” (No such file or directory)). At this point I was about to give up, until I did a little bit of research and found that the problem was more simple that I imagined.

Just run the following command in your terminal window:

sudo aptitude install libc6-i386 ia32-libs

ia32 is a package that contains runtime libraries for the ia32/i386 architecture, configured for use on systems running a 64-bit kernel. This will allow to install and run Zend Studio, but It will enable compatibility with any other application designed for 32-bit processors.

After running the above command, and installing Zend Studio, I ran into my second problem. A bug in eclipse that would not allow me to click on next or finish in certain windows. In my case, was when I was trying to create a new remote connection. To fix this problem I had to do the following steps:

• 1). Open terminal and go to Zend Studio Directory.
• 2). Create a new file called ZendStudio.sh and open it.
  vi ZendStudio.sh
• 3). Paste the following code, save and then close it:
  #!/bin/sh
CURDIR=`dirname $0`
export GDK_NATIVE_WINDOWS=1
$CURDIR/ZendStudio
• 4). Change the permissions of the file for execution
  chmod +w ZendStudio.sh
• 5). Go to your application launcher, and right click and select properties.
  Once in the properties dialog, modify the command field.

  Change the path from:

  "/home/{USER}/Zend/ZendStudio-7.0.0/ZendStudio"

  to

  "/home/{USER}/Zend/ZendStudio-7.0.0/ZendStudio.sh"

  So basically you are adding the .sh extension.

• 6). Close the window and open Zend Studio, everything should be working fine now.

I hope this information helps you if you happen to run with the same problem I did. Let me know if you have a different solution.

On my last post I wrote on how to debug and log error messages using Zend Framework and Firebug. Today I wanted to write on how to properly display messages and alerts to users.

There are different type of messages you can display to a user in a web application. From the typical validation messages, to a dreadful fatal error in your app.  Here are some rules I tend to follow when alerting the users that they must take an action without causing confusion:

• Use the same massaging system to display all messages
• Stick to 3 different types: warning (yellow),  success (green), and error (red)
• On system error, do not display the system error to the user
• Display informative messages when interface can be confusing

Users tend to adapt to applications, but if you are not consistent with your user interface, users will have a more difficult time associating things. That’s why I suggest you stick to one messaging system (format). This will create a balance in the application and users will be less prone to confusion.

Associating color to different types of actions or messages has been used for decades and not just on the web. The clearest example is traffic lights were you see the common red, yellow and green.
So, why re-invent the wheel and introduce new types of messages with weird color associations. Stick to at least these 3 basic colors, and use them accordingly. For example, if you have a fatal error or you want the user to stop the current action use red. To warn or inform the user then use yellow, and last but not least use green for success messages.

On system error, do not display the system error to the user. This rule should be obvious, but for some reason there are still developers that like to show errors or exceptions that the application throws. Always display a user friendly message. Something along the lines of “Sorry, an unexpected error occurred. Please try again, and if the problem persists please let us know”. Remember to log the error, so you can troubleshoot the problem at a later time if necessary.

My last rule is about guiding the users on how to use your application. When I’m creating a new application, I always have some idea on how the user should use a certain feature within the app. This does not mean they will use it how you thought. So why not train them while the use the application. My suggestion is to display messages that will be helpful, especially in places were the application can be confusing, or you want them to follow some sort of path. Never assume the user will be smart enough to figure out how to use your application!

That being said, I developed jAlert, a plug-in for jQuery that will aid you in displaying messages accordingly to the rules I discussed. Feel free to to use it on any of your projects.

When developing an application there are some important factors that you have to pay close attention to avoid problems in the future. I think one of the most important is logging information on how your application is working and when it fails.

Must of us like to log only big exceptions and fatal errors, but the truth is, that when you are in the development process it’s very important to keep track of not just errors, but important information of when something gets executed. As a web developer one of the most important tools to have is FireBug. If you didn’t know, FireBug has an API that you can use to send console messages for logging purposes, when debugging JavaScript. But, did you know you can use FireBug to debug your php applications?

Through Wildfire, a project that was created to help developers have a standard way for sending messages between different programming languages and scripts. The Zend Framework is now able to communicate to the Firebug console in order to display logging messages injected by PHP.

Using this component is pretty straight forward if you are using Zend_Controller_Front (MVC) with zend Framework.

Place this in your bootstrap file before dispatching your front controller

$writer = new Zend_Log_Writer_Firebug();
$logger = new Zend_Log($writer);

Then whenever you want to log something to Firebug just use it in your model, view, or controller like this.

$logger->log('This is an INFORMATIONAL log message!', Zend_Log::INFO);
$logger->log('This is a WARNING log message!', Zend_Log::WARN);
$logger->log('This is an ERROR log message!', Zend_Log::ERROR);

If you notice in the example above, you can specify the type of message you want to log (INFO, WARN, etc..). This is helpful when you want to clearly identify what type of message you are viewing since it will apply a special formatting and in some instances provide more information.

If you want to use the Zend_Log_Writer_Firebug as a stand alone here is the sample code you can use:

//Instantiate the Firebug Writer
$writer = new Zend_Log_Writer_Firebug();
$logger = new Zend_Log($writer);

//start the wildfire component
$request = new Zend_Controller_Request_Http();
$response = new Zend_Controller_Response_Http();
$channel = Zend_Wildfire_Channel_HttpHeaders::getInstance();
$channel->setRequest($request);
$channel->setResponse($response);

// Start output buffering
ob_start();

// Now you can make calls to the logger

$logger->log('This is a log message!', Zend_Log::INFO);

// Flush log data to browser
$channel->flush();
$response->sendHeaders();

If you don’t use ZendFramework there is another alternative to php developers. FirePhp, will also enable you to send log messages to Firebug by using php method calls. Be sure to check FirePhp website to get more information.

So remember that this is just one easy and great way to debug your projects, there are many other tools and methods you can incorporate into your projects. If you want to share other ways or simply just want to ask a question regarding this post, feel free to leave a comment.

According to Joe Hewitt, developer of the facebook app. Version 3.0 of the facebook application has already been submitted to apple, and it’s waiting for approval.

Here is what’s new on the version of the app will contain:

• New and improved Home screen that allows you to create shortcuts to your favorite friends and Pages
• Events: the new events screen will allow you to see your upcoming Events and RSVP
• Pages: support for pages was added so you can easily see and become fan of Pages and if you are a Page admin you can now post updates and photos to your pages.
• Birthdays: see your friends’ b-days.
• Notes: now you can write Notes and read your friends’ Notes
• Complete photo management (create albums, delete albums, delete photos, delete photo tags, Upload photos to any album)
• Upload videos from an iPhone 3GS
• Change your Profile Picture
• Zoom into photos
• Like functionality was added so you can like posts and photos
• See the same News Feed as the Facebook website
• Visit links in a built-in web browser
• See all of your friends’ friends and Pages
• See mutual friends
• Easily search for people and Pages
• Make friend requests
• Quickly call or text your friends
• Friends sorted by first or last name according to your settings
• Chat friends sorted alphabeticaly

There are a few missing functionality that we have been waiting for. But Joe Hewitt already mentioned in his twitter account that he already started development of version 3.1 of the facebook app and it will include “Push Notifications” and “Landscape Mode” and I guess he will throw in a few more small features.

Now with version 3.0 of the facebook application Will we ever need to go into the full facebook.com website? I guess that depends on how you use facebook, but, in my opinion I will be visiting the site less.

Update: According to the developer of the application the update it’s live on the iPhone App Store. So go grab it and let us know what you think.