[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [pdt-dev] Future of PDT development
- From: Robert Gründler <r.gruendler@xxxxxxxxx>
- Date: Wed, 11 Jul 2012 19:50:21 +0200
- Delivered-to: email@example.com
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=iB201KoJf6Qm3hvbUGrwXBumia1exJxbrtML4a4m3ec=; b=zc9qIzdOrZcAU72zNZz+OatvUwHLXH1NlvS0uJ4i23wuMt2Iau1P9BvyuTgMKvFf5d Rkn9agSpzDvBiMYB7BCJQ3tPNnenkycls7mwD8yjjGA1m2+6NF4kvqK37VrKk416fCMF fuDYcdrDcv+MVu4pExsNd5V7MFquO9P1iDCqC2UCRo6Ygf1dUzM7h8aPV45yrEyHbS5+ Fma5uKwqQ09rAQtk1dzJ9JcOXqP5qE0lnJGg6PGF/FuF/W4rKtMCk1d/R0ZCDts23Ioq SyJ+yG7gr7CokGPlEyeHlCPyuiyzJYMkcrPUnQo2L/BUej8Y7St4yx/Nx2/CAkfaKOwE GuLA==
On Wed, Jul 11, 2012 at 10:47 AM, Jacek PospychaÅa <jacek.p@xxxxxxxx>
it's great to hear about your plans. We always enjoyed seeing new plugins for PDT as this confirms there's strong PHP community around Eclipse. I'm even more happy now to hear that there's more to come.
Where can I follow your current discussion to better understand what you're planning/doing? Why not discuss or even develop this pdt-extension platform directly in PDT?
right now there's a github group  with a wiki and a google group where our discussion is taking place . Currently we're still in the planning phase. It would be great if the core features
could be discussed/developed directly with the PDT team.
From Zend pov, in the past the features that you mention were supposed to differentiate PDT and Zend Studio. Nowadays Zend Studio has gone in slightly different direction, and also more free alternatives popped up, so it's not argument any more.
But simply moving features between products takes us time, risk of regressions and gives no short term benefits. So although there's consensus in Zend that we could contribute back to PDT, it's hard to actually find time for that.
I understand. What i see for some features though is that there will be (or already are) duplicate implementations (see  for a small list what i've come up with). So maybe we can coordinate
this so those features are at least somehow distinct for the end-user in the menu structure (e.g. getter/setter generator or the new class wizard).
It would be optimal imho if we could merge some of this stuff in the future as the current situation leads to unnecessary workload on both sides ;)
In short term, until October we're very busy with next Zend Studio, but as part of that we want to get formatter better (bug 320130) and improve debugger. After that, we'll be more into bug fixing and planning next year, it'll be also good time
to give more love to PDT. By the end of the year we're also migrating PDT to Git and probably change it's build system.
That sounds great! Our short term goal is to provide a common p2 repository for all existing pdt extensions and figure out which parts of our plugins can be refactored into a more abstracted codebase.
The overall plan can be found on the wiki i've linked below.
Does this answer your questions?