|Re: [pdt-dev] State of eclipse plugin development, any thoughts?|
current state is a nightmare :( Iâm talking from PDT developer state, and also as PDT Extensions developer/maintainer. On each release we improve quality of extension points and utils, but they still arenât developer friendly. But looks better than 3 years ago ;) 
For now, best place to see how things can be extened are plugins from PDT Extension Group . For example autoedit you can find in DoctrineEclipsePlugin 
Basic documentation (off course outdated :/) for WTP SSE you can find here .
Complexity is a problem for most mature eclipse projects. Especially if they inherited some code base from JDT. While analyzing PDT / WTP / DLTK code you can find many classes/structures that doing similar things. Sometime exactly the same.Â
PDT use WTP as core for it's editor, and DLTK to introduce PHP Language Specific elements, like Type Inference, Code Assist, Validation, Searching...
Try read basic PDT Extension Point Core-Plugin code  (core and ui). This should clear you many things.Â
Reply:ÂPDT Developers <pdt-dev@xxxxxxxxxxx>
Date:Â9 August 2016 at 16:56:00
Subject:Â [pdt-dev] State of eclipse plugin development, any thoughts?