When I loaded the web page, all graphs were empty/broken.  Something was wrong. PHP had GD enabled, so it was not it. I checked the php log and no errors were found, but when I looked at the error_log I saw the following:

No fonts found; this probably means that the fontconfig
library is not correctly configured. You may need to
edit the fonts.conf configuration file. More information
about fontconfig can be found in the fontconfig(3) manual
page and on http://fontconfig.org

First of all, I had missed the requirement to have fontconfig. So I went ahead and installed it. After the installation was complete, the problem was still there. I checked and /usr/share/fonts was empty, but there is another directory, /usr/share/X11/fonts which had plenty of fonts. So I renamed the original fonts directory and created a symlink to the one that has plenty of fonts.

After this, ganglia’s graphs showed up as expected.

When you need to embed a font in Adobe Flex, you do so by adding something like this in the css:

@font-face {
        font-family: Gotham;
        src: url('assets/Gotham.otf');
}
.headerText
{
	font-family: Gotham;
	font-size: 18pt;
	color:#fbaf33;
}

The original problem was that some parts of the Flex application were using the font, but specific components did not. The problem got confusing when a co-worker was able to see the correct font in all components with the same code base.

After much research and trial and error, we found that the reason he was able to see the font in all components was that he had the font installed in his computer. So apparently, Flash and the browser displayed the correct font from the system when not being able to get it from the embed font.

So, after finding out that the font had to be installed locally to be displayed all across the Flex application, and after removing the font locally, the solution came quicker:

When embedding fonts in Flex, you need to embed each font style and weight separately. And this important: You cannot specify the weight in the css style names. You just specify which font family you want to use to use a different font weight.

This is how it would be done:

@font-face {
        font-family: Gotham;
        src: url('assets/Gotham.otf');
}
@font-face {
        font-family: Gotham-Bold;
        src: url('assets/Gotham-Bold.otf');
}

.headerText
{
	font-family: Gotham;
	font-size: 18pt;
	color:#fbaf33;
}

.headerText2
{
	font-family: Gotham-Bold;
	font-size: 18pt;
	color:#fbaf33;
}

I am sure I will not make this mistake again!

All I needed to do is validate a string to verify if it follows the pattern of a hostname.

After much work and research I finally narrowed it down and here it is:

<mx:RegExpValidator id="regExpV"
source="{tbDomainName}" property="text"
flags="i" expression="^[a-zA-Z0-9\-\.]+\.[A-Za-z]\{2,6\}$"
/>

Notice the backslashes for escaping { and }  as these characters are used in Flex for data binding.

I did a quick search on Google and did not find any place on how to effectively duplicate a Propel object which in turn would duplicate the row in a table.

Basically, what I need is another record with the same values except the primary key which is an autoincremented integer.

Here is the snipped of code that I added to the Propel object.

 public function duplicate()
 {
 // duplicate object
 $ap = clone $this;

 $values = $ap->toArray( );

 $values2 = array();

 // create array of fields with null so we can force all values to be modified
 foreach( $values as $idx => $v )
 {
 $values2[ $idx ] = null;
 }

 // force all values to be changed so the doInsert inserts the values.
 $ap->fromArray( $values2 );
 $ap->fromArray( $values );

 $ap->setIsActive(false);
 $ap->setId(null);
 $ap->setNew(true);
 $ap->save();

 return $ap;
 }

Is there is another easier way, maybe provided by Propel, which I could not find, please let me know.

A weird problem occured: The input text was empty even though the property in the object has some text. I tested by removing the Binding and was able to see the text in the Input.  Weird… I’ve done this so many times before and never had a problem.

Well, it turns out that if you set the object where the Input grabs the text from before adding the component to the tree of UIComponents for some reason the Binding messes up. So the solution was adding the Panel to the parent and then setting this object where Input grabs the text from.