sudo apt-get update
sudo apt-get install php5-dev apache2-dev build-essential apache2-threaded-dev php-pear
sudo pecl install apc

Then update /etc/php5/apache2/php.ini and add this line:

extension=apc.so

Have fun!

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

Wikipedia, Facebook, Friendster, Yahoo, Delicious, Youtube, Digg, WordPress, Tagged, W3Counter, MyYearBook

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

You might ask, why not just use setLabels?

Firstly, if you already set required fields to true/false in setValidators, why do you have to add the stars manually again in setLabels? It just doesn't make sense!

Secondly, using setLabels to add stars is interfering with language translation.

Thirdly, this is I believe a proper (or proper-ish?) way to do this kind of things with sfForm.

OK, let's get into it!

Below is an example on how to use it in your form class

<?php
 
class yourForm extends sfForm
{
  function configure()
  {
    $this->setWidgets(array(
      'first_name'           => new sfWidgetFormInput(array(), array('maxlength' => 50)),
      'last_name'            => new sfWidgetFormInput(array(), array('maxlength' => 50)),
      'email'                => new sfWidgetFormInput(array(), array('maxlength' => 128)),
    ));
 
    $this->setValidators(array(
      'first_name'           => new sfValidatorString(array('max_length' => 50, 'required' => true)),
      'last_name'            => new sfValidatorString(array('max_length' => 50, 'required' => false)),
      'email'                => new sfValidatorEmail(array('max_length' => 128, 'required' => true)),
    ));
 
    $decorator = new sidFormFormatter($this->widgetSchema, $this->validatorSchema);
    $this->widgetSchema->addFormFormatter('custom', $decorator);
    $this->widgetSchema->setFormFormatterName('custom');    
  }
}

This is optional but you might want to add the following into your css (e.g.: main.css)

em.required {font-size:1.2em;font-weight:bold;margin:0px;padding:0px;}
label.required {font-weight:bold;}

Last but most importantly, save this formatter class in your project lib folder as sidFormFormatter.php:

<?php
 
class sidFormFormatter extends sfWidgetFormSchemaFormatter {
 
  protected 
    $rowFormat = "\n%error%\n<div class=\"formRow\">\n<div class=\"formLabel\">%label%</div>\n<div class=\"formField\">%field%\n%help%</div></div>\n%hidden_fields%",
    $helpFormat = '<div class="fieldHelp">%help%</div>', 
    $errorRowFormat = "<div>\n%errors%<br /></div>\n", 
    $errorListFormatInARow = "<ul>%errors%</ul>\n", 
    $errorRowFormatInARow =  "<li class=\"error\">&darr; %error% &darr;</li>\n", 
    $namedErrorRowFormatInARow = "<li class=\"error\">&darr; %error% &darr;</li>\n", 
    $decoratorFormat = "%content%";
 
  /**
   * @var sfValidatorSchema
   */
  protected $validatorSchema = null;
 
  /**
   * @var array
   */
  protected $params = array();
 
  /**
   * Constructor
   *
   * Params:
   *  - "required_label_class_name" css class name for label tag when the field is required field, the default is 'required'.
   *  - "required_label_format" default is '%label% <em class="required">*</em>'.
   *
   * @param sfWidgetFormSchema $widgetSchema
   * @param sfValidatorSchema $validatorSchema
   * @param array $params
   */
  public function __construct(sfWidgetFormSchema $widgetSchema, sfValidatorSchema $validatorSchema, $params = array())
  {
    $this->validatorSchema = $validatorSchema;
    $this->params = $params;
    parent::__construct($widgetSchema);
  }
 
  /**
   * Returns parameter identified with $name or if does not exist, returns $default.
   *
   * @param string $name
   * @param mixed $default
   * @return mixed
   */
  public function getParameter($name, $default=null)
  {
    if (!isset($this->params[$name]))
    {
      return $default;
    }
 
    return $this->params[$name];
  }
 
