Elke die-hard developer weet dat de wereld beter zou worden van “goeie code”. Applicaties (in mijn geval web applicaties) zouden niet alleen doen wat ze horen te doen, ze zouden ook nog eens sneller zijn ! Het project process zou vlotter verlopen, en het eindresultaat zou voldoen aan alle eisen vooropgesteld in de analyse, right ? Spijtig genoeg is de realiteit anders.

Het eindresultaat is niet altijd afhankelijk van tijd/resources, er zijn ook andere factoren.

Ik heb in het verleden al aan tal van internet applicaties gewerkt, en altijd had ik de beste intenties voor de realisatie van het project. Altijd ! Beginnend met de analyse, alle actoren en processen zo goed mogelijk in kaart brengen en begrijpen hoe al die zaken uiteindelijk moeten samenwerken. Het resultaat was (meestal) duidelijke en gedocumenteerde code die gestructureerd, onderhoudbaar, leesbaar en uitbereidbaar was…tenminste toch tot de klant zich besloot te “moeien”

Indien je al aan grotere projecten gewerkt hebt ken je zeker deze regel : “klanten weten nooit wat ze willen”. Zelfs als ze beweren van wel. Na het tonen van de eerste demo zijn ze verbaast en enthousiast zodat ze onmiddelijk idee’en beginnen te opperen om de applicatie “nog beter” en “nog cooler” te maken. Nu dit is niet echt een probleem zolang je de klant onder controle hebt (analyse document, project specificaties), maar dit niet het geval is : “let the bad code in” !

Op 90% van de reeds gerealiseerde projecten kwam er een moment waarop we keuzes moesten maken. Mogelijk kan er uit de eerste demo maar één voorstel van functionaliteit komen wat de klant geintegreerd wil zien. De kans is groot dat net deze functionaliteit zal botsen met alles wat je daarvoor al hebt geschreven. Daarom is het extreem moeilijk om “goeie code” te behouden. Het vereist oefening, ervaring en skill om dingen te schrijven die flexibel genoeg zijn om te voorzien aan de toenemende eisen van de klant.

Imagine you have found the exact page / function / action where it’s going wrong, and you are trying to debug it. Commercial companies offer solutions like Zend Platform / Zend Studio to debug, view stacktraces, variable watches & alot more…and i am mostly using Zend Studio for that too, but at this moment in time, Zend does not offer a windows library for Zend Platform that supports PHP 5.2.0, neither did they release a fix for Zend Studio 5.5 to build inspectation data over a Samba share…So let’s do the same thing using XDebug, afterall the world still spins without Zend.
Make sure to get the right windows or linux module for your php version from www.xdebug.org and use the installation instructions to get it running, make sure to check phpinfo to see if the xdebug is loaded. When everything is installed, we’ll start by profiling a certain action to find out what exactly the page/action is doing. Make sure to adapt your php.ini with the following configuration :

zend_extension_ts=”c:/apache/php/ext/php_xdebug-2.0.0rc2-5.2.1.dll”

[xdebug]
xdebug.remote_autostart=1
xdebug.remote_enable=1
xdebug.remote_handler=dbgp
xdebug.remote_mode=req
xdebug.profiler_append=0
xdebug.profiler_enable=1
xdebug.profiler_enable_trigger=1
xdebug.profiler_output_dir=c:/temp/
xdebug.profiler_output_name=profile

After that restart your apache, and open the page you want to analyse. As soon as you send a request to the webserver it will create a file in the c:/temp (or whatever path you defined). For me it generated a file (c:/temp/cachegrind.out.5808). This file contains alot of information what exactly php was doing on your request. Call it a stack trace. This file is human readable but does not give an immidiate overview, that’s why i would suggest to use a program to analyse the cachegrind. To my knowledge, the best program to-do that is KCacheGrind, the downside is that is a KDE program, so if you are using windows you would need alot of hacks, just to get KCacheGrind running, thats why there is a windows port (with less features) available called WinCacheGrind. If you open WinCache use the File>Open File dialog and relocate to the cachegrind.out file (for me c:/temp/cachegrind.out.5808), depending on the size of your file, wincachegrind will start analysing and give you a visual representation of the stack trace of your action.

Note that all pages you visit from now (untill de-activating the module in php.ini) will get ‘profiled’ and generate a cachegrind file. As this is filesystem intensive, i would suggest commenting the above php.ini section as soon as you’re done and restart your webserver.

• easy configuration
• multi sortable columns (ascending & descending)
• search features
• add actions to one or multiple records (icon + action)
• sizeable columns
• go to page x
• ability to change rows per page

So since my last post, 2 weeks have passed and i am proud to say we’ve finished a large part of the code. Now we are still having problems with the javascript to allow the user to change his column width in multiple browsers, IE seems to refuse some of the javascript code. I am still looking into that.

P.S. : I have been getting several e-mails with code requests. Untill i am really done i won’t give out the code. If you think you can help me with the javascript resizing issue though, you can always drop me an e-mail.

