Saturday, August 21, 2010

10 Reasons To Choose Drupal Over Joomla

   1. SEO Friendly URL’s – This is a pain in the butt with Joomla! It’s automatically built in with Drupal and very very easy to use.
   2. Easy To Use Admin Interface - I think Joomla tried a little too hard in this area. Drupal found a way to just make things more simple and not so overwhelming for the beginner user.
   3. Built In Blog – The blog that’s built in to Drupal is very easy to use and customize. Joomla really does not give a good blogging option at all surprisingly.
   4. Web Forms Plugin – This is a terrific plugin that I suggest you use. Just do a search for it on the website. Let’s you create as many of your own customized forms as you need. Very easy to use and very comprehensive.
   5. User Management – User roles and access control is so much easier to manage and maintain using Drupal. It makes multi-user websites easy to create rather than a pain in the neck.
   6. Ubercart – I just recently wrote about this shopping cart plugin for Drupal. Hands down the best shopping cart you will find for any content management system period.
   7. Drupal Taxonomy – Drupal’s way of categorizing content is such much better than Joomla. You can tell that it was way more thought out beforehand. This is important for anyone creating content rich websites.
   8. Meta Tags Plugin - a fantastic plugin allowing you to create custom meta keywords and more importantly descriptions for each page. Do a search for this one. Great Plugin.
   9. Page Title Plugin – Something Joomla does not currently have. A plugin that EASILY allows you to customize each pages Page Title. An absolute must for search engine optimization.
  10. Social Networking – For a major social network I of course choose elgg. However, if you are looking to build a more niche/smaller social network than Drupal is perfect. Again referencing to it’s user management capabilities combined with it’s Drupal Taxonomy to content manage all content Drupal makes for a fantastic easy to setup social network.

I wrote this post for two major reasons. First and foremost of course, to inform you the reader about Drupal and it’s advantages. The other is to hopefully in one way or the other encourage Joomla to “take it to another level” if you will. Hopefully it will help motivate Joomla contributors and creators to better re

fine the CMS that they have. If they don’t, people are gonna find out how much better Drupal is and stick with them.

Wednesday, August 11, 2010

jquery | show and hide div contents

sample coding

inside java script





Html Contents

Tuesday, August 10, 2010

PHP tips and tricks

Monday, August 9, 2010

CodeIgniter : A recommendation for PHP Programmer

Why I recommend PHP Programmers to use CodeIgniter?

Yes I’ve decided to use it along with this I’ve asked my programmer friends out there in office to use it. You’re wondering why I choose CodeIgniter rather than using Zend Framework, which add more values in PHP programmer’s career.Let’ me answer them all in the reasons below.
  1. The main issue which I got attracted with CodeIgniter is its performance. CodeIgniter is faster than other popular PHP MVC frameworks. Take a look at these Benchmark test done by Rasmus Lerdorf(creator of PHP programming), here , here in here. And also take a look at another benchmark test . So it’s clear that CI is faster than other Framework. Rasmus also told that he liked CodeIgniter because it is faster, lighter and the least like a framework.
  2. Another main reason behind recommendation, it has very low learning curve. CodeIgniter Downloads come with a tremendous user guide which is a great documentation like PHP Manual to begin with. And from my personal experience, CodeIgniter has very low learning curve compared to CakePHP and Zend Framework. If you’re a beginner for PHP frameworks then I recommend to go with CodeIgniter at begining.
  3. The coding conventions are flexible and simple. Ironically, CakePHP has very strict coding conventions so you must be very careful about cases of characters while coding.
  4. Why not Zend Framework and why CodeIgniter? Ok, one question goes here what is so good about Zend Framwork ? Eventual answer is ZF contain huge set of libraries and classes compared to any other framework. OK I agree, but another great news is that You can use Zend Framework’s classes in the CodeIgniter using hooks in CI. So you can use huge amount of Zend’s libraried in CI as well.
These are the main reason why I recommend for using CodeIgniter for PHP programmers.But I still believe that I’ll be using CakePHP for once I get final version of 1.2.0 because I still believe that it is robust,  has a  great design patters and great tool for group development .
If you recommend any other PHP framework, please let us know why you recomment that framework

Wednesday, August 4, 2010

40 Tips for optimizing your php code

