Anyway, here goes:

function lastday($month = '', $year = '',$format = 'Y-m-d') {

   if (empty($month)) {
      $month = date('m');

   }
 
   if (empty($year)) {
      $year = date('Y');

   }
 
   $result = strtotime("{$year}-{$month}-01");

   $result = strtotime('-1 second', strtotime('+1 month', $result));

 
   return date($format, $result);
}

As you can see, usage is a simple matter of calling lastday() and feeding it the year and month you want it to return the last day for, though if you leave these two parameters out, it will simply return you the last date of the current month – all in a handy ISO 8601 formatting.

Useful.

How to calculate the number of working days in a month, in other words discount Saturdays and Sundays from a month’s total number of days.

It sounds pretty simple, but because of the shifting nature of the calendar we use, one can’t just take a guess and average it you know. No, we need a function to work out this total for each month of any particular year.

Now of course I’m sure there are for more acute, beautiful or elegant solutions to this particular problem out there, but I for one quite like the idea of seeing the logic behind what is happening step by step, which is exactly why I came up with this little function to do the work for me.

So in order to calculate the number of working days in a month by removing Saturdays and Sundays from its day count, have a look at this simple PHP function:

function calculateWorkingDaysInMonth($year = '', $month = '')

{
	//in case no values are passed to the function, use the current month and year
	if ($year == '')
	{

		$year = date('Y');
	}
	if ($month == '')

	{
		$month = date('m');
	}
	//create a start and an end datetime value based on the input year 

	$startdate = strtotime($year . '-' . $month . '-01');

	$enddate = strtotime('+' . (date('t',$startdate) - 1). ' days',$startdate);

	$currentdate = $startdate;
	//get the total number of days in the month	
	$return = intval((date('t',$startdate)),10);

	//loop through the dates, from the start date to the end date
	while ($currentdate <= $enddate)
	{

		//if you encounter a Saturday or Sunday, remove from the total days count
		if ((date('D',$currentdate) == 'Sat') || (date('D',$currentdate) == 'Sun'))

		{
			$return = $return - 1;
		}

		$currentdate = strtotime('+1 day', $currentdate);
	} //end date walk loop

	//return the number of working days
	return $return;
}

As you can see, the logic of the function is pretty straightforward to follow. To use the function in your code, simply call it and pass the month and year you want it to examine, meaning that

calculateWorkingDaysInMonth(2010,04);

is going to result in 22.

I received lot of requests from my readers that asked to me how to implement Pagination with jQuery, PHP and MySQL. so I had developed a simple tutorial. It’s looks big but very simple script.

pagination

The tutorial contains three PHP files and two js files includes jQuery plugin.

-config.php (Database Configuration)
-pagination.php
-pagination_data.php
-jquery.js
-jquery_pagination.js

Database Table

jquery_pagination.js
Contains javascript this script works like a data controller.

config.php
You have to change hostname, username, password and databasename.

pagination.php
User interface page.

pagination_data.php
Simple php script display data from the messages table.

CSS Code
CSS code for page numbers.

