Hi Gossi, I agree that some concepts were moved from JDT to PDT to straightforward or are to complicated from PHP developer point of view. Build path is a good example:) I'm not regular PHP developer so I'm focusing on different areas and I think it would be great if you can help us with such unclear/over-complicated places.
Michal On Tue, Sep 22, 2015 at 3:00 PM, Thomas Gossmann <ecli...@gos.si> wrote: > Hi guys, > > I would like to assist David with the build path dialog. I was heavily > involved with this during composer plugin development and know the pitfalls > (especially from a Usability/UX perspective). > > Talking about Usability/UX. There is much more, even great features, that > are easily misunderstand or are overly complicated to achieve (I hit them > here and there). A review under these aspect might be very helpful to get > to know these pitfalls and should result in documenting guidelines for > this, so these concepts could be carried into plugins as well. This would > also include a dictionary kind of thing, e.g. what the hell is a build > path? there is no such thing as a build path within php. This would be > helpful for devs and end users. > > Regarding composer: I opened a new thread, just for this. > > gossi > > Am 21.09.15 um 02:00 schrieb Dawid Pakuła: > >> Hi, >> >> +1 for assigns. Too many bugs are closed during cycle. >> >> About composer plugin, as far as I know gossi didn't have a time during >> holiday, so for now this topic is dead. We could resurrect it in 3.7. >> Gossi? >> >> -- >> Dawid Pakuła >> +48 795 996 064 >> >> On 20 September 2015 at 21:19:21, Michał Niewrzał (micha...@zend.com >> <mailto:micha...@zend.com>) wrote: >> >> > 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?overcomplicated >> > >> > Michal >> > >> > >> > On Fri, Sep 18, 2015 at 3:08 PM, Dawid Pakuła <zu...@w3des.net >> > <mailto:zu...@w3des.net>> wrote: >> > >> > Hi, >> > >> > 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 <tel:%2B48%20795%20996%20064> >> > >> > _______________________________________________ >> > pdt-dev mailing list >> > pdt-dev@eclipse.org <mailto:pdt-dev@eclipse.org> >> > To change your delivery options, retrieve your password, or >> > unsubscribe from this list, visit >> > https://dev.eclipse.org/mailman/listinfo/pdt-dev >> > >> > >> > _______________________________________________ >> > pdt-dev mailing list >> > pdt-dev@eclipse.org >> > To change your delivery options, retrieve your password, or >> > unsubscribe from this list, visit >> > https://dev.eclipse.org/mailman/listinfo/pdt-dev >> >> >> _______________________________________________ >> pdt-dev mailing list >> pdt-dev@eclipse.org >> To change your delivery options, retrieve your password, or >> unsubscribe from this list, visit >> https://dev.eclipse.org/mailman/listinfo/pdt-dev >> >> > _______________________________________________ > pdt-dev mailing list > pdt-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/pdt-dev > On Tue, Sep 22, 2015 at 3:00 PM, Thomas Gossmann <ecli...@gos.si> wrote: > Hi guys, > > I would like to assist David with the build path dialog. I was heavily > involved with this during composer plugin development and know the pitfalls > (especially from a Usability/UX perspective). > > Talking about Usability/UX. There is much more, even great features, that > are easily misunderstand or are overly complicated to achieve (I hit them > here and there). A review under these aspect might be very helpful to get > to know these pitfalls and should result in documenting guidelines for > this, so these concepts could be carried into plugins as well. This would > also include a dictionary kind of thing, e.g. what the hell is a build > path? there is no such thing as a build path within php. This would be > helpful for devs and end users. > > Regarding composer: I opened a new thread, just for this. > > gossi > > Am 21.09.15 um 02:00 schrieb Dawid Pakuła: > >> Hi, >> >> +1 for assigns. Too many bugs are closed during cycle. >> >> About composer plugin, as far as I know gossi didn't have a time during >> holiday, so for now this topic is dead. We could resurrect it in 3.7. >> Gossi? >> >> -- >> Dawid Pakuła >> +48 795 996 064 >> >> On 20 September 2015 at 21:19:21, Michał Niewrzał (micha...@zend.com >> <mailto:micha...@zend.com>) wrote: >> >> > 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? >> > >> > Michal >> > >> > >> > On Fri, Sep 18, 2015 at 3:08 PM, Dawid Pakuła <zu...@w3des.net >> > <mailto:zu...@w3des.net>> wrote: >> > >> > Hi, >> > >> > 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 <tel:%2B48%20795%20996%20064> >> > >> > _______________________________________________ >> > pdt-dev mailing list >> > pdt-dev@eclipse.org <mailto:pdt-dev@eclipse.org> >> > To change your delivery options, retrieve your password, or >> > unsubscribe from this list, visit >> > https://dev.eclipse.org/mailman/listinfo/pdt-dev >> > >> > >> > _______________________________________________ >> > pdt-dev mailing list >> > pdt-dev@eclipse.org >> > To change your delivery options, retrieve your password, or >> > unsubscribe from this list, visit >> > https://dev.eclipse.org/mailman/listinfo/pdt-dev >> >> >> _______________________________________________ >> pdt-dev mailing list >> pdt-dev@eclipse.org >> To change your delivery options, retrieve your password, or >> unsubscribe from this list, visit >> https://dev.eclipse.org/mailman/listinfo/pdt-dev >> >> > _______________________________________________ > pdt-dev mailing list > pdt-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/pdt-dev >
_______________________________________________ pdt-dev mailing list pdt-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/pdt-dev
