1. Operating habits are similar, do not change
2. PDT is very good for F3 of class static functions and automatically directs to the correct class function, and phpeclipse only recognizes the function name, which will bounce out to let you select the class you want (if the function name exists in several classes).
3. PDT is poorly oriented for class non-static functions, and phpeclipse looks for function names and guides, processes and static functions are directed similar
4. PDT is not for non-PHP projects, many of my projects are built through SVN or CVS, the initial is not a PHP project. You can turn any project into a PHP project in the PHP view. PHPEclipse is much smarter than PDT, as long as it is PHP files (including. Inc etc, according to the project properties set) can be resolved, the new project can also be the same as the old directory.
5. PDT's PHP Explorer, has the PHP class and class method as a file of the sub-order, very user-friendly. PHPEclipse does not have this feature.
6. Both automatic prompts are very good. You can recognize custom functions and classes.
7. PDT builds a project to create a include_path file that can be found directly. PHPEclipse cannot view the Include_path file directly, only the associated items in the system.
8. The PDT editor does not have the right button shortcut menu for "show" and is not convenient for locating files.
9. PDT When selecting variables, can not highlight the other the same variable, a bad experience.
10. Continue the trial.