<?php
Class RankingChecker {

	private $googleApiKey = null;

	private $googleBaseUrl = 'http://ajax.googleapis.com/ajax/services/search/web?v=1.0';

	private $checkPageCount = null;

	/**
	 * get an api key from: http://code.google.com/apis/ajaxsearch/signup.html
	 * @param string $googleApiKey
	 * @param int $checkPageCount
	 */
	public function __construct($googleApiKey, $checkPageCount = 5) {
		$this->googleApiKey = $googleApiKey;
		$this->checkPageCount = $checkPageCount;
	}

	/**
	 * get rankings
	 * @example $checker->check(array('phpasks'), array('phpasks.com'));
	 * @param array $keywords search these keywords
	 * @param array $domains domains to compare against
	 */
	public function check($keywords, $domains) {

		$rankings = array();

		if (! is_array($keywords)) { throw new Exception('Keywords array is no array'); }
		if (! is_array($domains)) { throw new Exception('Domains array is no array'); }

		foreach($keywords as $keyword) {
			$keyword = trim($keyword);
			$rows = array();

			if ($keyword) {
			    for($i=0;$i<$this->checkPageCount;$i++) {
		    		$start = $i*8;
		    		$url = sprintf('%s&hl=de&gl=AT&q=%s&rsz=8&key=%s&start=%s', $this->googleBaseUrl, urlencode($keyword), $this->googleApiKey, $start);

		    	    if ($result = file_get_contents($url)) {
		    			$result = json_decode($result);
		    			$rows = array_merge($rows, $result->responseData->results);
		    	    }
		    	}

		    	foreach($domains as $url) {
		    		$rankings[$keyword][$url] = '-';
		    		foreach($rows as $position => $row) {
		    			if (strpos($row->url, trim($url)) !== false) {
		    				$rankings[$keyword][$url] = $position+1;
		    				break;
		    			}
		    		}
		    	}
			}
		}	

		return $rankings;
	}

}
//$keywords[0] = 'adult dating';
//$website[0] = 'adultxdating.com';
?>
<html>
<head>
 <title>Google Ranking Checker Class in PHP5 by PHPASKS</title>
 <style type="text/css">
 body { font:12px arial,helvetica,sans-serif; padding:20px; }
 #info { margin-bottom:20px; }
 form { float:left; background:#f1f1f1; padding:20px; background:#f1f1f1; width:380px; }
 form textarea { width:100%; }
 table { float:left; width:380px; margin-left:10px; }
 table td { border:1px solid #eee; padding:5px; }
 .user { background:#fff; padding:5px; list-style-type:none; }
 h1 { font-size:20px; margin:0; }
 h2 { margin:0 0 10px 0; }
 button { position:absolute; right:0; bottom:0; font-size:20px; padding:5px 10px; margin:40px; }
 </style>
</head>
<body id="body" onload="init()">

 <div id="info">
 <h1>Google Ranking Checker Class <br /></h1>
 </div>
 <form action="<?=$_SERVER['PHP_SELF']?>" method="post">
 <label>Keywords <small>(max. 5)</small>:</label>
 <textarea rows="5" cols="50" name="keywords"><?=$_POST["keywords"]?></textarea>        
 <label>Domains:</label>

 <textarea rows="5" cols="50" name="website"><?=$_POST["website"]?></textarea>
 <input type="submit" name="check" value="Check now" />
 </form>
 <table>

 <?php
 if(isset($_POST["check"]))
 {
 $keywords = explode(",",$_POST["keywords"]);
 $website = explode(",",$_POST["website"]);
 $RankingChecker = new RankingChecker('ABQIAAAAT0QYHPdhh7eyjzLSB5OrohQDB0iR9tbFmh1rKcNxqCRfRwKkyBQlv_4XYljSF-KiMYSm1bu_oiXDrw', 5);
 $rankings = $RankingChecker->check($keywords,$website);
 //echo "<pre>".print_r($rankings)."</pre>";
 while(list($key,$val) = each($rankings))
 {
 echo "<tr>";
 echo "<td>".$key."</td>";
 while(list($key1,$val1) = each($val))
 {
 echo "<td>".$key1."</td>";    
 echo "<td>".$val1."</td>";
 }
 echo "</tr>";
 }
 }
 ?>
 </table>
</body>
</html>

Purpose of this script: To check a certain given backlink on hundreds of webpages provided you know the URL of every webpage.

<?php

$source = file_get_contents("source.txt");
$needle = "www.IamtryingtocheckThisPage";   //without http as I have imploded the http later in the script
$new = explode("\n",$source);

foreach ($new as $check) {
$a = file_get_contents("http://".trim($check));

if (strpos($a,$needle)) {
$found[] = $check;
	 } else {
	 $notfound[] = $check;
			}
						}

echo "Matches that were found: \n ".implode("\n",$found)."\n";
echo "Matches that were not found \n". implode("\n",$notfound);
?>

or Other way

<?php
function check_back_link($remote_url, $your_link) {
    $match_pattern = preg_quote(rtrim($your_link, "/"), "/");
    $found = false;
    if ($handle = @fopen($remote_url, "r")) {
        while (!feof($handle)) {
            $part = fread($handle, 1024);
            if (preg_match("/<a(.*)href=[\"']".$match_pattern.
"(\/?)[\"'](.*)>(.*)<\/a>/", $part)) {
                $found = true;
                break;
            }
        }
        fclose($handle);
    }
    return $found;
}
// example:
//if (check_back_link("http://www.abc.com", "http://www.xyz.com")) echo "link exists";
?>

<?php

class LoginForm extends sfForm
{
  public function configure()
  {
    $this->setWidgets(array(
      'username' => new sfWidgetFormInput(),
      'password' => new sfWidgetFormInputPassword()
    ));

    $this->widgetSchema->setNameFormat('login[%s]');

    $this->setValidators(array(
      'username' => new sfValidatorChoice(array('required' => true, 'choices' => array('admin'))),
      'password' => new sfValidatorChoice(array('required' => true, 'choices' => array('some_password')))
    ));
  }
}

The key here is using sfValidatorChoice to ensure that the input matches some predefined keys (“admin” and “some_password” in this case).

For completeness, here’s the action file:

<?php

class authActions extends sfActions
{
  public function executeLogin(sfWebRequest $request)
  {
    $this->form = new LoginForm();

    if ($request->isMethod('post'))
    {
      $this->form->bind($request->getParameter('login'));
      if ($this->form->isValid())
      {
        // authenticate user and redirect them
        $this->getUser()->setAuthenticated(true);
        $this->getUser()->addCredential('user');
        $this->redirect('home/index');
      }
    }
  }

  public function executeLogout()
  {
    $this->getUser()->clearCredentials();
    $this->getUser()->setAuthenticated(false);
    $this->redirect('@homepage');
  }
}

And the template file loginSuccess.php:

<form action="<?php echo url_for('auth/login') ?>" method="POST">
  <table>
    <?php echo $form ?>
    <tr>
      <td colspan="2">
        <input type="submit" />
      </td>
    </tr>
  </table>
</form>

And of course, you’ll want to turn on security for the application in security.yml:

default:
  is_secure: on
  credentials: user

First you create the table for store the category, let’s say the table name is tbl_category. The structure is like this.

+---------------+--------------+------+-----+---------+----------------+
| Field         | Type         | Null | Key | Default | Extra          |
+---------------+--------------+------+-----+---------+----------------+
| id            | int(11)      | NO   | PRI | NULL    | auto_increment |
| category_name | varchar(100) | YES  |     | NULL    |                |
| parent_id     | int(11)      | YES  |     | NULL    |                |
+---------------+--------------+------+-----+---------+----------------+
3 rows in set (0.00 sec)

Now we will explain the field one-by-one.

- Field id, is used to store the table primary key, it’s auto-increment value.
- Field category_name, is used to store the name of the category.
- Field parent_id, is used to store the parent id of specified category name, with this field you can store multilevel category data on single table.

Example data of tbl_category is like below.

mysql> select * from tbl_category;
+----+---------------+-----------+
| id | category_name | parent_id |
+----+---------------+-----------+
|  1 | PHP           |      NULL |
|  2 | Animal        |      NULL |
|  3 | Frameworks    |         1 |
|  4 | CakePHP       |         3 |
|  5 | CodeIgniter   |         3 |
|  6 | Horse         |         2 |
|  7 | Dog           |         2 |
|  8 | Dalmatians    |         7 |
+----+---------------+-----------+
8 rows in set (0.00 sec)

Above data represents category tree like below.

+- PHP
|-- Frameworks
|--- CakePHP
|--- CodeIgniter
+- Animal
|-- Horse
|-- Dog
|--- Dalmatians

It means category name PHP and Animal is the root category. PHP has Frameworks sub-category and Frameworks has two sub-category again, CakePHP and CodeIgniter. Animal has two sub-category, Horse and Dog. Dog has one sub-category called Dalmatians. All those data can be stored on single table structure like tbl_category above.

Now suppose you have table article called tbl_article, the structure is like below.

mysql> desc tbl_article;
+-------------+---------------+------+-----+---------+----------------+
| Field       | Type          | Null | Key | Default | Extra          |
+-------------+---------------+------+-----+---------+----------------+
| id          | int(11)       | NO   | PRI | NULL    | auto_increment |
| title       | varchar(100)  | YES  |     | NULL    |                |
| content     | varchar(1024) | YES  |     | NULL    |                |
| category_id | int(11)       | YES  |     | NULL    |                |
+-------------+---------------+------+-----+---------+----------------+
4 rows in set (0.06 sec)

You can fill category_id with id field from tbl_category. The example is like below.

mysql> select * from tbl_article\G
*************************** 1. row ***************************
         id: 1
      title: CakePHP is easy framework
    content: CakePHP is very easy framework in the world.
category_id: 4
*************************** 2. row ***************************
         id: 2
      title: Dalmatians dog killed by pedestrian
    content: A big dalmatians dog killed by pedestrian on Downing Street, London.
category_id: 8
2 rows in set (0.00 sec)

We can see that article with ID 1 has category_id 4, it means it’s category is CakePHP. Article ID 2 has category_id 8, it means it’s category is Dalmatians.

So – since we all know that the Magento documentation is pretty crappy at this time, I had to do a lot of digging through core files, and a lot of time just with trial and error. But, I finally did come up with something that works. I’m willing to bet that there is a better, more proper way to do it, but regardless, this seems to be working perfectly.

What I did was create a new PHTML file, created the proper block call in page.xml, and now I’ve got a

great working (and looking!) left-navigation. Here’s the home page (left), and a category page (right):

And the code:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

<h3>Browse by Category:</h3>

<ul>
<?php
$obj = new Mage_Catalog_Block_Navigation();
$store_cats	= $obj->getStoreCategories();
$current_cat 	= $obj->getCurrentCategory();

$current_cat	= (is_object($current_cat) ? $current_cat->getName() : '');

foreach ($store_cats as $cat) {
	if ($cat->getName() == $current_cat) {
		echo '<li><a href="'.$this->getCategoryUrl($cat).'">'.$cat->getName()."</a>\n<ul>\n";
		foreach ($obj->getCurrentChildCategories() as $subcat) {
			echo '<li><a href="'.$this->getCategoryUrl($subcat).'">'.$subcat->getName()."</a></li>\n";
		}
		echo "</ul>\n</li>\n";
	} else {
		echo '<li><a href="'.$this->getCategoryUrl($cat).'">'.$cat->getName()."</a></li>\n";
	}
}
?>
</ul>

If you know of a better way to do this – please let me know!

Product can be “on sale” in two ways:

1. when an item has a special price assigned to it on the individual level, or

2. when a special promotion “covers” the item

It is important to remember that you don’t have to set up the special price on each product to get it to be on sale; you can simply create a promotion rule and say something like “Set all the products in Category X to be on sale.”

I provided few screenshots at the bottom of this article to provide a closer look at what I’m talking about. I will not go into too much details here since this is a bit more advanced HOW TO, but here is the process in a nutshell:

First, create a copy of /catalog/product/list.phtml file and name it onsale_list.phtml. Here is my version of onsale_list.phtml file.

Second,  “activate” this new file. There are few ways you can do this. Let’s say you wish to assign this onsale_list.phtml on one of our categories, named “On Sale,” for instance.

We then go to Categories > Manage Categories > On Sale… select Custom design and under Custom layout update, place the following:

product_list_toolbar

If you now go to your category On Sale, it should only show products you have assigned to category “On sale” that have a special price set to them.

If you now wish to apply Promotion rules to entire “On sale” category, then you simply assign a rule to one item, and all the items assigned to the same “On sale” category (covered by promotion rules) will be automatically listed in the grid.

Basically, the magic is in one simple IF statement

< ?php if(($_product->special_price !== null) or ($_product->_rule_price !== null)): ?>

for each block that lists products.

Check out the screenshots, they explain a lot.

In any normal e-commerce website, it is a good thing to obviously show which products are new. This way you attract attention of your regular visitors and maybe you sell more and you extend the lifetime customer value. Anyway, it is pretty normal to put these new products in front of others in the catalog, or at least to make them conspicuous.

Although Magento allows you to configure start and end dates for a product in order to show it as new, the default Magento template doesn’t show it. This is the goal of this mini-tutorial : to show you how to show new products among old ones in a category list.

In fact, this is not complicated, you only have to know how to do it. This information I’ve found on this forum (french) doesn’t seem to be well known over the internet, but giving such informations might help a lot improving the Magento Community. Anyway. I’ve summerized it, put it in a real example, and even provided it as a download for lazy developers.

First, in the product page of some product in Magento’s backend, insert starting and ending dates for its newness state. To do a test, put (of course) a date before today’s date, and a date which is later as today’s date.

The code to add to access newness dates of a product is the following :

Static Block Created then called:

getLayout()->createBlock(‘cms/block’)->setBlockId(‘new-product-launch’)->toHtml()?>

which means you can just rename the local.xml.sample to local.xml to make all the error message print in the frondend.

Now you may have the errors for the toolbar pager as most of CE user will have their custom theme and the 1.3.2 and older all follow the same theme structure but in 1.4.0+ they change the toolbar class

1. Promotion
Block located in app\code\core\Mage\Catalog\Block\Product\List\Promotion.php

This is basically built in featured product functionality. It reacts to “promotion” attribute which needs to be created, so let’s click
Catalog->Attributes->Manage Attributes->Create New Attribute

Attribute Code: promotion
Scope: Global
Catalog Input Type for Store Owner: Yes/No

Promotion Products

Label: Promotion (second tab)

Other params can be left alone, but it’s up to you of course. I also labeled it Promotion just for this article.

Now we need to add created attribute to attribute set, so navigate to
Catalog->Attributes->Manage Attribute Sets
select attribute set you’re using and drag promotion to General group for example.

Now when you’re editing your products, there is new “Promotion” option under General tab.

Products on which you select Yes will be shown on promotion block which can be displayed through layouts with

<block type=”catalog/product_list_promotion” name=”product_promotion” template=”catalog/product/list.phtml”/>

or as cms content with

{{block type=’catalog/product_list_promotion’ template=’catalog/product/list.phtml’}}

This attribute should really be included in default attribute set or in Magento sample data.

2. Random
Block located in app\code\core\Mage\Catalog\Block\Product\List\Random.php

This block loads random product collection from current store.

The fastest way to display it would also be something like

<block type=”catalog/product_list_random” name=”product_random” template=”catalog/product/list.phtml”/>

since it also extends product_list block, however, since it is random product listing, that toolbar has no purpose here, so create phtml that will suit your shop needs, based on catalog/product/list.phtml. For example, i’m using similar Random block to display random products in sidebar.

Step 1 – Add a new product manually
add a new product manually to the catalog, assign it to a category, and fill out all fields that will be necessary to your store. The obvious ones are price, description, quantity etc. It’s important that you fill out all fields that you know you are going to need for all the products you import.

Step 2 – Export Your Products
Now we want to export your product to a .csv file so that we can view the fields that are required to import. Go to System >> Import/Export >> Profiles. Now click on Export All Products then Run Profile. Click on the “Run Profile in Popup” button. Once the export is completed, go to your var/export directory on your Magento install and you will find the .csv file there for you to download.

Step 3 – Analyze The .CSV File
Now if you look at your .csv export file you will see the field names that you need to match up. Now just start filling yours in and creating your csv file ready for import. This step is extremely important. Otherwise Magento cannot match what you are trying to import and the importing will fail. At a most basic level, here are the fields that I imported:

• store
• attribute_set
• type
• sku
• category_ids
• status
• visibility
• tax_class_id
• weight
• price
• name
• description

Step 4 – Import Your New .CSV File
Now go to System >> Import/Export >> Profiles. Now click on Import All Products. Change “Type” under Data Format to CSV/Tab Seperated. Now click on Upload File, and browse for your .csv file and click “Save and Continue Editing”. Now go to “Run Profile” and select your file from the dropdown menu. Click the button underneath to run the import. And whalllah. All your products should now be imported.

That was the easiest most simple approach that I could find for Importing Products into a Magento Open Source Ecommerce Store. Like I said I tried this myself and it worked well for me. After that, I went in and manually updated all of my Images and
Quantity numbers. You could even import those if you want to. But for
my purpose I didn’t need to.

Creating the new project
If you have installed the iPhone SDK/Xcode, then you can launch Xcode by navigating to /Developer/Applications. Once there, you can double click on the Xcode application (you may also find it handy to just drag the icon to the dock if you will be using it a lot).

Once Xcode launches, click File > New Project. Under the iPhone OS section on the left side of the resulting window, select “Application.” Select “View-based Application” from the templates that show up on the right side, and then click the “Choose” button. You will then be prompted to specify a project save name — this will also be the name of your resulting application, so choose your project name wisely.

You’re project has now been created, and the Xcode window that is displayed will contain all of your code, resources, etc. There isn’t much there now, but the application is fully functional at this point. You can click the “Build & Go” button in the toolbar, and the application will be compiled and launched in the iPhone Simulator. Again, this is a fully functional application, but it doesn’t do anything useful at this point — the usefulness of the app is up to your coding, but Apple supplies you with the base code and dependencies.

Using .xib files
XIB files are a “newer” format of Apple’s older NIB files. These files are where the user interface behind the Mac & iPhone applications is saved/packaged. The history of the NIB file is quite interesting and stretches back to the days of NeXT (you can read more about the history of Interface Builder here). You edit the user interface in an application called Interface Builder, which saves to these file types. When you double click on one of the files in Xcode, Interface Builder (IB) will automatically launch. Let’s double click on the MainWindow.xib file.

Once it loads, IB will display a mockup of an iPhone OS view. This view can have objects (buttons, text, etc.) placed on it, and linked to in the code. For this project, however, let’s make sure the Library window is open: Click Tools > Library (or press shift + command + L). In the Library, you will find all of the components that can make up an iPhone application. In the Library window, select “Objects,” and then click Library; In the search box type “text.” The search results will return two objects, but the one we want is the “Text View,” so drag that to the “Hello World View Controller” window, and the object will be “created.” If you double click where you just dragged the text view, then you will be able to edit the text that will be shown when the app launches. You can type what ever you wish, but we’ll use “Hello World!”

Once you have your text typed, select File > Save, from within IB; the information will be saved in the .xib file. Now close IB — you should see the Xcode application still opened.

Running your “Hello World!” iPhone app
Select “Build and Go” from the toolbar in Xcode. It will save the current project, compile the source code (along with the .xib file), and run it inside of the iPhone simulator. If you get an error while compiling, make sure that the build settings are set to “Simulator – iPhone OS 2.2.1.” You change this by clicking on the Overview drop-down menu on the tool bar; You can also change this by going to the Project > Set Active SDK menu.

Your application should launch in the simulator and display the text “Hello World!” So, congrats on your first iPhone application! Now you’re ready to start writing much cooler apps that take full advantage of the iPhone. If you don’t have Objective-C (or Cocoa) knowledge, I recommend that you backtrack to the post about useful Cocoa resources.

In the next iPhone Dev 101 post, I’ll talk about taking testing one step further by creating an Ad-hoc copy of your applications.

Purpose of the “Hello Universe” app
Using the app a user will be able to enter his/her full name and click a button to see a message appear. The message will say “John Doe says Hello Universe!!!”. This app will not only introduce you to some of the tools but will also show you how to use controls, respond to events and create new views. Excited, I am

This is how the app will look like

Creating a new project
Launch Xcode and click on File -> New Project -> Select Application (under iPhone OS) -> select Window-Based Application project template and click on choose.

In the next screen you will be asked to save your project and give it a name. Xcode creates some files for us based on the name of the project, so you want to be careful with the name you provide. I have named my project “HelloUniverse”.

This is how the list of files look like in Xcode.

All the class files are stored under the “Classes” folder, some special files are listed under “Other Sources”, all the view files and resources show up under “Resources”, and any library or frameworks we add to our project are listed under the “Frameworks” folder. It is important that we save all the images, files, databases, and views in the “Resources” folder because all the iPhone apps run in its own sand box; which means they can only access files placed under the resources folder.

How the app is launched
Every C/C++/Java/C# programmer knows about the main method found in main.m file which is present under the “Other Sources” folder. You normally will never have to change this method and all we have to know is that this method is responsible in launching the app. The method applicationDidFinishLaunching method is called when the app is launched on the device or the simulator. The method is defined in “HelloUniverseAppDelegate.m” file which is found under the “Classes” folder.

Interface Builder
Using Interface Builder we can design our application by adding controls or creating additional views. The files that the Interface Builder creates gets saved with a .xib extension and are called nib files. Every project gets one nib file by called which is called “MainWindow.xib” which can be found under “Resources”. An iPhone application has only one window (MainWindow.xib) unlike a desktop application which is created with multiple windows; however, we can create multiple views which are added to the window. Double click on “MainWindow.xib” to launch the Interface Builder, which will open four windows and one of the window will look like this

The above picture shows the contents of the “MainWindow.xib” nib file. Every nib file has atleast two files; File’s Owner and First Responder which cannot be deleted. Every other objects apart from the first two, represents an instance of an object which gets created when the nib file loads. File’s Owner simply shows that it owns the object in the nib file. First Responder tells us which object are we currently interacting with; like the textbox, buttons… The third object which is special to the MainWindow.xib file is called “Hello Universe App Delegate” and this file represents “HelloUniverseAppDelegate” class. Last but not the least the view represents the object which we design in our apps.

Creating a new view
If we had created this project using “View-Based Application” project template then there would have been no need of creating another view from scratch, but where is the fun in that. In Interface Builder create a new view by clicking File -> New -> Select Cocoa Touch -> View and click on choose. Let’s save the view in the project folder by naming it “HelloUniverse” and once we do that IB (Interface Builder) will prompt us to add the view to the current project; click on “Add” and it will show up in Xcode. In Xcode and move your view to the Resources folder.

Creating a view controller
We have a view now let’s create a view controller to manage the view. In Xcode create a new view controller by selecting classes and clicking File -> New File -> Select Cocoa Touch Classes under iPhone OS -> select UIViewController -> click on choose and name your file “HelloUniverseController” without changing the extension. The newly created class inherits from UIViewController which knows how to interact with a view. Now that we have our view and the controller class, there must be some way to connect these two files and we can do it by setting the class property of the File’s Owner. Double click “HelloUniverse.xib” file in Xcode to launch Interface Builder and select File’s Owner -> select Tools -> Identity Inspector and under “Class Identity” category, change the class to “HelloUniverseController”. This is how the Class Identity should look like

Once that is done we need a way to control the view in the nib file from code and this is done by connecting the view instance variable to the view object in the nib. The connection is made using “outlets”. Select Tools -> Connections Inspector create a connection from the view variable to the view in the nib file. Move your mouse over the empty circle to see it change to a plus symbol indicating that a connection can be created. Click on circle and drag your mouse to the view in the nib file and release. As you do this you will see a blue line being created from the circle to the mouse. Once a connection is created, the connections inspector for File’s Owner will look like this

Adding controls to the view
From the screen shot above we require two text boxes, one label, and a button (Round Rect Button). From the library drag and drop the controls to the view and align it as seen in the figure 1.0. After you have added the controls let’s change some of its properties, starting with the text boxes. Select the first text box and open Attributes Inspector by selecting Tools -> Attributes Inspector. Under Placeholder enter “First name”, under “Text Input Traits” change Capitalize property to “Words” and change the Return key property to “Done”. Apply the same settings for the other text box but change the Placeholder to say “Last name”. Select the label and delete its text property, since we do not want the label to say anything until the button is clicked. Double-click the button to edit the title of the button and type in “Click Me”. Save and quit Interface Builder as we have successfully designed our view.

Connecting instance variables to the objects in the view
We still need some way to interact with the controls on the view, in code and this is where outlets help us out. IBOutlet is a special keyword if used with an instance variable, will make the variable appear in Interface Builder. Since IBOutlet makes the variable appear in Interface Builder, using IBAction as a return type for a method will have the opposite effect. Using IBAction we can handle an event triggered by any control placed on the view. Let’s see how this works; open HelloUniverseController.h file in Xcode and type in the following code

All the variables above are marked with IBOutlet and Interface Builder will make these available to itself so proper connections can be made. We also have a method whose return type is IBAction (void); Interface Builder will also make this method available to itself so we can choose which event will call this method. The method also takes a parameter called “sender” which is the object which triggered the event. The variables are released in the dealloc method as shown above. Let’s connect these instance variables to the controls on the view (HelloUniverse) as described earlier. Open Interface Builder by double-clicking HelloUniverse.xib file and select File’s Owner, open Connections Inspector to see all the variables present under Outlets and to create connections.

Let’s hook up the button click event to the “btnClickMe_Clicked” method. Select the button and under the Events list it seems that we do not have a button click event; however, we do have a “Touch Up Inside” event which is raised when the button is touched and released symbolizing a click. With the button selected click the circle next to “Touch Up Inside” and drag your mouse over to File’s Owner and release to have the method name show; simply click on the method name to create a connection.

Handling events
Let’s write some code in btnClickMe_Clicked event to read the first and last name and display a message in the label. This is how the code looks like

The method does few simple things, it finds out the first and last names and figures out what message to display in the label. We also create a temporary variable called “Message” to hold the message which will be displayed in the label. The variable is allocated and initialized by alloc and initWithFormat messages respectively. The variable is released in the end because when working with the iPhone we are responsible of cleaning up the memory. The easiest way to remember when to release objects is; if you create it then you own the object and hence you are responsible of releasing it.

If you click on Build and Go, the view will not be visible because we have not yet added it to the window. Let’s see how we can do that

Adding view to the window
Now we cannot drag the view and add it to the window, so we need another way to add the view as a sub view to the window. We already know that “HelloUniverseController” is the view controller of the view “HelloUniverse” and “HelloUniverseAppDelegate” is the application delegate where the window is made visible in applicationDidFinishLaunching method. It is in that method we will add the view as a sub view to the window. Before we do that, the application delegate (HelloUniverseAppDelegate) needs to know about our view controller. Add the following lines to HelloUniverseAppDelegate.h file to change the file like this

From the above code we first add a forward class declaration of “HelloUniverseController” because we do not want any circular dependency when we import the header file of “HelloUniverseController” in HelloUniverseAppDelegate.m. A variable and a property of type HelloUniverseController is also declared. The property as you can see is declared with a couple of attributes called “retain” and “nonatomic”. The retain attribute will increase the reference count of the instance variable by one and nonatomic is used because our program is not multi-threaded.

A lot of first time users miss to synthesize the property we declared, so let’s do that now at the top of the HelloUniverseAppDelegate.m file and the code looks like this

The view is added as a subview to the window in applicationDidFinishLaunching method and this is how the code looks like

The second line shows that we imported the header file of “HelloUniverseController” and we also synthesized the property hvController. In the “olden” days in order to create a property we had to create getter and setter methods which would be something like getHVController and setHVController. The synthesize keyword automatically generates these methods for us. In applicationDidFinishLaunching method we allocate and initialize a temporary variable, assign it to our property, release it, and the view associated with the view controller is added as a sub view to the window. The key thing to remember here is that the view message is passed to the “hvController” which returns the view and is added as sub view to the window. A valid view is returned because we created a connection from the view instance variable to the view in the nib file. The property is finally released in the dealloc method as shown below

We have always allocated and initialized variables in one single line as seen below, this is usually the accepted way but the same code can be written in a different way as seen below

Build and go to test your application.

Hiding the keyboard
Wait a minute clicking the “Done” button doesn’t do anything. Ideally we would like to hide the keyboard when the “Done” button is clicked no matter which text box we are currently editing. To hide the keyboard we need to do two things; set the delegate of the keyboard to File’s Owner and implement a method called textFieldShouldReturn in HelloUniverseController.m file. To set the delegate, open Interface Builder by double clicking HelloUniverse.xib, select the first text box and click on Tools -> Connections Inspector. Click and drag your mouse by selecting the empty circle next to delegate under “Outlets” and release your mouse over to File’s Owner. Assign the delegate for the next text box in the same manner.

The method textFieldShouldReturn gets called when the “Done” button is clicked and this is how the code looks like

The method gets a parameter called sender, which is the object that triggered the event. We will use the same object to which we send the resignResponder message, which will hide the keyboard on the textbox. The boolean “Yes” is returned to tell the sender that the first responder is resigned.

PHPAsKS offers a full-service experience to clients and partners – that is PHPAsKS approach to software and application development.

Here at PHPAsKS, we understand that an idea needs to be protected and its value kept intact. After all, what would we develop if there were no ideas! So even before we talk to you about your requirements, we ensure that an NDA (Non-Disclosure Agreement) is put in place to protect your asset from day one.

Once your asset is secured, our experienced product managers will work with you first to identify the key goals and requirements of your app. These will be further developed into a “implementable” idea, taking into consideration your guidelines and key performance indicators.

The idea is then refined and prototyped to hand over to our designers – we ensure that any brand identity and values are retained throughout the design process, and your aesthetic requirements are met to the fullest extent.

Once the design is finalised, our team of programmers and technical experts take over and convert that prototype into a fully functioning application.

But we don’t just stop there. Once the product is tested, signed-off and deployed, we also provide you with statistical data and analytics on usage, downloads and other reporting. We think that the post-deployment process is as important as the creation of the app itself.

Whether it’s an “on the go” app, custom-designed for your business, or a “light-bulb moment” idea you’d like to market, we can develop, test, and deliver whatever you’ve got in mind.

At PHPAsKS, our iPhone developers specialise in all aspects of the iPhone development platform, spanning all mobile versions and operating systems.

Our iPhone development methodology and lifecycle processes are best suited to a quality driven approach, and all apps are optimised and tested before being deployed.

The PHPAsKS team of iPhone developers have years of experience developing on the Mac OS X platform, and are now utilising their skills on high quality and interative iPhone development.

If you are looking to hire an iPhone developer (or team of developers) for your project, PHPASKS can handle the entire development lifecycle for you from concept to execution, delivery and support.

Interested?
Find out more about our iPhone development services using the details on the right.

Our example form looks like this:

<input type="checkbox" name="foo" value="bar" />
<input type="button" onclick="show_checked()" value="Show" />
<input type="button" onclick="set_checked(true)" value="On" />
<input type="button" onclick="set_checked(false)" value="Off" />

There’s checkbox with name “foo” and then three buttons. The first calls a functionto show us if the checkbox is checked or not, and the second two change it from being checked to not being checked.

There are several ways to get to work out if a checkbox is checked or not with jQuery, and here a couple of alternatives. Each will return true if it’s checked or false if it’s not.

$('input[name=foo]').is(':checked')
$('input[name=foo]').attr('checked')

We can change the status of the checkbox using the attr() function like so, to check the box:

$('input[name=foo]').attr('checked', true);

and like so to uncheck the box:

$('input[name=foo]').attr('checked', false);

t’s looking for an element with id list which has a property value equal to 2. What you want is the option child of the list.
$(“#list option[value='2']“).text()

But sometimes you may need to get the selected option’s text. This is not as straight forward. First, we get the selected option with :selected selector. Then once we have the option, we can get the text with the function, text().

$("#list option:selected").text();
$j("#txt_employee_name option:selected").val() // Get the Option ID

Getting a form value with jQuery

To get a form value with jQuery use the val() function. Let's say we have a form like this, using an id for each form element:
<input name="foo" id="foo" type="text">

<select name="foo" id="bar">
    <option value="1">one</option>
    <option value="2">two</option>
    <option value="3">three</option>
</select>
We can display an alert for the values of "foo" and "bar" as easily this:
window.alert( $('#foo').val() );
window.alert( $('#bar').val() );
If we're using the name only and not specifying an id, the jQuery to get the form values would be this:
window.alert( $('[name=foo]').val() );
window.alert( $('[name=bar]').val() );
If you have a group of radio buttons and want to get the selected button, the code is slightly different because they all have the same name. Using the above code examples will show the value for the first radio button on the form with that name. To find out the value of the checked one, do this instead:

HTML:
<input type="radio" name="baz" value="x">
<input type="radio" name="baz" value="y">
<input type="radio" name="baz" value="z">
jQuery:
window.alert($('input[name=baz]:checked').val());
Setting a form value with jQuery
You can set the form values with jQuery using the same val() function but passing it a new value instead. Using the same example forms above, you'd do this for the text input and select box:
$('#foo').val('this is some example text');
$('#bar').val('3');
OR
$('[name=foo]').val('this is some example text');
$('[name=bar]').val('3');
Using the above for a radio button will change the actual value of the radio button rather than changing the one that is selected. To change the radio button that is selected you'd do this:
$('input[name="baz"]')[0].checked = true;
[0] would set the first one checked, [1] would set the second one checked and so on.

Create Selext Box In jQuery

Create a select box is very simple and straight forward. Just write a string with the normal select tag and a select box is created in jQuery

I bet everyone would have tried this and it work. However, manipulating might be a more challenging task.

Add Option In Select Box With jQuery

One easy way is to create a string with the whole element and create it straight away

Another way to create a list of elements is to create its option and append it in using pure jQuery.

You may not be familiar what i wrote above. Hence, a more javascript approach is shown below.

Get Select Box Value/Text In jQuery

Sometimes we want to know what is the value of the selected option. This is how we do it.

On the other hand, we can get the text of the option by doing this.

What if you know the value of the options you want to get instead of the one selected?

How about the first element on the select box?

How about the n element on the select box?

How about getting all elements but the first and last one in a select box?

Get Multiple Selected Value/Text In jQuery Select Box

Now we want to try to retrieve multiple selected values, we can do it easily with the following code.

How about storing these values?

This way we eliminate the additional index needed to follow through the loop! How about shorten the cold a bit?

This way we eliminate the need to create an array.

Remove Element In Select Box With jQuery

So we can get and add element into the select box. How about remove them? Basically, you will need to use one of the get element method describe above before applying the remove instruction.

Here we will remove all elements except the first and last one.

Select an option in the select box with jQuery

If you want to select an option in the select box, you can do this.

all option will be selected in this case.

UnSelect an option in the select box with jQuery

If you want to unselect an option in the select box, you can do this.

all option will be unselected n this case.

Best methods to optimize JPEG images for websites

While Internet connections becoming faster and faster, it’s still important to keep your website as fast as possible. One of the “slow” parts of your website are the images. In this article we show several ways to down-size the JPEG images for your website.

If you design your website should use some compression for your photos, banners and many other web elements. You favorite image editor should have some function to down-size your images. For this article we compare 4 ways to compress our example photo (file-size 393KB):

Adobe Photoshop

If you use the “Save for web…” function it’s possible to create a web optimized version from your image that is small enough and has a quality which is good enough for the Internet. In our example we used the preset “High Quality” which is equal to 60% quality. The result is a smaller file with a file-size of 95KB.

Adobe Fireworks

Fireworks is my favorite web image editor because of the unique feature to have bitmap and vector elements in a single file. We did an export with 80% quality and the compressed version has a file-size of 85KB.

GIMP (free Image Editor)

Both Adobe products are not free and are only available for Wndows or Mac. If you need a free editor you should try Gimp, an Image editor which many functions like the other commercial products mentioned before. The editor has also a “Safe for web” function and we used and 86% quality for our export file which becomes a size of 87KB. If you use GIMP to down-size your photos from your digital camera you should check the option “Strip EXIF”, removing the photo’s meta data will make the file smaller for another ~10KB.

ImageMagick (command line tools)

The last option is a tool we used via the command line. Using the following command the file is down-sized using an 80% quality (file size after conversion is 89KB):

convert original_100.jpg -quality 80 imagemagick_80.jpg

Sure this method works different from the other methods but the good point is that you can use this code in your PHP scripts or just from the command line of your web server.

Original image and compressed copies

Check the images below and note that the quality for the compressed images (file 2-5) is very similar.

The results after compression is very similar and the file size is between 85KB (fireworks) and 95KB (Photoshop). If you’re looking to down-size another 5-10%, you should try Smush.it a free service from Yahoo. They offer a tool which is able to optimize your images for 5-10% smaller file size without to lower the grade of quality.

Optimize your JPEG images with ImageMagick and PHP

If you need to optimize the images for your existing website, the following code might be useful:

<?php
$dir = '/home/some_directory/'; // the directory with your files
$compr = 80; // the quality precentage
if ($handle = opendir($dir)) {
	while (false !== ($file = readdir($handle))) {
		$path = $dir.$file;
		if (is_file($path)) {
			$ext = pathinfo($path, PATHINFO_EXTENSION);
			if (preg_match('/^(jpg|jpeg)$/i', $ext)) {
				exec(sprintf('convert %s -quality %d %s', $path, $compr, $path));
			}
		}
	}
	closedir($handle);
}
?>

Just enter the path to the the directory you like to optimize safe the code as a PHP script and execute the file from the command line of browser. Note only the JPEG files are getting compressed.

Optimize your images top make them load faster, but be careful don’t compress them too much.

Here are some obvious and not so obvious ways to ruin your WordPress website. Some of these will also destroy the relationships with your family and friends. In fact, I guarantee that if you follow these 150 simple steps, you will have a horrible WordPress website and very few friends.

Earlier this week I published a list of the best 101 WordPress plugins. Going a long with that huge list, I decided to come out with something similar…but from a different angle.

There are serious elements mixed in with some humor. Please note that I am not endorsing any of the illegal activities described in this post.

Let me know if I missed any WordPress ruining tips!

#1. Post every few months.

#2. Don’t check spelling or grammar on your posts.

#3. Post nude photos of your wife on the front page.

#4. Constantly change your permalink structure without creating 301 redirects. Google will love you for this.

#5. Post the same killer article every week with a different title.

#6. Copy content from another blog.

#7. Claim you have a PhD.

#8. Never flush your toilet.

#9. Use pink everywhere…especially as the main font color.

#10. Put a bunch of keywords at the bottom of your page, making the font color match the background.

#11. Lie about your age.

#12. Post about Brittany Spears every other day.

#13. Use the same post titles as your competitors.

#14. Copy someone’s post and claim that they stole your content in the comments of their article.

#15. Go to Yahoo Answers, create a question and then answer that question with a different account. Do this and repeat. Make sure you link to an article on your site in every answer.

#16. Spam Forums as much as possible

#17. Use slang words in your posts.

#18. Make sure your best posts are hidden from visitors.

#19. Make it difficult for users to find your home page.

#20. Add music that auto plays on your website. Do not provide a way to turn it off.

#21. Constantly submit your own articles to Digg and Reddit.

#22. Create 25 different twitter accounts and constantly retweet your posts.

#23. Claim you are the son/daughter of Brad Pitt.

#24. Make fun of anyone who comments on your posts.

#25. Stuff your site with ads.

#26. Make sure your contact and comment form are broken. If someone points this out to you, tell them it is because you get so much traffic.

#27. Only promote your website through prayer.

#28. Send an email to your friends with a link to your home page once per day.

#29. Make sure you spend a maximum of 10 minutes on each post.

#30. Put a massive amount of links in each post without explaining what they are for.

#31. Make sure each of your posts is in a different language.

#32. Tell everyone you have aids, but then say you are just kidding.

#33. Use a bright background color.

#34. Resize your images by changing the width and the height attributes.

#35. Make sure to use frames.

#36. Post stupid comments on other blogs because you know this will attract the most attention.

#37. Claim your blog is a joint effort of all the authors of your competitors.

#38. Make sure you require users to register to view your website…before you tell them what your website is about.

#39. Make fun of your family members on your website twice a week… preferably posts with photos.

#40. Include the F bomb with everyone you interact with on Twitter.

#41. Don’t respond to comments.

#42. Always post your titles in all caps.

#43. Whine about the government in every post.

#44. Use the default WordPress theme.

#45. Eat yellow snow.

#46. Put up an article about the top 100 ways to cheat Google.

#47. Make your about page a PDF file that you link to directly.

#48. Avoid using punctuation at all costs.

#49. Misspell post titles.

#50. Thinking that increased load time adds anticipation, make sure all images and photos are not optimized.

#51. On every page of your site, put a line asking people to click on your google ads.

#52. Use a domain name that doesn’t contain any words.

#53. Don’t let anyone under 18 view your website, even if it is not an adult website.

#54. Display a different main navigation menu on every page load.

#55. Click your own Google ads at least 10 times per day.

#56. Put the most popular search engine keywords on the web in the meta keywords field on every page of your site. Make sure to use at least 100 keywords.

#57. Claim your site is only meant to be viewed by men.

#58. Create a post about the top ten ways to be a terrorist.

#59. Make at least one racist comment per post.

#60. Make sure all text is tilted.

#61. Create a contest that offers $500 to the winner. But don’t pay up when the contest is over.

#62. Make sure to talk while you are eating when recording videos.

#63. Whine about your family in at least one post per week.

#64. Post your articles in English, but record and post videos in a different language.

#65. Go with the cheapest web host you can find, such as Blue Host. Specifically because they give you unlimited resources and your site will grow.

#66. Post as many one liner comments on as many blogs as possible.

#67. Write posts when you drunk.

#68. Lie to your customers about the price of your product.

#69. Advertise an ad that says “Buy one get five free!”, but after they place the order let them know that promotion ended last year.

#70. Create pages specifically for top keywords that have nothing to do with your website.

#71. Make fun of handicap people in a post once per week.

#72. Always make promises you cannot keep.

#73. Focus 100% on SEO, but don’t worry about how your visitors feel about your site.

#74. Submit your site to directories in the most high traffic categories, regardless of whether they match your content.

#75. Come out with a “your mom joke” once per week.

#76. If you didn’t graduate from college, make this the first thing your visitors know about your site.

#77. Sell marijuana by the pound on your products page.

Photo of some marijuana.

#78. Create a how to guide to being a prostitute.

#79. Post a link to a downloadable virus once per week.

#80. Sign-up your wife on dating sites.

#81. Write one post per week that features the word “retard”.

#82. Comment on your own articles using different names and email addresses.

#83. Install a spam bot on your server that posts spam comments on other blogs.

#84. Fill out as many contact forms as possible and only include a url to your site in the message/description.

#85. Offer to watch kids for a day, but then lock them up into a room. Just make sure to remember to feed them lunch.

#86. Ask for your friends ftp accounts for their websites, and then create a 301 redirect for all of them that goes to your site.

#87. Do not respond to emails any sooner than 2 weeks before you have received them.

#88. Never answer your cell phone.

#89. Do not pickup or do the dishes for 6 months straight.

#90. Email a virus to your friends as a practical joke.

#91. Make sure you charge 3x the amount for shipping as it actually costs.

#92. Post your admin password.

#93. Don’t update your plugins or WordPress installation….ever.

#94. Use your competitors logo for your website.

#95. Don’t include a site search.

#96. Never include photos in your posts.

#97. Urinate under your bed at least once per day.

#98. Use a crappy logo.

#99. Set all of your clocks to 3 hours behind.

#100. Require payment up front for any services you advertise, but don’t complete the service.

#101. Never do anything physical.

#102. Require all of your friends to post a comment once per week or you will never talk to them again.

#103. Never post on a topic that you have written about before.

#104. Block the google bot from accessing your website.

#105. Password protect your whole website, but don’t give anyone the password.

#106. Advertise sexual services on your blog.

#107. Make your main body text font size 10px.

#108. Make fun of a celebrity once per week.

#109. Put up a video of you barfing on your website.

#110. Put up all of your friends email addresses on your website.

#111. Make fun of your friends that are overweight.

#112. Make some of your text look like links, but they are not click able.

#113. Duplicate your killer articles at least 10 times on your site.

#114. Don’t do any research on SEO.

#115. Forget to renew your domain registration.

#116. If you are 13 years old or under, make sure you specify this in each of your posts.

#117. Claim that dropping out of high school is what everyone should do.

#118. Use post titles that do not relate at all with your content.

#119. Post your sister’s diary on your website. Make it a featured post.

#120. Only keep friends that are within 10 lbs of your weight. If they are more than that, tell them they need to gain/lose weight to be your friend.

#121. In your welcome message, say something like: “This website is only meant for Caucasian visitors who weigh less than 200 lbs.”.

#122. Randomly post a photo of a banana every day.

#123. Learn to type only with your feet.

#124. Post a Richard Simmons video once every two weeks.

#125. Never use the word “and” or “is”.

#126. Take photos off of the internet randomly, not caring if you have permission to use them or not.

#127. Forget about your wife on Valentine’s day.

#128. Create a post about each of your competitors and list out what you do not like about each website.

#129. Only test your browser in Chrome.

#130. Make your website 100% flash.

#131. Require everyone who visits your website to first download a pirated eBook.

#132. Claim you are a best-selling author.

#133. Forget to come into work for five days in a row.

#134. Only eat spam for a whole week.

#135. Take a shower once per 6 months.

#136. Put your parents phone number as the contact number on your website.

#137. Take a dump in the sink and tell your wife to clean it up.

#138. Pretend you are carrying a grenade on an airplane.

#139. Lock yourself into an airplane bathroom for the entire flight.

#140. Don’t check your site after upgrading your plugins.

#141. Redirect 404 pages to your competitors home page.

#142. Steal your neighbors pets.

#143. Poop in your neighbor’s lawn.

#144. Talk bad about your boss on your blog.

#145. Don’t create titles for your posts.

#146. Claim you have the #1 position for a popular search engine keyword.

#147. Post comments on other blogs, letting them know that your site is better than theirs.

#148. Forget to pay your hosting bill.

#149. Before you write any content, make sure you get at least 10,000 visitors to your domain.

#150. Exchange links with other websites, but take off their link after a few days.

Demo

Suffolk County Council

Web design and build / CMS integration / E-Newsletters / SEO

Visit the website

Earthmoves Design

Web design and build / CMS integration / Branding

Visit the website

Gwynedd Council

Web design and build / Site management

Visit the website

Keep your site fresh and up to date with our easy to use, yet powerful content management system

Try a demo or get a quote

Give new and existing customers a secure, easy to use platform to purchase from you online

Try a demo or get a quote

Send branded, rich, targeted email campaigns and track results using our E-Mail campaign system

Try a demo or get a quote

HTML Source Donwload

<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html dir="ltr" xml:lang="en-gb" xmlns="http://www.w3.org/1999/xhtml" lang="en-gb">
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title>Web design and online marketing by Blend, Ipswich, Suffolk, UK</title>
<link rel="stylesheet" href="http://www.phpasks.com/blogs/wp-content/uploads/2010/03/style.css" type="text/css" media="screen, projection">
<script type="text/javascript" src="http://www.phpasks.com/blogs/wp-content/uploads/2010/03/jquery.js"></script>
<script type="text/javascript" src="http://www.phpasks.com/blogs/wp-content/uploads/2010/03/jquery_minified.js"></script>
</head>
<body>
<div>
<div> <img src="http://www.phpasks.com/blogs/wp-content/uploads/2010/03/ssp.jpg" alt="Suffolk County Council" width="210" height="176">
<!-- START of .boxgrid caption -->
<div style="top: 127px;">
<h3>Suffolk County Council</h3>
<p>Web design and build / CMS integration / E-Newsletters / SEO</p>
<a bitly="BITLY_PROCESSED" href="http://www.phpasks.com/contact-us.html" title="visit the Transforming Suffolk website">Visit the website</a>
</div>
<!-- end of .boxgrid caption -->
</div>
<!-- end of .cover boxcaption -->
<div> <img src="http://www.phpasks.com/blogs/wp-content/uploads/2010/03/emd.jpg" alt="Earthmoves Design" width="210" height="176">
<div>
<h3>Earthmoves Design</h3>
<p>Web design and build / CMS integration / Branding</p>
<a bitly="BITLY_PROCESSED" href="http://www.phpasks.com/contact-us.html" title="visit the Earthmoves Design website">Visit the website</a> </div>
<!-- end of .boxgrid caption -->
</div>
<!-- end of .cover boxcaption -->
<div> <img src="http://www.phpasks.com/blogs/wp-content/uploads/2010/03/ghia.jpg" alt="Gwynedd Council" width="210" height="176">
<div>
<h3>Gwynedd Council</h3>
<p>Web design and build / Site management</p>
<a bitly="BITLY_PROCESSED" href="http://www.phpasks.com/contact-us.html" title="visit the Health Challenge Gwynedd website">Visit the website</a> </div>
<!-- end of .boxgrid caption -->
</div>
<!-- end of .cover boxcaption -->
<div>
<!-- end of .grid_4 -->
<div> <img src="http://www.phpasks.com/blogs/wp-content/uploads/2010/03/cms.jpg" alt="Manage your website with a content management system" width="210" height="176">
<div>
<p>Keep your site fresh and up to date with our easy to use, yet powerful content management system</p>
<p><a bitly="BITLY_PROCESSED" href="http://www.phpasks.com/contact-us.html" title="get a quote">Try a demo or get a quote</a></p>
</div>
<!-- end of .boxgrid caption -->
</div>
<!-- end of .cover boxcaption -->
<div> <img src="http://www.phpasks.com/blogs/wp-content/uploads/2010/03/ecom.jpg" alt="Sell online with our E-Commerce system" width="210" height="176">
<div>
<p>Give new and existing customers a secure, easy to use platform to purchase from you online</p>
<p><a bitly="BITLY_PROCESSED" href="http://www.phpasks.com/contact-us.html" title="get a quote">Try a demo or get a quote</a></p>
</div>
<!-- end of .boxgrid caption -->
</div>
<!-- end of .cover boxcaption -->
<div> <img src="http://www.phpasks.com/blogs/wp-content/uploads/2010/03/email.jpg" alt="Send email campaigns with our E-Mail Newsletter system" width="210" height="176">
<div>
<p>Send branded, rich, targeted email campaigns and track results using our E-Mail campaign system</p>
<p><a bitly="BITLY_PROCESSED" href="http://www.phpasks.com/contact-us.html" title="get a quote">Try a demo or get a quote</a></p>
</div>
<!-- end of .boxgrid caption -->
</div>
<!-- end of .cover boxcaption -->
</div>
</div>
<!--end of container_16 -->
</body>
</html>