[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pdt-dev] Post PDT 3.6 plans

Hi Dawid,

I don't have clear plans at the moment. We are close to Zend Studio release and after that it will be easier to make detailed list. But I can define areas of my interest:)
* Finish PHP 7 support (e.g. anonymous elements in Outline, CA for grouped use statements, etc.)
* Finish smart paste/indent optimization (speed and memory consumption)
* Also performance, but I'm not sure what exactly. For example I don't feel comfortable with actual building/indexing model. It is rater slow,Âinefficient and it's consuming a lot of memory:)
* Things around PHP editor in general

I also think it would be nice if we start assigning bugs in Bugzilla. It will give us better info what is going on.

Btw, I remember that there was plan to move Composer plugin to PDT. Any news about that?



On Fri, Sep 18, 2015 at 3:08 PM, Dawid PakuÅa <zulus@xxxxxxxxx> wrote:

new release itâs close to door so I have to ask for your plans.

From my point of view, next version should be at least minor release (3.7). My personal minimum plan:
* I want continue performance and consistency optimisation in TI and CA - for ex. bugÂ475525 [1] bugÂ438087 [2] bugÂ459947 [3]
* Merge Include and Build paths views - bugÂ444226 [4]
* Introduce extendable âsave-actionsâ - bugÂ462135 [5]
* Introduce PDT Help SDK to simplify help updates (like move / rename refactoring)

[1] - http://eclip.se/475525
[2] - http://eclip.se/438087
[3] - http://eclip.se/459947
[4] - http://eclip.se/444226
[5] - http://eclip.se/462135

BTW: This release will be latest with long (6 months) cycle. Since Neon, three rather than two sub-releases will be published.

Dawid PakuÅa
+48 795 996 064

pdt-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit