I would like to share some PDT uses from a developer perspective. I use PDT for editing and source code management. These features are good enough, and will be more productive eventually.
However I felt lack of support for deployment features, all you get is external tools for local apache and basic page browsing. But Every time I modify a web page, I've to do rcp or use WinSCP to deploy that file back to the server and refresh page. Also, most of the times, It's essential to be connected with server on SSH connection to do regular fancy server stuff. WinSCP, although a great tool, isn't really "ergonomic excellence" and hence this tool switching becomes a painful activity.
It seems PDT is assuming that developers work only on development/staging machine and hence the lack of support for deployed web applications. Also based on my experience, I found PHP deployment to be very very different, fairly simple to be ridiculously near non-existence, compared to other "heavy-weight" web environment. Java, for example, has lots of "things" and steps to deploy a web app, but that's a different story...
I strongly recommend consideration for following features:
- Built in SSH command interface (remote terminal as console view ).
- Support for auto upload, or built in rcp (rsync builder - rsync as a part of auto-build would be a great feature!). Alternatively, this can be like MS Visual Studio style interface through HTTP interface, using HTTP methods (PUT etc.). Live Deployment feature is *essential*.
I'll post more uses of PDT as I go along using it.