  /**
   * Generates a label for the given field name.
   *
   * @param  string $name        The field name
   * @param  array  $attributes  Optional html attributes for the label tag
   *
   * @return string The label tag
   */
  public function generateLabel($name, $attributes = array())
  {
    $is_required = false;
    if ( $this->validatorSchema and isset($this->validatorSchema[$name]) )
    {
      $validator = $this->validatorSchema[$name];
      /* @var $validator sfValidatorBase */
 
      if ( $validator->getOption('required') )
      {
        $class_name = $this->getParameter('required_label_class_name', 'required');
        if (isset($attributes['class'])) $attributes['class'] .= ' '.$class_name; else $attributes['class'] = $class_name;
        $is_required = true;
      }
    }
 
    $s = parent::generateLabel($name, $attributes);
 
    if ($is_required)
    {
      $format = $this->getParameter('required_label_format', '%label% <em class="required">*</em>');
      $s = str_replace('%label%', $s, $format);
    }
 
    return $s;
  }
}

That's it! Don't forget to "symfony cc" (clear cache).

Happy coding!

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

Click for larger image

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

Click for larger image

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

So now, when I want to create a Symfony 1.0 project, I would just execute "$ symfony10 init-project myproject". And then in the project I would use "$ ./symfony cc" instead of "$ symfony cc".

It worths mentioning that I think this trick is good for development environment but "svn:externals" trick or Symfony freeze are better for production/deployment as each project will have their own copy of Symfony Framework.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

I became known as Java man, because 1) I was born in Java island, 2) I program Java, 3) I can speak Javanese, and 4) even though unrelated, I also do Javascript.

On the other hand, I have also been doing a bit of PHP4. Coming from a Java background, PHP4 Object Oriented seems backward, but I love the flexibility of PHP and how it feels right for developing websites.

So when PHP5 with java like OO features was released, I was very ecstatic (in a normal kind of way). And since then I've been looking for a PHP framework that takes full advantage of that java like OO features. I tried few frameworks before currently settled with Symfony Framework.

Symfony Framework is a full-stack (comprehensive and complete) framework written in PHP5 that take advantage of the Java like OO of PHP5.

Here's few things that I like about Symfony ...

Well known PHP libraries in one framework

Symfony Framework does not reinvent the wheel like many other frameworks, instead it integrated the best breed, well known, and matured PHP libraries like PEAR, Propel, Phing, and more. I've used PEAR in many occasions before started with Symfony. I've also used ORM (what Propel is) and have used Apache Ant (what Phing is based on). So although I still had to spend time learning Symfony, I was already familiar with its components.

Plugins

Symfony supports plugin and hence there are so many plugins available for Symfony. There are plugins for YUI, Extjs, Doctrine, Smarty, Prototype, JQuery, and more.

There are also high level plugins to add complete features to a Symfony project like:

• User management plugin
• CMS plugin
• Blog plugin
• Forum plugin
• Wiki plugin
• Media assets management plugin
• Lucene plugin
• And many many more

All of those are available to every Symfony developers list of arsenal. Plugins can be installed into Symfony project manually or via PEAR.

Scafolding

One of the best features of Symfony is its CLI commands. You can start a Symfony project in seconds. Just type a command line and all the skeleton of your project is created for you (including skeleton for your project's unit tests). No need to reinvent your own file structures, but if you're not happy with Symfony's default file structures, you can change it.

Works well with Eclipse

This one is quite a biggie to me. Eclipse is arguably the best free Java based IDE that has grown (so big) to support many (many!) programming languages including PHP. Personally, I use Eclipse PDT.

I particularly like the way Eclipse provides auto code completion for Symfony. It is able to parse the classes in your Symfony project and provides auto code completion for them. Notepad just doesn't cut it any longer since I've used Eclipse.

However, there are tricks that you need to know to get Eclipse PDT to code completion all of your Symfony classes (will write in another post).

Used by big companies

I'd still use Symfony even if there's no big companies are using it but it's good to know that big companies are starting to notice this framework.

• Yahoo is using Symfony to develop Yahoo! Bookmarks
• Delicious preview was rumored to have been built using Symfony.

Open source (MIT License)

Last but not least, Symfony is open source which mean the community (thousands of developers) is able to help to maintain it.

So there you go, few things I like about Symfony Framework

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.