As time moved on, this loading of the datagrid became slower and slower (due to increasing objects, about 9000 records with multiple joined tables). This was mainly because the old datagrid first loaded all objects, and then sorted the entire array by the columns as defined by the user….don’t tell me..i know ! This is a bad approach, that means all records get looped, and if you are using propel that would mean for each of those 9000+ records an object is created…that’s crazy…(it has some advantages though)…

So now i finally found some time to do a total rewrite of this datagrid, combined with the power of the propel pager, propel criteria & the php/ajax framework xajax, i came up, faster then expected, with a powerfull scalable datagrid that only loads the visible records. All switchpages, sorting & filters call a corresponding ajax function. These functions change the criteria in the object and reload the datagrid. I’ll elaborate on this later, by showing you some code and perhaps an online example.

• make sure the power settings do not use the option to enable cpu throttling (this seems to be a java issue)
• try replacing zends jre by JRE 6 (http://java.sun.com/javase/6/download.jsp)
• disable the OS look&feel in your zend application
• disable all power management for your video card
• if you are using a dual monitor setup, make sure the editor & palettes are on the same monitor/display
• remove the Zend Project cache file : /Documents and Settings/{Win username}/ZDE/config_5.1/caches/
• expand the heap sizes (to more then 256 MB) the JRE needs for the Studio to function [file: {studiopath}/bin/ZDE.lax]
  
• if you have a 64b machine, make sure you have the 64bit java lib
• try disabling your antivirus for a second and check if performance goes up
  
• if you are using an external subversion client (not ZDE’s), make sure your options in ZDE are on CVS. (options > source control). Performance gets a huge boost (integrated svn is causing a problem when using 3th party tools)
  
• submit a support ticket (http://www.zend.com/support) (make sure to mention you tried all t he above steps, and provide as much detail as possible, because they won’t fix your problem untill they have everything they are looking for : hardware, software, ZDE.log, description of the project)
  

Here’s the info I found posted over at the PhpBuilder.com Zend Studio Forum by MStaniszczak (post is no longer there). This item addresses the speed of the java virtual machine, and for those of us running Intel processors, this tends to be faster than the Sun JRE. If you’ve got an AMD processor, this may or may not yield any performance.

Head on over to BEA Systems and get the JRockit 5.0 JRE. Don’t worry about the SDK, unless you’re a Java programmer. It’s about 30 megs, so dial-up beware. After downloading it, extract the exe (right click, extract archive).

After you’ve done that, you should see some files, as well as another archive or zip file named something like win_ia32_jrockit150_04_jre.zip. You’ll want to extract that as well, to it’s own directory or folder (name it jre) , and that’s going to be what we need.

First, make sure the ZDE is not currently running. If it is, exit it. Now, find your installation of the Zend Studio client. It should be something like C:/Program Files/Zend/ZendStudioClient-5.0.0/. You’ll see a directory already named jre. Rename it to jre_old. Copy the directory we created from the archive into the ZendStudioClient-5.0.0/ directory.

For me the HEAP size, in combination with the source control tab (to cvs) did it, as i am using tortoisesvn for version management.

The most important in my daily development is my IDE, for the last three years i have been using Zend Studio Professional, at this moment i think (and i’m pretty sure), it’s the best PHP IDE Around. It has debugging capabilities, code completion, svn/cvs integration (although i prefer tortoisesvn, see above), but ofcourse it can’t be perfect…(i do expect it to come close for 300$/year).
One thing i don’t like about the Zend IDE (besides the pricing), are the updates. Zend is quite slow on the updates, (they might have too much todo), but as a registered & paying customer, i think some major fixes (Javascript errors in internal browser, Linux Visual Interface, Crashes) in Zend Studio 5.2.0 have a higher priority then deciding to build a new IDE when the current one is not finished (it never is). Nevertheless, this IDE is still the best PHP Editor around, in combination with the Zend Platform (free for developer licences & combined in the Zend Pro licence) you’ve got yourself a kickass debugging system containing the most important features as breakpoints, watches, stacks and output buffering.

Because you are reading this howto, i can conclude you have a website running on a domain or atleast a subdomain. For multi-language systems i prefer using the subdomain to set the language of the user. So if you were using www.mydomain.tld/index.php?lang=en before, you will now be using en.mydomain.tld. For a website with multiple languages that would become :

• www.mydomain.tld : would point to the default language, or will relocate the user based on browser/os/nslookup (whatever you prefer)
• en.mydomain.tld : would point to the website in english
• fr.mydomain.tld : would point to the website in french
• X.mydomain.tld : would point to the website in …

If you are using a subdomain this could be done with en.subdomain.mydomain.tld etc….
This way of working has some advantages :

• users will be able to bookmark directly in their language.
• Search engine optimalisation can be targetted on subdomains seperately
• crawlbots will easily know which language they are crawling (also due to tag)

Step 1 : Set up your nameserver records

Make sure the A records all point to the same adress, i prefer setting a records for all different languages as i do not want to point *.domain.tld to the website (for various reasons). As this is not a dns administration guide, try to find more information in the docs of your dns daemon, but before doing that check if undefined subdomains do not already point to the same ip as your main domain, this could be the case and then no configuration is needed…

You can check this by doing :

 ping mydomain.tld

Compare the result ip adress with a ping to a subdomain :

 ping en.mydomain.tld

If both ip match, you will most probably have the right nameserver configuration already, you can go straight to step 2.

Step 2 : Make sure the webserver catches the subdomain

As i am using apache only at this moment, i will only explain you briefly how to do this in apache, for all other webservers check the documentation. Try to look for the virtualhost directive of your domain in the webserver configuration, by default this will be in /etc/httpd/conf, searching for httpd.conf, apache.conf or apache2.conf will tell you where it’s located…If you split up your virtualhost directives in different files, you are most probably clever enough to find your virtualhost directive, if you didn’t check the bottom of your configation file, there should be something like this :

  ServerName yourdomain
  DocumentRoot "/path/to/your/webroot"
  DirectoryIndex index.php
  
   AllowOverride All
   Order allow,deny
   Allow from All
  

Add a serveralias, so apache knows to catch the subdomains, there are 2 ways of doing this, you can add a ServerAlias for all different languages, or you could add a * alias, so from now on apache will catch all unknown subdomains for this domain.

Option 1 : Catch only the subdomains i want

  ServerName yourdomain
  ServerAlias language1.yourdomain
  ServerAlias language2.yourdomain
  DocumentRoot "/path/to/your/webroot"
  DirectoryIndex index.php
  
   AllowOverride All
   Order allow,deny
   Allow from All
  

Option 2 : Catch all subdomains

  ServerName yourdomain
  ServerAlias *.yourdomain
  DocumentRoot "/path/to/your/webroot"
  DirectoryIndex index.php
  
   AllowOverride All
   Order allow,deny
   Allow from All
  

Save your virtualhost config file, or main webserver configuration file and restart your webserver

 apachectrl -k restart

More information on setting Apache virtualhosts serveralias’es.

You should now be able to see the same website you had before, using the lang.mydomain.tld subdomains, if this is not the case, check your include paths etc….I have to stop this howto for now, we will go the the coding itself in Part III

I decided to give it a go and use the framework on my latest project for EuPR (www.plasticsrecyclers.eu), as the timeframe for this project was quite limited, i needed a good framework, with plenty of documentation to solve the issues i would run into…

A snippet from the symfony about page :

Symfony is a web application framework for PHP5 projects.

It aims to speed up the creation and maintenance of web applications, and to replace the repetitive coding tasks by power, control and pleasure.

The very small number of prerequisites make symfony easy to install on any configuration; you just need Unix or Windows with a web server and PHP 5 installed. It is compatible with almost every database system. In addition, it has a very small overhead, so the benefits of the framework don’t come at the cost of an increase of hosting costs.

If you want to have a look at the results, go over to plasticsrecyclers.eu, i implented a login form, upload functionality (in different categories and a pager to browse through the various results of newsletters & documents…Keep in note that this is a “non-released” website still open for feedback & improvements….

Whatta ya think ?

• language selection was saved in session or by $_GET argument
• meta language tag was not always set
• there was no clear line how the language was selected, user couldn’t see by url which language he selected

I did a few lookups on the internet, some various SEO forums, and i’ve collected this information and, with the help of Apache mod_rewrite, turned the website into a fancy, easy-to-use, multilanguage environment, and this is how i did it. I will explain you in 3 different parts, which i will try to finish in the upcoming 3 days….

To start off i am using .xml files to hold all the different language strings, nowadays you can find some php frameworks that fully support i18n, but back in the days i was making international websites, they were not that commonly available. If you would go for a framework i would choose Mojavi, Prado or Symfony, i am not going to elaborate on that, as this post is not about frameworks, but howto put different languages on your website, and making sure google (and other search engines), crawl em like they should….

Start off by making sure you have a google sitemaps account and have a way to gather website statistics, very good would be a package where you can list the crawl bots seperately (i prefer awstats)

Sitemaps what/where went wrong when crawling your site. The Google Sitemaps program has two major components:

• Google Sitemaps Console: Provides statistics and error information about your site, as well as tools for managing your site.
• Google Sitemaps files: Enable you to tell us what pages are present on your site.

I’ll leave you the time to make sure you have both of the above items + it’s a really nice excuse to stop writing and do something else…Part II soon…

We are creating a system to analyse “Post Construction Waste” that is being transferred in Europe. To satisfy the need of our customer we designed a [tag]framework[/tag] that uses some of the most recent technologies including ajax, output caching, templating, xml language parsing and more…Because i prefer working with the recent available technologies, we decided to develop the project in php5, mainly because of the new/extended oop features and exception handling.

For version management we use Subversion, on my windows machine powered by TortoiseSVN with some extra scripts to commit/update/export with a simple click of the mouse (or shortcut combination). I noticed this week we crossed revision 700, we passed the cape of 500 programming hours on this project too….Time to move to the next one ?