1. Eclipse PHP Development Tools
(PDT) 3.0 – Indigo Release Review
Roy Ganor,
Project Lead

2. Introduction
• Indigo Release – PDT 3.0
• Emphasis on quality fixes and major
performance improvements
• Collaborating with the DLTK team

3. Features
• Core
– Improved indexing, optimized schema files
– Namespace representation was improved to
reflect the feedback from PDT 2.2
– Align with updated DLTK API
– Start using Eclipse API Tools to verify backward
compatibility
– Bug fixes

4. Features
• UI
– Project setting for base path was added,
streamlines the user experience when debug
configuration is used
– Improved semantic coloring to better represent
default requirements
– Content Assist fixes for namespace syntax

5. Non-Code Aspects
• Little has changed for PDT in it’s
documentation, state of internationalization,
etc.
• PDT wiki remains central repo for
documentation created over the release
– http://wiki.eclipse.org/PDT

6. API
phpDebugMessages
phpDebugHandlers
phpDebugParametersInitializers
phpWizardPages org.eclipse.php.debug.core phpExe
phpElementFilters
debugCommunicationDaemon
phpEditorTextHovers
phpTreeContentProviders
phpManualSites org.eclipse.php.debug.deamon
org.eclipse.php.ui phpManualDirectors
phpContentAssistProcessor
httpServerLaunchDelegate
phpOutlineElementComparers phpDebugModelPresentations
phpPreferencePageBlocks
foldingStructureProviders org.eclipse.php.server.core
org.eclipse.php.debug.ui
phpHyperlinkDetector
actionFilterContributors
serverTab
serverWizardFragment
org.eclipse.php.server.ui
includePathVariables
workspaceModelListener
phpBuilderExtensions
org.eclipse.php.core

7. API
• org.eclipse.php.core
– goalEvaluatorFactoriesPHP-Evaluator Factory
– PhpSourceElementRequestorsPHP Build Visitor
• org.eclipse.php.ui
– ActionFilterContributors–PHP Action FilterContributor
– FoldingStructureProvidersPHP Folding Structure Provider
– PhpActionDelegatorPHP Action Delegator
– PhpEditorTextHoversPHP Editor Text Hover
– PhpElementFiltersPHP Element Filter
– PhpFormatterPrefBlockPHP Formatter Preferences Block
– PhpFormatterProcessorPHP Formatter Processor

8. API
• org.eclipse.php.ui
– PhpHyperlinkDetectorPHP Hyperlink Detector
– PhpManualSitesPHP Manual URL
– PhpPreferencePageBlocksPHP
– Preferences Page Block PhpTreeContentProvidersPHP Tree Content
Provider
– PhpTreeElementComparersPHP Tree Element Comparer
– PhpWizardPagesPHP Wizard Page
– WizardAndCompositeFragmentsWizard and Composite Fragments
– QuickAssistProcessorsQuick Assist Processor
– QuickFixProcessorsQuick Fix Processor
• org.eclipse.php.debug.core
– fileMapper
– pathEntryFilters

9. API
• org.eclipse.php.debug.core
– phpDebuggers
– phpDebugHandlers
– phpDebugMessages
– phpDebugParametersInitializer
– phpDebugStepFilters
– PhpExe
– org.eclipse.php.debug.ui
– debugServerConnectionTest
– launchConfigurationTabs
– phpConsoleListeners
– phpDebugModelPresentations

10. Architectural Issues
• Little has changed in the PDT architecture in
this release

11. Bugzilla
blocker critical major normal minor trivial Total
P1 . 4 12 31 4 . 51
P2 . 5 15 53 7 2 82
P3 1 7 16 129 28 3 184
Total 1 16 43 213 39 5 317

12. Bugzilla
REOPENED REOPENED
NEW
Code Assist 26 4
Code Folding 5 .
Code Formatter 5 2
Core 25 4
Debugger 42 4
Documentation 8 .
Editor 49 6
General UI 44 4
Outline Views 13 1
PHP Explorer & Projects
36 7
management
PHP Manual 3 .
PHP Modeling 2 1
PHP Search 5 .
Problems view 2 .
Release Engineer 2 .
Templates 3 .
Updater 4 1
Website 11 .
Total 285 34

13. Standards
• PDT requires J2SE 1.5,
• Key driver for using 1.5 was the benefits of
generics-aware APIs
• Based on DLTK's standards, which are
relatively similar to JDT's standards
• Code standards remain the same as those for
the previous PDT 2.x versions

14. Schedule
• PDT follows the Indigo Release train schedule

15. IP
• The project leadership verifies that:
– ... that the about files and use licenses are in place as per the Guidelines to Legal
Documentation
– ... all contributions (code, documentation, images, etc) has been committed by individuals
who are either Members of the Foundation, or have signed the appropriate Committer
Agreement. In either case, these are individuals who have signed, and are abiding by, the
Eclipse IP Policy.
– ... that all significant contributions have been reviewed by the Foundation's legal staff. Include
references to the IPZilla numbers of all clearances.
– ... that all non-Committer code contributions, including third-party libraries, have been
documented in the release and reviewed by the Foundation's legal staff. Include references to
the IPZilla numbers of all clearances.
– ... that all Contribution Questionnaires have been completed
– ... the "copyright" field of each feature is set to the copyright owner (the Eclipse Foundation is
rarely the copyright owner).
– ... that any third-party logos or trademarks included in the distribution (icons, help file logos,
etc) have been licensed under the EPL.
– ... that any fonts or similar third-party images included in the distribution (e.g. in PDF or EPS
files) have been licensed under the EPL.

16. Many thanks to
the PDT and PHP communites!