1. If a method can be static, declare it static. Speed improvement is by a factor of 4.
2. echo is faster than print.
3. Use echo’s multiple parameters instead of string concatenation.
4. Set the maxvalue for your for-loops before and not in the loop.
5. Unset your variables to free memory, especially large arrays.
6. Avoid magic like __get, __set, __autoload
7. require_once() is expensive
8. Use full paths in includes and requires, less time spent on resolving the OS paths.
9. If you need to find out the time when the script started executing, $_SERVER[’REQUEST_TIME’] is preferred to time()
10. See if you can use strncasecmp, strpbrk and stripos instead of regex
11. str_replace is faster than preg_replace, but strtr is faster than str_replace by a factor of 4
12. If the function, such as string replacement function, accepts both arrays and single characters as arguments, and if your argument list is not too long, consider writing a few redundant replacement statements, passing one character at a time, instead of one line of code that accepts arrays as search and replace arguments.
13. It’s better to use switch statements than multi if, else if, statements.
14. Error suppression with @ is very slow.
15. Turn on apache’s mod_deflate
16. Close your database connections when you’re done with them
17. $row[’id’] is 7 times faster than $row[id]
18. Error messages are expensive
19. Do not use functions inside of for loop, such as for ($x=0; $x < count($array); $x) The count() function gets called each time. 20. Incrementing a local variable in a method is the fastest. Nearly the same as calling a local variable in a function. 21. Incrementing a global variable is 2 times slow than a local var. 22. Incrementing an object property (eg. $this->prop++) is 3 times slower than a local variable.
23. Incrementing an undefined local variable is 9-10 times slower than a pre-initialized one.
24. Just declaring a global variable without using it in a function also slows things down (by about the same amount as incrementing a local var). PHP probably does a check to see if the global exists.
25. Method invocation appears to be independent of the number of methods defined in the class because I added 10 more methods to the test class (before and after the test method) with no change in performance.
26. Methods in derived classes run faster than ones defined in the base class.
27. A function call with one parameter and an empty function body takes about the same time as doing 7-8 $localvar++ operations. A similar method call is of course about 15 $localvar++ operations.
28. Surrounding your string by ‘ instead of ” will make things interpret a little faster since php looks for variables inside “…” but not inside ‘…’. Of course you can only do this when you don’t need to have variables in the string.
29. When echoing strings it’s faster to separate them by comma instead of dot. Note: This only works with echo, which is a function that can take several strings as arguments.
30. A PHP script will be served at least 2-10 times slower than a static HTML page by Apache. Try to use more static HTML pages and fewer scripts.
31. Your PHP scripts are recompiled every time unless the scripts are cached. Install a PHP caching product to typically increase performance by 25-100% by removing compile times.
32. Cache as much as possible. Use memcached – memcached is a high-performance memory object caching system intended to speed up dynamic web applications by alleviating database load. OP code caches are useful so that your script does not have to be compiled on every request
33. When working with strings and you need to check that the string is either of a certain length you’d understandably would want to use the strlen() function. This function is pretty quick since it’s operation does not perform any calculation but merely return the already known length of a string available in the zval structure (internal C struct used to store variables in PHP). However because strlen() is a function it is still somewhat slow because the function call requires several operations such as lowercase & hashtable lookup followed by the execution of said function. In some instance you can improve the speed of your code by using an isset() trick.Ex.if (strlen($foo) < 5) { echo “Foo is too short”; }vs.

if (!isset($foo{5})) { echo “Foo is too short”; }

Calling isset() happens to be faster then strlen() because unlike strlen(), isset() is a language construct and not a function meaning that it’s execution does not require function lookups and lowercase. This means you have virtually no overhead on top of the actual code that determines the string’s length.
34. When incrementing or decrementing the value of the variable $i++ happens to be a tad slower then ++$i. This is something PHP specific and does not apply to other languages, so don’t go modifying your C or Java code thinking it’ll suddenly become faster, it won’t. ++$i happens to be faster in PHP because instead of 4 opcodes used for $i++ you only need 3. Post incrementation actually causes in the creation of a temporary var that is then incremented. While pre-incrementation increases the original value directly. This is one of the optimization that opcode optimized like Zend’s PHP optimizer. It is a still a good idea to keep in mind since not all opcode optimizers perform this optimization and there are plenty of ISPs and servers running without an opcode optimizer.
35. Not everything has to be OOP, often it is too much overhead, each method and object call consumes a lot of memory.
36. Do not implement every data structure as a class, arrays are useful, too
37. Don’t split methods too much, think, which code you will really re-use
38. You can always split the code of a method later, when needed
39. Make use of the countless predefined functions
40. If you have very time consuming functions in your code, consider writing them as C extensions