jmHeadJsPlugin Release

After blogging about my Symfony2 bundle release I had to also blog about my new Symfony 1.3/1.4 plugin jmHeadJsPlugin.

This plugin uses HeadJS to load javascripts into your page and adds a whole load of other functionality to your application. Check out my plugin and HeadJS for more information.

Flex 3.0 meets Symfony meets PureMVC: sfFlexymfonyPlugin

I have just released the new sfFlexymfonyPlugin for Symfony.

The sfFlexymfonyPlugin provides means for a developer to easily integrate flex applications into Symfony. The undelying Felx application uses a specific framework aimed to give developers a Symfony-like feel.
Detailed documentation still to follow. Please for now try to have a look at the DefaultModule example in your application. The underlying architecture is based on PureMVC so please also have a look at their documentations. Soon I will update the documentation and provide a full tutorial on how to use the framework. Also browse through the whole source code (there is not much in there so you will have a nice overview of what’s going on).

Check it out here

http://www.symfony-project.org/plugins/sfFlexymfonyPlu

Symfony Plugin Install Script

This is a very short post.

Currently I am using Symfony 1.4.1 for my development but I have noticed that I could not install most if not all plug-ins through the PEAR packaging system. Since I am using Ubuntu I quickly wrote myself a short script to handle the download and unpacking of plug-ins that I want to install. When calling the script you just give it the URL to the .tgz package of the plug-in. Enjoy

#!/bin/sh
url=$1
#extract the package filename from the URL
package_name=$(echo $1 | sed 's/.*\///')
#extract the raw plug-in name (with version number)
plugin_raw=$(echo $package_name | sed 's/\(.*\?\)\.tgz/\1/')
#extract the actual name of the plug-in (without the version number)
plugin_name=$(echo $package_name | sed 's/\([^-]*\).*/\1/')

#go to the plug-in directory
cd plugins

#check if we already have downloaded the package. You may change the destination to anything you like.
#I store the packages in /usr/share
if [ -f /usr/share/$package_name ]
then
 sudo cp /usr/share/$package_name ./$package_name
else
 wget $1
 sudo cp ./$package_name /usr/share/$package_name
fi

# untar
tar zxpf ./$package_name
mv ./$plugin_raw ./$plugin_name
sudo rm ./$package_name

# remove package.xml file
if [ -f ./package.xml ]
then
 rm package.xml
fi

exit 0

Process Monitor

Just a quick dump of a recommendation I got earlier.

Process Monitor is a very useful tool if you need to see what processes are using which resources on your machine. Here’s a short overview from the website

Overview of Process Monitor Capabilities

Process Monitor includes powerful monitoring and filtering capabilities, including:

• More data captured for operation input and output parameters
• Non-destructive filters allow you to set filters without losing data
• Capture of thread stacks for each operation make it possible in many cases to identify the root cause of an operation
• Reliable capture of process details, including image path, command line, user and session ID
• Configurable and moveable columns for any event property
• Filters can be set for any data field, including fields not configured as columns
• Advanced logging architecture scales to tens of millions of captured events and gigabytes of log data
• Process tree tool shows relationship of all processes referenced in a trace
• Native log format preserves all data for loading in a different Process Monitor instance
• Process tooltip for easy viewing of process image information
• Detail tooltip allows convenient access to formatted data that doesn’t fit in the column
• Cancellable search
• Boot time logging of all operations

You can find the tool here