[pdt-dev] Develope pdt extension
Hi, I have two simple question for pdt. 1. Is any method to integrate pdtt tests with external pdt extensions? 2. Is there documentation for pdt developing (not only javadoc)? Thank you -- Dawid Pakuła +48 795 996 064 ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] Develope pdt extension
Czesc ;) Sorry for my english and thank you for your reply. I want (have to) write some tests for pdt-eg Core-Plugin validators (without this, extending its like a lottery). I was trying to use existing pdt test suite. At begin I want to use PHP54ErrorReportingTest but I each time I see in surefire report: java.lang.NoSuchMethodError: org.eclipse.dltk.core.IBuildpathEntry.isContainerEntry()Z at org.eclipse.php.internal.core.language.LanguageModelInitializer.enableLanguageModelFor(LanguageModelInitializer.java:181) at org.eclipse.php.internal.core.project.PHPNature.configure(PHPNature.java:158) at org.eclipse.core.internal.resources.NatureManager$1.run(NatureManager.java:144) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.resources.NatureManager.configureNature(NatureManager.java:159) at org.eclipse.core.internal.resources.NatureManager.configureNatures(NatureManager.java:205) at org.eclipse.core.internal.resources.Project.basicSetDescription(Project.java:102) at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1349) at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1378) at org.eclipse.php.core.tests.errors.PHP54ErrorReportingTests.setUpSuite(PHP54ErrorReportingTests.java:59) at org.eclipse.php.core.tests.errors.PHP54ErrorReportingTests$3.setUp(PHP54ErrorReportingTests.java:140) Thanks -- Dawid Pakuła +48 795 996 064 On Thursday, 7 February 2013 at 07:40, Jacek Pospychała wrote: > Czesc Dawid, > > re 1. do I correctly understand that you have some external pdt > extension and now you'd like to run pdtt tests on top of eclipse+your > extension? Or you'd like to write your own pdtt tests for your > extension? > So regarding running them, I'm sure you should be able to run PDT > tests from within Eclipse. You need to create JUnit Plug-in Test > launch configuration, make sure that it includes PDT plugins, PDT unit > tests and your extension and then just run PDT tests. > The unit tests to run are specified in test plugins pom.xml files: > org.eclipse.php.core.tests plugin -> main test suite is > org.eclipse.php.core.tests.AllTests > org.eclipse.php.ui.tests plugin -> main test suite is > org.eclipse.php.ui.tests.AllTests > > Once you have them running inside Eclipse, you should also be able to > get tests running automatically in Maven. > > Now if you'd like to write your own pdtt tests, you could try just > copy one of pdt test plugins and replace it with your tests. > > re 2. we have a wiki page, that you probably have already seen: > http://wiki.eclipse.org/PDT. It's not perfect, some data is quite old, > but most is still relevant. > There's also a community of PDT extenders, who created lots of > interesting PDT extensions. You might find it useful to look at their > source code, or even get in touch with them. > See Github https://github.com/pdt-eg and mailing list > https://groups.google.com/forum/#!forum/pdt-extensions-platform. > > Feel free to ask here if you have more specific questions, > > thanks > > Jacek > > On Wed, Feb 6, 2013 at 11:19 PM, Dawid Pakuła (mailto:dawid.pak...@w3des.net)> wrote: > > Hi, > > > > I have two simple question for pdt. > > 1. Is any method to integrate pdtt tests with external pdt extensions? > > 2. Is there documentation for pdt developing (not only javadoc)? > > > > Thank you > > -- > > Dawid Pakuła > > +48 795 996 064 > > > > > > ___ > > pdt-dev mailing list > > pdt-dev@eclipse.org (mailto:pdt-dev@eclipse.org) > > https://dev.eclipse.org/mailman/listinfo/pdt-dev > > > > ___ > pdt-dev mailing list > pdt-dev@eclipse.org (mailto:pdt-dev@eclipse.org) > https://dev.eclipse.org/mailman/listinfo/pdt-dev > > ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] Develope pdt extension
Hi You can forgot about this message ;) Problem was with pdt-eg Core-Plugin feature.xml. After mvn install I had in my local repository old pdt version (3.0.1). After fix I can easy integrate pdtt files in this plugin. Thanks -- Dawid Pakuła +48 795 996 064 On Thursday, 7 February 2013 at 19:09, Dawid Pakuła wrote: > Czesc ;) > > Sorry for my english and thank you for your reply. > I want (have to) write some tests for pdt-eg Core-Plugin validators (without > this, extending its like a lottery). > I was trying to use existing pdt test suite. At begin I want to use > PHP54ErrorReportingTest but I each time I see in surefire report: > > java.lang.NoSuchMethodError: > org.eclipse.dltk.core.IBuildpathEntry.isContainerEntry()Z > at > org.eclipse.php.internal.core.language.LanguageModelInitializer.enableLanguageModelFor(LanguageModelInitializer.java:181) > at > org.eclipse.php.internal.core.project.PHPNature.configure(PHPNature.java:158) > at > org.eclipse.core.internal.resources.NatureManager$1.run(NatureManager.java:144) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at > org.eclipse.core.internal.resources.NatureManager.configureNature(NatureManager.java:159) > at > org.eclipse.core.internal.resources.NatureManager.configureNatures(NatureManager.java:205) > at > org.eclipse.core.internal.resources.Project.basicSetDescription(Project.java:102) > at > org.eclipse.core.internal.resources.Project.setDescription(Project.java:1349) > at > org.eclipse.core.internal.resources.Project.setDescription(Project.java:1378) > at > org.eclipse.php.core.tests.errors.PHP54ErrorReportingTests.setUpSuite(PHP54ErrorReportingTests.java:59) > at > org.eclipse.php.core.tests.errors.PHP54ErrorReportingTests$3.setUp(PHP54ErrorReportingTests.java:140) > > > > Thanks > -- > Dawid Pakuła > +48 795 996 064 > > > On Thursday, 7 February 2013 at 07:40, Jacek Pospychała wrote: > > > Czesc Dawid, > > > > re 1. do I correctly understand that you have some external pdt > > extension and now you'd like to run pdtt tests on top of eclipse+your > > extension? Or you'd like to write your own pdtt tests for your > > extension? > > So regarding running them, I'm sure you should be able to run PDT > > tests from within Eclipse. You need to create JUnit Plug-in Test > > launch configuration, make sure that it includes PDT plugins, PDT unit > > tests and your extension and then just run PDT tests. > > The unit tests to run are specified in test plugins pom.xml files: > > org.eclipse.php.core.tests plugin -> main test suite is > > org.eclipse.php.core.tests.AllTests > > org.eclipse.php.ui.tests plugin -> main test suite is > > org.eclipse.php.ui.tests.AllTests > > > > Once you have them running inside Eclipse, you should also be able to > > get tests running automatically in Maven. > > > > Now if you'd like to write your own pdtt tests, you could try just > > copy one of pdt test plugins and replace it with your tests. > > > > re 2. we have a wiki page, that you probably have already seen: > > http://wiki.eclipse.org/PDT. It's not perfect, some data is quite old, > > but most is still relevant. > > There's also a community of PDT extenders, who created lots of > > interesting PDT extensions. You might find it useful to look at their > > source code, or even get in touch with them. > > See Github https://github.com/pdt-eg and mailing list > > https://groups.google.com/forum/#!forum/pdt-extensions-platform. > > > > Feel free to ask here if you have more specific questions, > > > > thanks > > > > Jacek > > > > On Wed, Feb 6, 2013 at 11:19 PM, Dawid Pakuła > (mailto:dawid.pak...@w3des.net)> wrote: > > > Hi, > > > > > > I have two simple question for pdt. > > > 1. Is any method to integrate pdtt tests with external pdt extensions? > > > 2. Is there documentation for pdt developing (not only javadoc)? > > > > > > Thank you > > > -- > > > Dawid Pakuła > > > +48 795 996 064 > > > > > > > > > ___ > > > pdt-dev mailing list > > > pdt-dev@eclipse.org (mailto:pdt-dev@eclipse.org) > > > https://dev.eclipse.org/mailman/listinfo/pdt-dev > > > > > > > ___ > > pdt-dev mailing list > > pdt-dev@eclipse.org (mailto:pdt-dev@eclipse.org) > > https://dev.eclipse.org/mailman/listinfo/pdt-dev > > > > > > > > ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] pdt 3.1.2 on 22 februari
Hi current pdt extensions requires pdt 3.2 nightly (kepler release) -- Pozdrawiam Dawid Pakuła +48 795 996 064 On Thursday, 21 February 2013 at 16:42, Sjaak Eenhuis wrote: > Hi there, > > According to the planning pdt 3.1.2 will be released tomorrow (22 febr). I am > curious about the improvements that will end up in the final release. > Is everything going all right? > > FYI I am using pdt-nightly now, and pdt-extensions conflicts with the nightly > [see screenshot]. I don't know wether this is due to pdt or pdt-extensions. > > thanks for all your work, > exceptione > ___ > pdt-dev mailing list > pdt-dev@eclipse.org (mailto:pdt-dev@eclipse.org) > https://dev.eclipse.org/mailman/listinfo/pdt-dev > > > > > Attachments: > - pdt-nightly-update-error.png > ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
[pdt-dev] Tracking structural changes / dependencies
Hi, I'm working on PDT Semantic Analysis (JDT Style), and I'm looking for best method for tracking structural changes after save (DLTK ScriptBuilder) and while writing (DLTK ReconcileBuilder). Now I've created simple BuildParticipant extension point for type searching, and prototype ScriptBuilder extension point for file dependency recording.: https://github.com/zulus/Core-Plugin/blob/semanticanalysis/org.pdtextensions.validation/src/org/pdtextensions/validation/test/BuildParticipant.java https://github.com/zulus/Core-Plugin/blob/semanticanalysis/org.pdtextensions.validation/src/org/pdtextensions/validation/DependencyBuilder.java https://github.com/zulus/Core-Plugin/blob/semanticanalysis/org.pdtextensions.validation/src/org/pdtextensions/validation/PEXProblem.java If any PEXProblem Import problem will be reported, DLTK will rebuild SourceModule if it finds new dependencies. Do you have a better method of PDT to track structural changes (Interface mods, new method in supertypes etc…)? -- Dawid Pakuła +48 795 996 064 ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
[pdt-dev] Two AST models and parsers
Hi PDT-team, while working on php 5.5 support for PDT I understood that this project have two very similar AST models and parsers for each one. Is this necessary? First model is older and is very similar to JDT/JSDT AST Second is extended DLTK generic model. (compiler AST) First model is used in ASTRewrite, Formatter etc… Second in DLTK TI framework, error reporting, etc... Each one contains own visitors, utils etc... Maybe is this possible to link them? This should improve performance and simplify the further development. Thanks, Dawid___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] Two AST models and parsers
One of JDT AST models contains also logic for FlowAnalysis. At first look PDT ASTs works like in JDT, but… Older (JDT like) AST contains binding resolver, which using compiler AST and sometimes whole DLTK TI framework. Older AST (JDT like) is mostly used directly in UI with many utils, functions and widget ported from JDT (many of them still contains java/jdt keyword in comments and strings). And as I see, it is always created while using editor. He has ability to record his changes. Second AST (compiler subnamespace) its created for DLTK integration, but it also used in outline, syntax coloring etc… This AST is cashed by DLTK In summary, it looks like an unfinished migration to DLTK. I do not see the terms of use of these models. Maybe will be possible to transform from one to another (by special visitor), instead of duplicating parsers. Dawid From: Alexey Panchenko Alexey Panchenko Actually, JDT also uses 2 ASTs :) One is used in indexing/search/model building etc - the so called compiler AST. It uses less resources, so can be created faster. The other one supports rewrite, so it uses more resources because of that and is used mostly for refactorings. Regards, Alex On Sat, Nov 16, 2013 at 1:01 AM, Seva Lapsha wrote: I have a good idea why. Because it it's a time consuming project to migrate everything. So it was decided to postpone it until there is necessary time frame. But as always happens the time never came. Now none of the people who took that decision is longer in the team :) So: "why" - is not really a helpful question IMO. The good questions are: "what" priority should the migration take and "when" should it happen. Hope this helps. On Fri, Nov 15, 2013 at 6:32 AM, Kaloyan Raev wrote: Good catch! I am currently working on improving performance in Zend Studio and noticed the same. Yet no idea why they both co-exist. Hopefully there is someone who still remember the early days of PDT. On Fri, Nov 15, 2013 at 1:17 PM, Dawid Pakuła wrote: Hi PDT-team, while working on php 5.5 support for PDT I understood that this project have two very similar AST models and parsers for each one. Is this necessary? First model is older and is very similar to JDT/JSDT AST Second is extended DLTK generic model. (compiler AST) First model is used in ASTRewrite, Formatter etc… Second in DLTK TI framework, error reporting, etc... Each one contains own visitors, utils etc... Maybe is this possible to link them? This should improve performance and simplify the further development. Thanks, Dawid ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] preliminary Eclipse PHP package
Hi interesting logo ;) Would be nice to add special welcome page with shortcuts to install most popular plugins like jQuery, EclipseColorThemes etc. If this is possible, and allowed be the rules of the Eclipse Foundation. As I remember this was suggested by Kaloyan Raev on PDT Extensions Platform discussion group. I think that also RSE (Remote System Explorer) should be bundled with this package. -- Dawid Pakuła +48 795 996 064 From: Jacek Pospychała Jacek Pospychała Reply: PDT Developers pdt-dev@eclipse.org Date: 17 grudnia 2013 at 20:27:04 To: PDT Developers pdt-dev@eclipse.org Subject: [pdt-dev] preliminary Eclipse PHP package hi, we're looking at having a PHP package on www.eclipse.org/downloads page for Luna release (June 2014): a downloadable and executable Eclipse preconfigured exclusively for PHP devs. There's an initial package available for testing, so if there's anybody willing to give it a try and share their feedback, please go to https://hudson.eclipse.org/packaging/job/luna.epp-tycho-build/ and look for Eclipse PHP product package, e.g. direct link to currently latest build #30: https://hudson.eclipse.org/packaging/job/luna.epp-tycho-build/30/artifact/org.eclipse.epp.packages/packages/org.eclipse.epp.package.php.product/target/products/ Jacek ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] preliminary Eclipse PHP package
I think about this: On welcome screen special button with for ex text: “Extend your PHP IDE” After click on it, widget/window will be opened with simple (but user friendly) plugin browser (categories, tags etc). On each plugin lead will be two buttons: Read more (open full market place info), Install (start install process) But how, where and by who data for this widget should be stored and collected I have no idea: Option 1: Probably as XML stored somewhere in eclipse infrastructure (in appropriate git repo?). Would be nice to read as many as we can information directly from marketplace (stars, description, comments Option 2: Use appropriate list of tags/categories/special markets and read all informations from marketplace (example tags: PHP, JavaScript, CSS, HTML). But in this model, we will be without control on content. -- Dawid Pakuła +48 795 996 064 From: Kaloyan Raev Kaloyan Raev Reply: PDT Developers pdt-dev@eclipse.org Date: 18 grudnia 2013 at 10:10:56 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] preliminary Eclipse PHP package Yes, there is a number of plugins, which are not hosted at eclipse.org and hence not included in the EPP package that can really enhance the experience of PHP developers. It would be great if we can somehow promote them on the Welcome screen. If we have them all registered at the Eclipse Marketplace, perhaps it will be possible to make them easily discovered from the PHP EPP package. Eclipse Foundation tdoes not prohibit (and even encourages) promoting Eclipse extensions (both open-source or proprietary) as long as all parties are treated equally (a.k.a. vendor neutrality). Dawid, Jacek, do you have an opinion how such promotion can be designed in the EPP package? Greetings, Kaloyan On Tue, Dec 17, 2013 at 10:22 PM, Dawid Pakuła wrote: Hi interesting logo ;) Would be nice to add special welcome page with shortcuts to install most popular plugins like jQuery, EclipseColorThemes etc. If this is possible, and allowed be the rules of the Eclipse Foundation. As I remember this was suggested by Kaloyan Raev on PDT Extensions Platform discussion group. I think that also RSE (Remote System Explorer) should be bundled with this package. -- Dawid Pakuła +48 795 996 064 From: Jacek Pospychała Jacek Pospychała Reply: PDT Developers pdt-dev@eclipse.org Date: 17 grudnia 2013 at 20:27:04 To: PDT Developers pdt-dev@eclipse.org Subject: [pdt-dev] preliminary Eclipse PHP package hi, we're looking at having a PHP package on www.eclipse.org/downloads page for Luna release (June 2014): a downloadable and executable Eclipse preconfigured exclusively for PHP devs. There's an initial package available for testing, so if there's anybody willing to give it a try and share their feedback, please go to https://hudson.eclipse.org/packaging/job/luna.epp-tycho-build/ and look for Eclipse PHP product package, e.g. direct link to currently latest build #30: https://hudson.eclipse.org/packaging/job/luna.epp-tycho-build/30/artifact/org.eclipse.epp.packages/packages/org.eclipse.epp.package.php.product/target/products/ Jacek ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] preliminary Eclipse PHP package
Hi, I think we can copy-paste plugins from PDT Extension Group [1] if they are available on Eclipse Marketplace. @Kaloyan I will try tonight [1] http://p2-dev.pdt-extensions.org/ -- Dawid Pakuła +48 795 996 064 From: Kaloyan Raev Kaloyan Raev Reply: PDT Developers pdt-dev@eclipse.org Date: 18 grudnia 2013 at 13:50:41 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] preliminary Eclipse PHP package Adding an “Extend your PHP IDE” link on the Welcome screen that launches an arbitrary UI is easy. I guess we now need to build the list of all potential plugins that would end in this plugin browser. Then we can start experimenting with the browser design so it fits to the complexity of the list we have. How about collecting all the plugins on a wiki page first, e.g. http://wiki.eclipse.org/PDT/Extensions ? Dawid, do you want to take the first round? Greetings, Kaloyan On Wed, Dec 18, 2013 at 12:57 PM, Dawid Pakuła wrote: I think about this: On welcome screen special button with for ex text: “Extend your PHP IDE” After click on it, widget/window will be opened with simple (but user friendly) plugin browser (categories, tags etc). On each plugin lead will be two buttons: Read more (open full market place info), Install (start install process) But how, where and by who data for this widget should be stored and collected I have no idea: Option 1: Probably as XML stored somewhere in eclipse infrastructure (in appropriate git repo?). Would be nice to read as many as we can information directly from marketplace (stars, description, comments Option 2: Use appropriate list of tags/categories/special markets and read all informations from marketplace (example tags: PHP, JavaScript, CSS, HTML). But in this model, we will be without control on content. -- Dawid Pakuła +48 795 996 064 From: Kaloyan Raev Kaloyan Raev Reply: PDT Developers pdt-dev@eclipse.org Date: 18 grudnia 2013 at 10:10:56 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] preliminary Eclipse PHP package Yes, there is a number of plugins, which are not hosted at eclipse.org and hence not included in the EPP package that can really enhance the experience of PHP developers. It would be great if we can somehow promote them on the Welcome screen. If we have them all registered at the Eclipse Marketplace, perhaps it will be possible to make them easily discovered from the PHP EPP package. Eclipse Foundation tdoes not prohibit (and even encourages) promoting Eclipse extensions (both open-source or proprietary) as long as all parties are treated equally (a.k.a. vendor neutrality). Dawid, Jacek, do you have an opinion how such promotion can be designed in the EPP package? Greetings, Kaloyan On Tue, Dec 17, 2013 at 10:22 PM, Dawid Pakuła wrote: Hi interesting logo ;) Would be nice to add special welcome page with shortcuts to install most popular plugins like jQuery, EclipseColorThemes etc. If this is possible, and allowed be the rules of the Eclipse Foundation. As I remember this was suggested by Kaloyan Raev on PDT Extensions Platform discussion group. I think that also RSE (Remote System Explorer) should be bundled with this package. -- Dawid Pakuła +48 795 996 064 From: Jacek Pospychała Jacek Pospychała Reply: PDT Developers pdt-dev@eclipse.org Date: 17 grudnia 2013 at 20:27:04 To: PDT Developers pdt-dev@eclipse.org Subject: [pdt-dev] preliminary Eclipse PHP package hi, we're looking at having a PHP package on www.eclipse.org/downloads page for Luna release (June 2014): a downloadable and executable Eclipse preconfigured exclusively for PHP devs. There's an initial package available for testing, so if there's anybody willing to give it a try and share their feedback, please go to https://hudson.eclipse.org/packaging/job/luna.epp-tycho-build/ and look for Eclipse PHP product package, e.g. direct link to currently latest build #30: https://hudson.eclipse.org/packaging/job/luna.epp-tycho-build/30/artifact/org.eclipse.epp.packages/packages/org.eclipse.epp.package.php.product/target/products/ Jacek ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] preliminary Eclipse PHP package
Hi Here https://wiki.eclipse.org/PDT/Extensions is draft version of plugin list (only some plugins from pdt-extensions.org). Any suggestions? Is the chosen document format ok? -- Dawid Pakuła +48 795 996 064 From: Dawid Pakuła Dawid Pakuła Reply: Dawid Pakuła zu...@w3des.net Date: 18 grudnia 2013 at 14:09:43 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] preliminary Eclipse PHP package Hi, I think we can copy-paste plugins from PDT Extension Group [1] if they are available on Eclipse Marketplace. @Kaloyan I will try tonight [1] http://p2-dev.pdt-extensions.org/ -- Dawid Pakuła +48 795 996 064 From: Kaloyan Raev Kaloyan Raev Reply: PDT Developers pdt-dev@eclipse.org Date: 18 grudnia 2013 at 13:50:41 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] preliminary Eclipse PHP package Adding an “Extend your PHP IDE” link on the Welcome screen that launches an arbitrary UI is easy. I guess we now need to build the list of all potential plugins that would end in this plugin browser. Then we can start experimenting with the browser design so it fits to the complexity of the list we have. How about collecting all the plugins on a wiki page first, e.g. http://wiki.eclipse.org/PDT/Extensions ? Dawid, do you want to take the first round? Greetings, Kaloyan On Wed, Dec 18, 2013 at 12:57 PM, Dawid Pakuła wrote: I think about this: On welcome screen special button with for ex text: “Extend your PHP IDE” After click on it, widget/window will be opened with simple (but user friendly) plugin browser (categories, tags etc). On each plugin lead will be two buttons: Read more (open full market place info), Install (start install process) But how, where and by who data for this widget should be stored and collected I have no idea: Option 1: Probably as XML stored somewhere in eclipse infrastructure (in appropriate git repo?). Would be nice to read as many as we can information directly from marketplace (stars, description, comments Option 2: Use appropriate list of tags/categories/special markets and read all informations from marketplace (example tags: PHP, JavaScript, CSS, HTML). But in this model, we will be without control on content. -- Dawid Pakuła +48 795 996 064 From: Kaloyan Raev Kaloyan Raev Reply: PDT Developers pdt-dev@eclipse.org Date: 18 grudnia 2013 at 10:10:56 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] preliminary Eclipse PHP package Yes, there is a number of plugins, which are not hosted at eclipse.org and hence not included in the EPP package that can really enhance the experience of PHP developers. It would be great if we can somehow promote them on the Welcome screen. If we have them all registered at the Eclipse Marketplace, perhaps it will be possible to make them easily discovered from the PHP EPP package. Eclipse Foundation tdoes not prohibit (and even encourages) promoting Eclipse extensions (both open-source or proprietary) as long as all parties are treated equally (a.k.a. vendor neutrality). Dawid, Jacek, do you have an opinion how such promotion can be designed in the EPP package? Greetings, Kaloyan On Tue, Dec 17, 2013 at 10:22 PM, Dawid Pakuła wrote: Hi interesting logo ;) Would be nice to add special welcome page with shortcuts to install most popular plugins like jQuery, EclipseColorThemes etc. If this is possible, and allowed be the rules of the Eclipse Foundation. As I remember this was suggested by Kaloyan Raev on PDT Extensions Platform discussion group. I think that also RSE (Remote System Explorer) should be bundled with this package. -- Dawid Pakuła +48 795 996 064 From: Jacek Pospychała Jacek Pospychała Reply: PDT Developers pdt-dev@eclipse.org Date: 17 grudnia 2013 at 20:27:04 To: PDT Developers pdt-dev@eclipse.org Subject: [pdt-dev] preliminary Eclipse PHP package hi, we're looking at having a PHP package on www.eclipse.org/downloads page for Luna release (June 2014): a downloadable and executable Eclipse preconfigured exclusively for PHP devs. There's an initial package available for testing, so if there's anybody willing to give it a try and share their feedback, please go to https://hudson.eclipse.org/packaging/job/luna.epp-tycho-build/ and look for Eclipse PHP product package, e.g. direct link to currently latest build #30: https://hudson.eclipse.org/packaging/job/luna.epp-tycho-build/30/artifact/org.eclipse.epp.packages/packages/org.eclipse.epp.package.php.product/target/products/ Jacek ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev m
Re: [pdt-dev] Two AST models and parsers
Hi Marek, At this moment both are required and it probably will not change for a long time DOM AST is a more complete and can be modified in runtime, unlike to compiler AST. I suggest you use a DOM AST together with ASTRewriter (very nice class ported from JDT). ASTRewriter use formatter internally and your SourceModules will be always formatted properly (in theory). I thought about it for class/interface and getter/setter generator for PDT-Eg Core Plugin. How to use ASTRewrite you can check here: https://github.com/pdt-eg/Core-Plugin/blob/master/org.pdtextensions.core.ui/src/org/pdtextensions/core/ui/contentassist/AssignToLocalCompletionProposal.java -- Dawid Pakuła +48 795 996 064 From: Marek Maksimczyk Marek Maksimczyk Reply: PDT Developers pdt-dev@eclipse.org Date: 20 grudnia 2013 at 19:42:06 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] Two AST models and parsers On 15.11.2013 23:26, Dawid Pakuła wrote: > One of JDT AST models contains also logic for FlowAnalysis. > > At first look PDT ASTs works like in JDT, but… Older (JDT like) AST contains > binding resolver, which using compiler AST and > sometimes whole DLTK TI framework. > Older AST (JDT like) is mostly used directly in UI with many utils, functions > and widget ported from JDT (many of them still > contains java/jdt keyword in comments and strings). And as I see, it is > always created while using editor. He has ability to > record his changes. > Second AST (compiler subnamespace) its created for DLTK integration, but it > also used in outline, syntax coloring etc… This > AST is cashed by DLTK > > In summary, it looks like an unfinished migration to DLTK. I do not see the > terms of use of these models. > > Maybe will be possible to transform from one to another (by special visitor), > instead of duplicating parsers. > > Dawid > Anyone can tell me, which AST should be use and will be developed in future? I would like to refactor class/interface wizard (creating code based on AST models). M.M ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
[pdt-dev] Cleanup PDT bugzilla
Hi PDT-Team, PDT bugzilla contain now over 600 opened bugs/tasks [1]. Many of them are outdated and when you open up this list, you do not know where to start. It would be good to gradually review and close these tasks. [1] https://bugs.eclipse.org/bugs/buglist.cgi?query_format=specific&bug_status=__open__&product=PDT&list_id=7958673 -- Dawid Pakuła +48 795 996 064 ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
[pdt-dev] Maintenance release
Hi, Eclipse project page [1] contain information about PDT 3.2.1 and 3.2.2 release. Is this release is still planned? [1] - https://projects.eclipse.org/projects/tools.pdt/documentation -- Dawid Pakuła +48 795 996 064___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] Tests
Hi,
how look your configuration?:
1. Selected test runner
2. OS what you are using
3. Product run (Main tab)
4. Program arguments and VM arguments (Arguments TAB).
This is my configuration for OSX, can be helpful:
Test runner: JUnit 4 (work with JUnit 3 also)
Product: org.eclipse.platform.ide
Program arguments:
-os ${target.os} -ws ${target.ws} -arch ${target.arch} -nl ${target.nl}
-consoleLog
VM arguments:
-Dosgi.requiredJavaVersion=1.6 -XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts -Xss8m -XX:MaxPermSize=1024m
-Xms120m -Xmx2048m -Xdock:icon=../Resources/Eclipse.icns -XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts
(-XstartOnFirstThread is required on OSX only).
If you run tests from maven you can copy/paste some surefire arguments ;)
--
Dawid Pakuła
+48 795 996 064
From: Marek Maksimczyk Marek Maksimczyk
Reply: PDT Developers pdt-dev@eclipse.org
Date: 6 lutego 2014 at 22:44:35
To: PDT Developers pdt-dev@eclipse.org
Subject: [pdt-dev] Tests
Hello,
I have problem with runing org.eclipse.php.core.test, I tried to run this as
JUnit Plugin Test but it looks like Runs (in JUnit view) don't increment and
tests freeze after few minutes (10-15). Is any particular way to run it in one
big package?
M.M
___
pdt-dev mailing list
pdt-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/pdt-dev
___
pdt-dev mailing list
pdt-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] Maintenance release
Hi, ping -- Dawid Pakuła +48 795 996 064 From: Dawid Pakuła Dawid Pakuła Reply: Dawid Pakuła zu...@w3des.net Date: 4 lutego 2014 at 23:29:11 To: PDT Developers pdt-dev@eclipse.org Subject: Maintenance release Hi, Eclipse project page [1] contain information about PDT 3.2.1 and 3.2.2 release. Is this release is still planned? [1] - https://projects.eclipse.org/projects/tools.pdt/documentation -- Dawid Pakuła +48 795 996 064___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
[pdt-dev] Gerrit issue
Hi pdt-commiters, I appologize, but I caucht on gerrit bug [1] :( I tried fix it manualy by git rebase, but without success. I temporary disabled pdt-gerrit job for this. Please do not push any new changes directly to pdt repo until webmaster fix this : [2]. [1] - http://code.google.com/p/gerrit/issues/detail?id=2374 [2] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=428338 -- Dawid Pakuła +48 795 996 064___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
[pdt-dev] Hudson job not working
Hi all, looks like, job pdt-master [1] not working correctly. No new builds since 2014-02-18. I haven’t privileges to this job, so I cannot check/repair it. Maybe its good time to move it to our HIPP instance ? [1] - https://hudson.eclipse.org/hudson/job/pdt-master/ -- Dawid Pakuła +48 795 996 064___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
[pdt-dev] Luna update site
Hi, If you have time, please look into this patch https://git.eclipse.org/r/25619. This patch requires WTP SourceEditing with latest commits, to fix deprecation highlighters while editing (available in latest commuter snapshot). I modified version in MANIEST.MF, switched repository to Luna and fixed broken tests (CSS in formatters and surefire configuration for UI). Unfortunately this patch will prevent PDT-dev updates on Kepler :( -- Dawid Pakuła +48 795 996 064 ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] preliminary Eclipse PHP package
Hi, I want refresh this thread, because latest luna milestone will be at 9 may. Next builds in theory should be RC. Any plan for this? Besides MPC have now public api [1] [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=432803 -- Dawid Pakuła +48 795 996 064 From: Kaloyan Raev kaloya...@zend.com Reply: PDT Developers pdt-dev@eclipse.org Date: 18 grudnia 2013 at 22:30:32 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] preliminary Eclipse PHP package Hi Dawid, > Here https://wiki.eclipse.org/PDT/Extensions is draft version of plugin list > (only some plugins from pdt-extensions.org). > Any suggestions? > Is the chosen document format ok? Thanks for starting this wiki. The format is good for start, we can adjust it later as needed. I added just a few of the features of Zend Studio that can be listed. So far, I can see that we will have around 10 categories with a number of features (between 1 and 20) in each of them. There will be both open source and commercial features, and even some features (e.g. PHPUnit) will have an open source and commercial alternatives. This looks pretty similar to the Mylyn case. Please, have a look at the Mylyn Connector Discovery. It seems to me like a good fit for our case too. We can use the same technology for "PDT Extension Discovery". Greetings, Kaloyan On Wed, Dec 18, 2013 at 7:56 PM, Dawid Pakuła wrote: Hi Here https://wiki.eclipse.org/PDT/Extensions is draft version of plugin list (only some plugins from pdt-extensions.org). Any suggestions? Is the chosen document format ok? -- Dawid Pakuła +48 795 996 064 From: Dawid Pakuła Dawid Pakuła Reply: Dawid Pakuła zu...@w3des.net Date: 18 grudnia 2013 at 14:09:43 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] preliminary Eclipse PHP package Hi, I think we can copy-paste plugins from PDT Extension Group [1] if they are available on Eclipse Marketplace. @Kaloyan I will try tonight [1] http://p2-dev.pdt-extensions.org/ -- Dawid Pakuła +48 795 996 064 From: Kaloyan Raev Kaloyan Raev Reply: PDT Developers pdt-dev@eclipse.org Date: 18 grudnia 2013 at 13:50:41 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] preliminary Eclipse PHP package Adding an “Extend your PHP IDE” link on the Welcome screen that launches an arbitrary UI is easy. I guess we now need to build the list of all potential plugins that would end in this plugin browser. Then we can start experimenting with the browser design so it fits to the complexity of the list we have. How about collecting all the plugins on a wiki page first, e.g. http://wiki.eclipse.org/PDT/Extensions ? Dawid, do you want to take the first round? Greetings, Kaloyan On Wed, Dec 18, 2013 at 12:57 PM, Dawid Pakuła wrote: I think about this: On welcome screen special button with for ex text: “Extend your PHP IDE” After click on it, widget/window will be opened with simple (but user friendly) plugin browser (categories, tags etc). On each plugin lead will be two buttons: Read more (open full market place info), Install (start install process) But how, where and by who data for this widget should be stored and collected I have no idea: Option 1: Probably as XML stored somewhere in eclipse infrastructure (in appropriate git repo?). Would be nice to read as many as we can information directly from marketplace (stars, description, comments Option 2: Use appropriate list of tags/categories/special markets and read all informations from marketplace (example tags: PHP, JavaScript, CSS, HTML). But in this model, we will be without control on content. -- Dawid Pakuła +48 795 996 064 From: Kaloyan Raev Kaloyan Raev Reply: PDT Developers pdt-dev@eclipse.org Date: 18 grudnia 2013 at 10:10:56 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] preliminary Eclipse PHP package Yes, there is a number of plugins, which are not hosted at eclipse.org and hence not included in the EPP package that can really enhance the experience of PHP developers. It would be great if we can somehow promote them on the Welcome screen. If we have them all registered at the Eclipse Marketplace, perhaps it will be possible to make them easily discovered from the PHP EPP package. Eclipse Foundation tdoes not prohibit (and even encourages) promoting Eclipse extensions (both open-source or proprietary) as long as all parties are treated equally (a.k.a. vendor neutrality). Dawid, Jacek, do you have an opinion how such promotion can be designed in the EPP package? Greetings, Kaloyan On Tue, Dec 17, 2013 at 10:22 PM, Dawid Pakuła wrote: Hi interesting logo ;) Would be nice to add special welcome page with shortcuts to install most popular plugins like jQuery, EclipseColorThemes etc. If this is possible, and allowed be the rules of the Eclipse Foundation. As I remember this was suggested by Kaloyan Raev on PDT Extensions Platform discussion group. I think that also RSE (Remote S
Re: [pdt-dev] preliminary Eclipse PHP package
Hi, Jacek: thank you for explanation. One problem is here, snapshots are not signed. Kaloyan: live is brutal ;) Maybe, we move PDT Extension Discovery idea into bugzilla? [1] - http://build.eclipse.org/simrel/luna/reporeports/reports/verifydiroutput/unsigned.txt -- Dawid Pakuła +48 795 996 064 w3des.net ul. Grabiszyńska 108/10 53-437 Wrocław NIP: 894-293-95-95 REGON: 340769757 From: Kaloyan Raev kaloya...@zend.com Reply: PDT Developers pdt-dev@eclipse.org Date: 28 kwietnia 2014 at 13:12:28 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] preliminary Eclipse PHP package Initially I planned to implement the PDT Extension Discovery wizard for Luna, but then my schedule became pretty tight. Most probably I will be able to work on this for SR1. The MPC public API is indeed a helpful improvement. On Mon, Apr 28, 2014 at 1:30 PM, Jacek Pospychała wrote: In the past we did code freeze and then rebuild per-request only. That is we would add a new p2 repository for 3.3 (.../updates/3.3-release), put there latest nightly build (from May 9th) and also update simrel repository with release repository url. Then we'd keep running nightly builds and copy nightly to release when requested. Finally we'd end up with one of nighly builds becoming a 3.3 release. Makes sense? On Mon, Apr 28, 2014 at 10:41 AM, Dawid Pakuła wrote: > Hi, > > I want refresh this thread, because latest luna milestone will be at 9 may. > Next builds in theory should be RC. > Any plan for this? > > Besides MPC have now public api [1] > > [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=432803 > > -- > Dawid Pakuła > +48 795 996 064 > > > From: Kaloyan Raev kaloya...@zend.com > Reply: PDT Developers pdt-dev@eclipse.org > Date: 18 grudnia 2013 at 22:30:32 > > To: PDT Developers pdt-dev@eclipse.org > Subject: Re: [pdt-dev] preliminary Eclipse PHP package > > Hi Dawid, > >> Here https://wiki.eclipse.org/PDT/Extensions is draft version of plugin >> list (only some plugins from pdt-extensions.org). >> Any suggestions? >> Is the chosen document format ok? > > Thanks for starting this wiki. The format is good for start, we can adjust > it later as needed. > > I added just a few of the features of Zend Studio that can be listed. > > So far, I can see that we will have around 10 categories with a number of > features (between 1 and 20) in each of them. There will be both open source > and commercial features, and even some features (e.g. PHPUnit) will have an > open source and commercial alternatives. > > This looks pretty similar to the Mylyn case. Please, have a look at the > Mylyn Connector Discovery. It seems to me like a good fit for our case too. > We can use the same technology for "PDT Extension Discovery". > > Greetings, > Kaloyan > > > On Wed, Dec 18, 2013 at 7:56 PM, Dawid Pakuła wrote: >> >> Hi >> >> Here https://wiki.eclipse.org/PDT/Extensions is draft version of plugin >> list (only some plugins from pdt-extensions.org). >> Any suggestions? >> Is the chosen document format ok? >> -- >> Dawid Pakuła >> +48 795 996 064 >> >> From: Dawid Pakuła Dawid Pakuła >> Reply: Dawid Pakuła zu...@w3des.net >> Date: 18 grudnia 2013 at 14:09:43 >> >> To: PDT Developers pdt-dev@eclipse.org >> Subject: Re: [pdt-dev] preliminary Eclipse PHP package >> >> Hi, >> >> I think we can copy-paste plugins from PDT Extension Group [1] if they are >> available on Eclipse Marketplace. >> >> @Kaloyan I will try tonight >> >> [1] http://p2-dev.pdt-extensions.org/ >> -- >> Dawid Pakuła >> +48 795 996 064 >> >> From: Kaloyan Raev Kaloyan Raev >> Reply: PDT Developers pdt-dev@eclipse.org >> Date: 18 grudnia 2013 at 13:50:41 >> To: PDT Developers pdt-dev@eclipse.org >> Subject: Re: [pdt-dev] preliminary Eclipse PHP package >> >> Adding an “Extend your PHP IDE” link on the Welcome screen that launches >> an arbitrary UI is easy. >> >> I guess we now need to build the list of all potential plugins that would >> end in this plugin browser. Then we can start experimenting with the browser >> design so it fits to the complexity of the list we have. >> >> How about collecting all the plugins on a wiki page first, e.g. >> http://wiki.eclipse.org/PDT/Extensions ? >> Dawid, do you want to take the first round? >> >> Greetings, >> Kaloyan >> >> >> On Wed, Dec 18, 2013 at 12:57 PM, Dawid Pakuła wrote: >>> >>> I think about this: >>> >>> On welcome screen special button w
Re: [pdt-dev] Fwd: [cross-project-issues-dev] Contribute project styling for the dark theme
Hi, I sent patch for review: https://git.eclipse.org/r/25787 I’m not sure if I should escape preference values (# or \# in css). I’ll perform some tests tonight and probably merge this patch. -- Dawid Pakuła +48 795 996 064 From: Jacek Pospychała jacek.pospych...@gmail.com Reply: PDT Developers pdt-dev@eclipse.org Date: 30 kwietnia 2014 at 07:13:42 To: PDT Developers pdt-dev@eclipse.org Subject: [pdt-dev] Fwd: [cross-project-issues-dev] Contribute project styling for the dark theme anyone willing to add dark theme to PDT editor? looks like low hanging fruit -- Forwarded message -- From: Lars Vogel Date: Wed, Apr 30, 2014 at 6:28 AM Subject: [cross-project-issues-dev] Contribute project styling for the dark theme To: cross-project-issues-...@eclipse.org Hi, in the recent integration builds (or M7) the platform team supports styling of UI related properties. This allows projects to contribute reasonable defaults for syntax highlighting for the integrated dark theme. See the attached files. xml-editor.png shows how a not styled editor would look like and colorsyntaxhightlighs.png shows the styled Java editor. I could like to encourage projects to contribute their settings to the dark theme. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=433475 for the general discussion and https://bugs.eclipse.org/bugs/show_bug.cgi?id=433605 for an example how to style JDT (which I plan to contribute for RC1, via 433605). For several projects I created already bugs to contribute that. If you are interested, please create a bug and add it to 433475. Best regards, Lars ___ cross-project-issues-dev mailing list cross-project-issues-...@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
[pdt-dev] Bootleneck in PerFileModelAccessCache.getTypes()
Hi pdt devs I have a question for IModelAccessCache and its main implementation PerFileModelAccessCache used by DefaultBindingResolver (semantic highlights, override indicator etc..). Line 222 is problematic for me. If method .getTypes is called for IType which is not from SourceModule connected to PerFileModelAccessCache, this line trying to load All ITypes from project! So, because often one class is using types from other files, in general all types are loaded during each semantic highlight / override detection! Someone remember why this class always doing it (this code have 3 years). -- Dawid Pakuła +48 795 996 064 ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] preliminary Eclipse PHP package
Hi, I pushed my one of the three pending patches, but 3.3 nightly site does not update after build. -- Dawid Pakuła +48 795 996 064 From: Jacek Pospychała jacek.pospych...@gmail.com Reply: PDT Developers pdt-dev@eclipse.org Date: 12 maja 2014 at 07:44:36 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] preliminary Eclipse PHP package hi, as mentioned earlier, I added PDT release repository[1] and seeded it with latest nightly build (and signed it). If you still have any updates for Luna, please push them to nightly and let me know. cheers Jacek [1] - http://download.eclipse.org/tools/pdt/updates/3.3 On Mon, Apr 28, 2014 at 6:44 PM, Jacek Pospychała wrote: > I'll sign them. > > On Mon, Apr 28, 2014 at 5:22 PM, Dawid Pakuła wrote: >> Hi, >> >> Jacek: thank you for explanation. One problem is here, snapshots are not >> signed. >> >> Kaloyan: live is brutal ;) Maybe, we move PDT Extension Discovery idea into >> bugzilla? >> >> [1] - >> http://build.eclipse.org/simrel/luna/reporeports/reports/verifydiroutput/unsigned.txt >> >> -- >> Dawid Pakuła >> +48 795 996 064 >> >> w3des.net >> ul. Grabiszyńska 108/10 >> 53-437 Wrocław >> NIP: 894-293-95-95 >> REGON: 340769757 >> >> From: Kaloyan Raev kaloya...@zend.com >> Reply: PDT Developers pdt-dev@eclipse.org >> Date: 28 kwietnia 2014 at 13:12:28 >> >> To: PDT Developers pdt-dev@eclipse.org >> Subject: Re: [pdt-dev] preliminary Eclipse PHP package >> >> Initially I planned to implement the PDT Extension Discovery wizard for >> Luna, but then my schedule became pretty tight. Most probably I will be able >> to work on this for SR1. >> >> The MPC public API is indeed a helpful improvement. >> >> >> On Mon, Apr 28, 2014 at 1:30 PM, Jacek Pospychała >> wrote: >>> >>> In the past we did code freeze and then rebuild per-request only. >>> That is we would add a new p2 repository for 3.3 >>> (.../updates/3.3-release), put there latest nightly build (from May >>> 9th) and also update simrel repository with release repository url. >>> Then we'd keep running nightly builds and copy nightly to release when >>> requested. >>> Finally we'd end up with one of nighly builds becoming a 3.3 release. >>> Makes sense? >>> >>> On Mon, Apr 28, 2014 at 10:41 AM, Dawid Pakuła wrote: >>> > Hi, >>> > >>> > I want refresh this thread, because latest luna milestone will be at 9 >>> > may. >>> > Next builds in theory should be RC. >>> > Any plan for this? >>> > >>> > Besides MPC have now public api [1] >>> > >>> > [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=432803 >>> > >>> > -- >>> > Dawid Pakuła >>> > +48 795 996 064 >>> > >>> > >>> > From: Kaloyan Raev kaloya...@zend.com >>> > Reply: PDT Developers pdt-dev@eclipse.org >>> > Date: 18 grudnia 2013 at 22:30:32 >>> > >>> > To: PDT Developers pdt-dev@eclipse.org >>> > Subject: Re: [pdt-dev] preliminary Eclipse PHP package >>> > >>> > Hi Dawid, >>> > >>> >> Here https://wiki.eclipse.org/PDT/Extensions is draft version of plugin >>> >> list (only some plugins from pdt-extensions.org). >>> >> Any suggestions? >>> >> Is the chosen document format ok? >>> > >>> > Thanks for starting this wiki. The format is good for start, we can >>> > adjust >>> > it later as needed. >>> > >>> > I added just a few of the features of Zend Studio that can be listed. >>> > >>> > So far, I can see that we will have around 10 categories with a number >>> > of >>> > features (between 1 and 20) in each of them. There will be both open >>> > source >>> > and commercial features, and even some features (e.g. PHPUnit) will have >>> > an >>> > open source and commercial alternatives. >>> > >>> > This looks pretty similar to the Mylyn case. Please, have a look at the >>> > Mylyn Connector Discovery. It seems to me like a good fit for our case >>> > too. >>> > We can use the same technology for "PDT Extension Discovery". >>> > >>> > Greetings, >>> > Kaloyan >>> > >>> > >>> > On Wed, Dec 18, 2013 at 7:56 PM, Dawid Pakuła wrote: >>>
Re: [pdt-dev] preliminary Eclipse PHP package
Hi, All my PDT 3.3.0 pending patches are pushed to master. -- Dawid Pakuła +48 795 996 064 From: Jacek Pospychała jacek.pospych...@gmail.com Reply: PDT Developers pdt-dev@eclipse.org Date: 12 maja 2014 at 18:13:40 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] preliminary Eclipse PHP package it should be up-to-date now. On Mon, May 12, 2014 at 4:09 PM, Dawid Pakuła wrote: > Hi, > > I pushed my one of the three pending patches, but 3.3 nightly site does not > update after build. > > -- > Dawid Pakuła > +48 795 996 064 > > From: Jacek Pospychała jacek.pospych...@gmail.com > Reply: PDT Developers pdt-dev@eclipse.org > Date: 12 maja 2014 at 07:44:36 > > To: PDT Developers pdt-dev@eclipse.org > Subject: Re: [pdt-dev] preliminary Eclipse PHP package > > hi, > as mentioned earlier, I added PDT release repository[1] and seeded it > with latest nightly build (and signed it). > If you still have any updates for Luna, please push them to nightly > and let me know. > > cheers > > Jacek > > > > [1] - http://download.eclipse.org/tools/pdt/updates/3.3 > > On Mon, Apr 28, 2014 at 6:44 PM, Jacek Pospychała > wrote: >> I'll sign them. >> >> On Mon, Apr 28, 2014 at 5:22 PM, Dawid Pakuła wrote: >>> Hi, >>> >>> Jacek: thank you for explanation. One problem is here, snapshots are not >>> signed. >>> >>> Kaloyan: live is brutal ;) Maybe, we move PDT Extension Discovery idea >>> into >>> bugzilla? >>> >>> [1] - >>> >>> http://build.eclipse.org/simrel/luna/reporeports/reports/verifydiroutput/unsigned.txt >>> >>> -- >>> Dawid Pakuła >>> +48 795 996 064 >>> >>> w3des.net >>> ul. Grabiszyńska 108/10 >>> 53-437 Wrocław >>> NIP: 894-293-95-95 >>> REGON: 340769757 >>> >>> From: Kaloyan Raev kaloya...@zend.com >>> Reply: PDT Developers pdt-dev@eclipse.org >>> Date: 28 kwietnia 2014 at 13:12:28 >>> >>> To: PDT Developers pdt-dev@eclipse.org >>> Subject: Re: [pdt-dev] preliminary Eclipse PHP package >>> >>> Initially I planned to implement the PDT Extension Discovery wizard for >>> Luna, but then my schedule became pretty tight. Most probably I will be >>> able >>> to work on this for SR1. >>> >>> The MPC public API is indeed a helpful improvement. >>> >>> >>> On Mon, Apr 28, 2014 at 1:30 PM, Jacek Pospychała >>> wrote: >>>> >>>> In the past we did code freeze and then rebuild per-request only. >>>> That is we would add a new p2 repository for 3.3 >>>> (.../updates/3.3-release), put there latest nightly build (from May >>>> 9th) and also update simrel repository with release repository url. >>>> Then we'd keep running nightly builds and copy nightly to release when >>>> requested. >>>> Finally we'd end up with one of nighly builds becoming a 3.3 release. >>>> Makes sense? >>>> >>>> On Mon, Apr 28, 2014 at 10:41 AM, Dawid Pakuła wrote: >>>> > Hi, >>>> > >>>> > I want refresh this thread, because latest luna milestone will be at 9 >>>> > may. >>>> > Next builds in theory should be RC. >>>> > Any plan for this? >>>> > >>>> > Besides MPC have now public api [1] >>>> > >>>> > [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=432803 >>>> > >>>> > -- >>>> > Dawid Pakuła >>>> > +48 795 996 064 >>>> > >>>> > >>>> > From: Kaloyan Raev kaloya...@zend.com >>>> > Reply: PDT Developers pdt-dev@eclipse.org >>>> > Date: 18 grudnia 2013 at 22:30:32 >>>> > >>>> > To: PDT Developers pdt-dev@eclipse.org >>>> > Subject: Re: [pdt-dev] preliminary Eclipse PHP package >>>> > >>>> > Hi Dawid, >>>> > >>>> >> Here https://wiki.eclipse.org/PDT/Extensions is draft version of >>>> >> plugin >>>> >> list (only some plugins from pdt-extensions.org). >>>> >> Any suggestions? >>>> >> Is the chosen document format ok? >>>> > >>>> > Thanks for starting this wiki. The format is good for start, we can >>>> > adjust >>>> > it later as needed. >>>> > >>>> > I added just a few of the features o
Re: [pdt-dev] refresh our website
Hi, I like it! Articles on wiki, website as simple splash screen :D Currently it’s a problem on small screen : no menu button. -- Dawid Pakuła +48 795 996 064 From: Mike Milinkovich mike.milinkov...@eclipse.org Reply: mike.milinkov...@eclipse.org mike.milinkov...@eclipse.org, PDT Developers pdt-dev@eclipse.org Date: 18 maja 2014 at 21:46:26 To: pdt-dev@eclipse.org pdt-dev@eclipse.org Subject: Re: [pdt-dev] refresh our website On 18/05/2014 2:17 PM, Jacek Pospychała wrote: we're getting close to Luna release, it (re)introduces new PHP package and I thought It'd be nice to bring a breath of fresh air to PDT website. Jacek, Are you aware of the site-wide refresh that's going live on June 11th? You should definitely make sure that anything new that you launch plays well with that. Please pay special attention to the content in Christopher Guindon's announcement and the report is refers to http://eclip.se/1H New look for eclipse.org coming soon Last week we announced the upcoming release of a new skin for www.eclipse.org. Please test your project pages! More info in Christopher's announcement: http://eclip.se/1H and Ian's blog post: http://ianskerrett.wordpress.com/2014/05/15/new-eclipse-web-site-going-live-june-11/ -- Mike Milinkovich mike.milinkov...@eclipse.org +1.613.220.3223 (mobile) ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev part5.07060406.05070409@eclipse.org Description: Binary data ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] New and Noteworthy anyone?
Hi, From my side: 1. PHP 5.5 support (screenshots with syntax ?) 2. Improve PHP editor performance and responsiveness, editing and syntax highlighters 3. CA improvements (I can prepare full list). 4. Suport for default php.ini configuration in PHP debugger 5. And if you move current nightly to release, it also contain constant and deprecation icon support (bug #255164) How I can deliver screenshots? -- Dawid Pakuła +48 795 996 064 From: Jacek Pospychała jacek.pospych...@gmail.com Reply: PDT Developers pdt-dev@eclipse.org Date: 23 maja 2014 at 20:11:23 To: PDT Developers pdt-dev@eclipse.org Subject: [pdt-dev] New and Noteworthy anyone? hi there! as we're approaching luna release quickly, I'd like to ask everyone involved to submit anything that you'd like to be included in PDT 3.3 New and Noteworthy/Release Notes. This typically includes short descriptions of new features that you specially care about, beautiful screenshots, acknowledgements, etc. thank you! Jacek ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
[pdt-dev] 3.3.0 branch
Hi again As usual I have a problem, sorry :P Can we create branch with current stable (3.3.0), and continue work on 3.3.1 without waiting for official eclipse 4.4.0 release (example name: R3_3_stable, or just last_stable)? I want continue my work on 3.3.1 without waiting 25 days for merge. After release and tag this branch can be safely removed. -- Dawid Pakuła +48 795 996 064___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] H2Cache questions
Hi, I made some Java and SQL optimization: * Indexes * Replace subquery by inner joins * Remove 1=1 from where ;) * Tweaks on H2ConnectionFactory Now on large project in my test environment, h2cache is not required. For me, everything is faster, less memory usage. Here is my experiment: https://github.com/zulus/dltk.core/commit/5be4dc62ffed6c19a431b91915c1b9010c7363bb How I’m testing: 2 large Symfony 2 projects in workspace Enable all highlighters Open 2k file with many nested call Format your file , next run CA Check your profiler ;) Advantages: faster eclipse startup ! Open PHP type always working (without “wait for indexer”) Before I send a patch to bugzilla, I have to perform some code cleanup. I also see two other points for optimization in h2 indexer. -- Dawid Pakuła +48 795 996 064 From: Kaloyan Raev kaloya...@zend.com Reply: PDT Developers pdt-dev@eclipse.org Date: 23 października 2013 at 09:30:15 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] H2Cache questions The test I ran yesterday for only for importing huge existing project in the workspace. There is a search operation for each file before it is indexed (to avoid indexing the same file twice). In this case the h2 cache is indeed an overhead because most of the time the searched file isn't available neither in the h2 cache, nor in the h2 db. Today, I ran an additional test - I searched for a method reference in this same huge project. Well, without the cache this operation is 3 times slower. My system is with SSD. I guess that on HDD it will be even more slower. So, it's seems that the h2 cache really optimizes search operations. Kaloyan On Tue, Oct 22, 2013 at 6:35 PM, Alexey Panchenko wrote: Hi Kaloyan, How often does your performance test execute search operations? what operations are executed at all in the test? I afraid this indexer at the moment is used only by PDT, so I don't have any performance data. Regards, Alex On Tue, Oct 22, 2013 at 8:59 PM, Kaloyan Raev wrote: Hi again, I did a quick experiment with removing H2Cache. My performance tests show slight improvement without this cache. Alex, I'll be curious to hear if it's the same in your adopter's product. Here is a commit to cherry pick: https://github.com/kaloyan-raev/dltk.core/commit/e8bfa12aa5408341d230c57530474db281ef132c Greetings, Kaloyan On Mon, Oct 21, 2013 at 10:10 AM, Kaloyan Raev wrote: Hi Alex, The same thoughts crossed my mind when I worked on improving the performance in Zend Studio a couple of months ago. H2Cache is a set of maps with strong references, which makes it really look more like an in-memory copy of the h2 db, rather than a cache. Over time, I suspect, this may cause memory consumption problems. I suppose that the H2Cache was introduced in the past, because of some inefficiencies in the h2 db schema - remember eclip.se/415137. But now, when the necessary index is added to the schema, the benefits of H2Cache are not really visible. One of the idea in my todo list for performance optimizations is indeed to try removing the H2Cache and measure the impact. Unfortunately, I was distracted from the performance topic with other things, but I hope I'll be back on it very soon. Greetings, Kaloyan On Sat, Oct 19, 2013 at 10:13 AM, Alexey Panchenko wrote: Hi PDT-team, I have some questions regarding this class http://git.eclipse.org/c/dltk/org.eclipse.dltk.core.git/log/core/plugins/org.eclipse.dltk.core.index.sql.h2/src/org/eclipse/dltk/internal/core/index/sql/h2/H2Cache.java which was contributed some time ago by Michael and committed by Roy. As I understand the code, it looks like *all* the data from SQL database is loaded into this class and then updates happen to both the in-memory copy and the underlying SQL database. For me, that effectively compromises the SQL database, as the same result could be reached with eventually saving data to file using java serialization. So, I am curious of the following: - how much memory does it use? - is it supposed to be a cache (and contain recently used data) or a full in-memory copy? - how much does it improve the performance? Can the same effect be reached in other ways? Thanks, Alex ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] H2Cache questions
From: Jacek Pospychała jacek.pospych...@gmail.com Reply: PDT Developers pdt-dev@eclipse.org Date: 8 czerwca 2014 at 08:56:09 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] H2Cache questions great work Dawid! so does it mean that this h2cache is useless? Maybe now content-assist just shows less matches? On my github branch h2cache is disabled. Select query time is reduced from 20-250ms into 0-3 in most cases. All PDT tests are passed from now, but I’m still playing. It'd be great to see a performance test that exhibits the difference before and after applying your changes. I’ll try run PDT performance tests later. On Sun, Jun 8, 2014 at 4:59 AM, Dawid Pakuła wrote: > Hi, > > I made some Java and SQL optimization: > * Indexes > * Replace subquery by inner joins > * Remove 1=1 from where ;) > * Tweaks on H2ConnectionFactory > > Now on large project in my test environment, h2cache is not required. For > me, everything is faster, less memory usage. > > Here is my experiment: > https://github.com/zulus/dltk.core/commit/5be4dc62ffed6c19a431b91915c1b9010c7363bb > > How I’m testing: > > 2 large Symfony 2 projects in workspace > Enable all highlighters > Open 2k file with many nested call > Format your file , next run CA > Check your profiler ;) > > Advantages: > > faster eclipse startup ! > Open PHP type always working (without “wait for indexer”) > > Before I send a patch to bugzilla, I have to perform some code cleanup. I > also see two other points for optimization in h2 indexer. > > -- > Dawid Pakuła > +48 795 996 064 > > From: Kaloyan Raev kaloya...@zend.com > Reply: PDT Developers pdt-dev@eclipse.org > Date: 23 października 2013 at 09:30:15 > To: PDT Developers pdt-dev@eclipse.org > Subject: Re: [pdt-dev] H2Cache questions > > The test I ran yesterday for only for importing huge existing project in the > workspace. There is a search operation for each file before it is indexed > (to avoid indexing the same file twice). In this case the h2 cache is indeed > an overhead because most of the time the searched file isn't available > neither in the h2 cache, nor in the h2 db. > > Today, I ran an additional test - I searched for a method reference in this > same huge project. Well, without the cache this operation is 3 times slower. > My system is with SSD. I guess that on HDD it will be even more slower. > > So, it's seems that the h2 cache really optimizes search operations. > > Kaloyan > > > On Tue, Oct 22, 2013 at 6:35 PM, Alexey Panchenko > wrote: >> >> Hi Kaloyan, >> >> How often does your performance test execute search operations? what >> operations are executed at all in the test? >> >> I afraid this indexer at the moment is used only by PDT, so I don't have >> any performance data. >> >> Regards, >> Alex >> >> >> On Tue, Oct 22, 2013 at 8:59 PM, Kaloyan Raev wrote: >>> >>> Hi again, >>> >>> I did a quick experiment with removing H2Cache. My performance tests show >>> slight improvement without this cache. >>> >>> Alex, I'll be curious to hear if it's the same in your adopter's product. >>> Here is a commit to cherry pick: >>> https://github.com/kaloyan-raev/dltk.core/commit/e8bfa12aa5408341d230c57530474db281ef132c >>> >>> Greetings, >>> Kaloyan >>> >>> >>> On Mon, Oct 21, 2013 at 10:10 AM, Kaloyan Raev >>> wrote: >>>> >>>> Hi Alex, >>>> >>>> The same thoughts crossed my mind when I worked on improving the >>>> performance in Zend Studio a couple of months ago. >>>> >>>> H2Cache is a set of maps with strong references, which makes it really >>>> look more like an in-memory copy of the h2 db, rather than a cache. Over >>>> time, I suspect, this may cause memory consumption problems. >>>> >>>> I suppose that the H2Cache was introduced in the past, because of some >>>> inefficiencies in the h2 db schema - remember eclip.se/415137. But now, >>>> when >>>> the necessary index is added to the schema, the benefits of H2Cache are not >>>> really visible. >>>> >>>> One of the idea in my todo list for performance optimizations is indeed >>>> to try removing the H2Cache and measure the impact. Unfortunately, I was >>>> distracted from the performance topic with other things, but I hope I'll be >>>> back on it very soon. >>>> >>>> Greetings, >>>> Kaloyan >>>> >>&
Re: [pdt-dev] H2Cache questions
Hi, again me I modified php performance tests bundle (hardcode ZF location + enable all tests from ProjectSuite): Patched DLTK - my github indexing branch Original DLTK - dltk master branch Patched PDT - pdt master + https://git.eclipse.org/r/#/c/28183/ Test machine: MBP 17” , OSX 10.9.3, 12GB RAM, SSD, Oracle Java 1.7u55 CMD: rm -rf ~/.perf_results/ && mvn clean install -o In general test results are comparable, sometimes faster is first, sometimes second: Patched PDT + Patched DLTK : Test Time: 39.651s Total time: 57.579s Memory: 84M/1110M Patched PDT + Original DLTK: Test Time: 40.281s Total time: 58.762s Memory: 83M/1109M Similar results are for standard PDT tests, but. Even betters look any profiler output: 1. Open eclipse with PDT 2. Import any large project 3. Enable all PDT features (folding, highlighting etc..) 4. Open 1k line file 5. Start working on file 6. Connect any profiler (JVM monitor, Netbeans, YourKit, jProfiler what ever) and look on live results: 7. Less cpu usage, with modified DLTK Please review ;) I think, that later, instead of using current h2cache methodology (load all, then manually iterate hash maps), we can try run second h2 with in-memory mode ( copy disk database into memory database on startup). Sorry for spam and my english :P -- Dawid Pakuła +48 795 996 064 From: Jacek Pospychała jacek.pospych...@gmail.com Reply: PDT Developers pdt-dev@eclipse.org Date: 8 czerwca 2014 at 08:56:09 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] H2Cache questions great work Dawid! so does it mean that this h2cache is useless? Maybe now content-assist just shows less matches? It'd be great to see a performance test that exhibits the difference before and after applying your changes. On Sun, Jun 8, 2014 at 4:59 AM, Dawid Pakuła wrote: > Hi, > > I made some Java and SQL optimization: > * Indexes > * Replace subquery by inner joins > * Remove 1=1 from where ;) > * Tweaks on H2ConnectionFactory > > Now on large project in my test environment, h2cache is not required. For > me, everything is faster, less memory usage. > > Here is my experiment: > https://github.com/zulus/dltk.core/commit/5be4dc62ffed6c19a431b91915c1b9010c7363bb > > How I’m testing: > > 2 large Symfony 2 projects in workspace > Enable all highlighters > Open 2k file with many nested call > Format your file , next run CA > Check your profiler ;) > > Advantages: > > faster eclipse startup ! > Open PHP type always working (without “wait for indexer”) > > Before I send a patch to bugzilla, I have to perform some code cleanup. I > also see two other points for optimization in h2 indexer. > > -- > Dawid Pakuła > +48 795 996 064 > > From: Kaloyan Raev kaloya...@zend.com > Reply: PDT Developers pdt-dev@eclipse.org > Date: 23 października 2013 at 09:30:15 > To: PDT Developers pdt-dev@eclipse.org > Subject: Re: [pdt-dev] H2Cache questions > > The test I ran yesterday for only for importing huge existing project in the > workspace. There is a search operation for each file before it is indexed > (to avoid indexing the same file twice). In this case the h2 cache is indeed > an overhead because most of the time the searched file isn't available > neither in the h2 cache, nor in the h2 db. > > Today, I ran an additional test - I searched for a method reference in this > same huge project. Well, without the cache this operation is 3 times slower. > My system is with SSD. I guess that on HDD it will be even more slower. > > So, it's seems that the h2 cache really optimizes search operations. > > Kaloyan > > > On Tue, Oct 22, 2013 at 6:35 PM, Alexey Panchenko > wrote: >> >> Hi Kaloyan, >> >> How often does your performance test execute search operations? what >> operations are executed at all in the test? >> >> I afraid this indexer at the moment is used only by PDT, so I don't have >> any performance data. >> >> Regards, >> Alex >> >> >> On Tue, Oct 22, 2013 at 8:59 PM, Kaloyan Raev wrote: >>> >>> Hi again, >>> >>> I did a quick experiment with removing H2Cache. My performance tests show >>> slight improvement without this cache. >>> >>> Alex, I'll be curious to hear if it's the same in your adopter's product. >>> Here is a commit to cherry pick: >>> https://github.com/kaloyan-raev/dltk.core/commit/e8bfa12aa5408341d230c57530474db281ef132c >>> >>> Greetings, >>> Kaloyan >>> >>> >>> On Mon, Oct 21, 2013 at 10:10 AM, Kaloyan Raev >>> wrote: >>>> >>>> Hi Alex, >>>> >>>> The same thoughts crossed my mind when I wo
Re: [pdt-dev] H2Cache questions
Yes, search, syntax coloring, CA. On SSD is similar or faster than DLTK with H2 cache. I’m using it on production now ;) On windows with normal HDD, patched version is faster. Update sites for tests (zip): PDT : http://cl.ly/261H2P0w3E29/download/pdtrepository.zip DLTK : http://cl.ly/0x0Q1y3y3o3W/download/dltkrepository.zip -- Dawid Pakuła +48 795 996 064 From: Kaloyan Raev kaloya...@zend.com Reply: PDT Developers pdt-dev@eclipse.org Date: 9 czerwca 2014 at 15:47:54 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] H2Cache questions Dawid, Did you test searching in the project? If you see my message in this same thread from October last year, I noticed significant performance hit on search tasks if I remove the h2 cache. Loading the complete h2 db in memory is an interesting experiment that worth trying. Greetings, Kaloyan On Sun, Jun 8, 2014 at 9:39 PM, Dawid Pakuła wrote: Hi, again me I modified php performance tests bundle (hardcode ZF location + enable all tests from ProjectSuite): Patched DLTK - my github indexing branch Original DLTK - dltk master branch Patched PDT - pdt master + https://git.eclipse.org/r/#/c/28183/ Test machine: MBP 17” , OSX 10.9.3, 12GB RAM, SSD, Oracle Java 1.7u55 CMD: rm -rf ~/.perf_results/ && mvn clean install -o In general test results are comparable, sometimes faster is first, sometimes second: Patched PDT + Patched DLTK : Test Time: 39.651s Total time: 57.579s Memory: 84M/1110M Patched PDT + Original DLTK: Test Time: 40.281s Total time: 58.762s Memory: 83M/1109M Similar results are for standard PDT tests, but. Even betters look any profiler output: 1. Open eclipse with PDT 2. Import any large project 3. Enable all PDT features (folding, highlighting etc..) 4. Open 1k line file 5. Start working on file 6. Connect any profiler (JVM monitor, Netbeans, YourKit, jProfiler what ever) and look on live results: 7. Less cpu usage, with modified DLTK Please review ;) I think, that later, instead of using current h2cache methodology (load all, then manually iterate hash maps), we can try run second h2 with in-memory mode ( copy disk database into memory database on startup). Sorry for spam and my english :P -- Dawid Pakuła +48 795 996 064 From: Jacek Pospychała jacek.pospych...@gmail.com Reply: PDT Developers pdt-dev@eclipse.org Date: 8 czerwca 2014 at 08:56:09 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] H2Cache questions great work Dawid! so does it mean that this h2cache is useless? Maybe now content-assist just shows less matches? It'd be great to see a performance test that exhibits the difference before and after applying your changes. On Sun, Jun 8, 2014 at 4:59 AM, Dawid Pakuła wrote: > Hi, > > I made some Java and SQL optimization: > * Indexes > * Replace subquery by inner joins > * Remove 1=1 from where ;) > * Tweaks on H2ConnectionFactory > > Now on large project in my test environment, h2cache is not required. For > me, everything is faster, less memory usage. > > Here is my experiment: > https://github.com/zulus/dltk.core/commit/5be4dc62ffed6c19a431b91915c1b9010c7363bb > > How I’m testing: > > 2 large Symfony 2 projects in workspace > Enable all highlighters > Open 2k file with many nested call > Format your file , next run CA > Check your profiler ;) > > Advantages: > > faster eclipse startup ! > Open PHP type always working (without “wait for indexer”) > > Before I send a patch to bugzilla, I have to perform some code cleanup. I > also see two other points for optimization in h2 indexer. > > -- > Dawid Pakuła > +48 795 996 064 > > From: Kaloyan Raev kaloya...@zend.com > Reply: PDT Developers pdt-dev@eclipse.org > Date: 23 października 2013 at 09:30:15 > To: PDT Developers pdt-dev@eclipse.org > Subject: Re: [pdt-dev] H2Cache questions > > The test I ran yesterday for only for importing huge existing project in the > workspace. There is a search operation for each file before it is indexed > (to avoid indexing the same file twice). In this case the h2 cache is indeed > an overhead because most of the time the searched file isn't available > neither in the h2 cache, nor in the h2 db. > > Today, I ran an additional test - I searched for a method reference in this > same huge project. Well, without the cache this operation is 3 times slower. > My system is with SSD. I guess that on HDD it will be even more slower. > > So, it's seems that the h2 cache really optimizes search operations. > > Kaloyan > > > On Tue, Oct 22, 2013 at 6:35 PM, Alexey Panchenko > wrote: >> >> Hi Kaloyan, >> >> How often does your performance test execute search operations? what >> operations are executed at all in the test? >> >> I afraid this indexer at the moment is use
[pdt-dev] Dark theme contribution
Hi, in luna RC3 our dark theme syntax colors stopped working, so I sent patch to HEAD. Jacek, can you release it for Luna RC4? I checked this on OSX 10.9.3, Ubuntu 14.04 (VM) and Windows XP (VM) Thanks -- Dawid Pakuła +48 795 996 064___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] Dark theme contribution
Thanks! -- Dawid Pakuła +48 795 996 064 From: Jacek Pospychała jacek.pospych...@gmail.com Reply: PDT Developers pdt-dev@eclipse.org Date: 11 czerwca 2014 at 19:41:55 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] Dark theme contribution sure, done! On Wed, Jun 11, 2014 at 1:16 AM, Dawid Pakuła wrote: > Hi, > > in luna RC3 our dark theme syntax colors stopped working, so I sent patch to > HEAD. > > Jacek, can you release it for Luna RC4? I checked this on OSX 10.9.3, Ubuntu > 14.04 (VM) and Windows XP (VM) > > Thanks > -- > Dawid Pakuła > +48 795 996 064 > > ___ > pdt-dev mailing list > pdt-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/pdt-dev > ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] Fwd: [cross-project-issues-dev] DLTK in Luna RC4
Hi, I’m using PDT EPP (from m7) + DLTK 5.1 on production. DLTK 5.1 have a regression in H2 search: MatchRule.CAMEL_CASE and MatchRule.PREFIX not work with PHP FQN (with “\”) if h2cache is not loaded or if you search for reference. Workaround: manually escape “\”, It not will affect PDT because H2Cache is enabled by default, and PDT never search for references, so everything from PDT works correctly. -- Dawid Pakuła +48 795 996 064 From: Jacek Pospychała jacek.pospych...@gmail.com Reply: PDT Developers pdt-dev@eclipse.org Date: 12 czerwca 2014 at 21:42:54 To: PDT Developers pdt-dev@eclipse.org Subject: [pdt-dev] Fwd: [cross-project-issues-dev] DLTK in Luna RC4 hi Team! any thoughts on dltk 5.1? anybody of you have been testing/building against it before RC4? btw you can test Eclipse PHP package Luna RC4 by downloading from https://hudson.eclipse.org/packaging/job/luna.epp-tycho-build/150/ Jacek___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
[pdt-dev] 3.3.0 release is coming
Hi, can we remove 3.2.1 and 3.2.2 from PMI/bugzilla? [1] [2] I can't find any policy for this task in eclipse wiki. Probably we also should tag current master. [1] - https://projects.eclipse.org/projects/tools.pdt/releases/3.2.1 [2] - https://projects.eclipse.org/projects/tools.pdt/releases/3.2.2 -- Dawid Pakuła +48 795 996 064___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] 3.3.0 release is coming
Hi, tag R3_3_0 pushed to our repo. -- Dawid Pakuła +48 795 996 064 From: Jacek Pospychała jacek.pospych...@gmail.com Reply: PDT Developers pdt-dev@eclipse.org Date: 14 czerwca 2014 at 16:22:27 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] 3.3.0 release is coming hej Dawid! good point! I removed 3.2.1 and 3.2.2 from PMI. I can't remove them from bugzilla because only webmaster can remove/edit there - so I'd leave them as is. Re adding a tag, you can do it or I'll do it later. thanks! Jacek On Sat, Jun 14, 2014 at 3:24 PM, Dawid Pakuła wrote: > Hi, > > can we remove 3.2.1 and 3.2.2 from PMI/bugzilla? [1] [2] > I can't find any policy for this task in eclipse wiki. > > Probably we also should tag current master. > > [1] - https://projects.eclipse.org/projects/tools.pdt/releases/3.2.1 > [2] - https://projects.eclipse.org/projects/tools.pdt/releases/3.2.2 > > -- > Dawid Pakuła > +48 795 996 064 > > ___ > pdt-dev mailing list > pdt-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/pdt-dev > ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
[pdt-dev] Continue performance improvements
Hi, after couple months with PDT and DLTK code base I see many performance problems, which cannot be fixed without cooperate with DLTK project. In theory PDT add import into file. But, while resolving references (for example in TI or CA), AST is required to detect aliases. Since 5.6 problem will grow up, because will be possible to import function. -- Dawid Pakuła +48 795 996 064___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] Continue performance improvements
Sorry I didn’t finish this mail. I don’t know why it was sent. Please ignore it. I resend when finish. -- Dawid Pakuła +48 795 996 064 From: Jacek Pospychała jacek.pospych...@gmail.com Reply: PDT Developers pdt-dev@eclipse.org Date: 23 czerwca 2014 at 11:56:52 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] Continue performance improvements how about cooperating with DLTK project? any issues there? On Mon, Jun 23, 2014 at 11:44 AM, Dawid Pakuła wrote: > Hi, > > after couple months with PDT and DLTK code base I see many performance > problems, which cannot be fixed without cooperate with DLTK project. > > In theory PDT add import into file. But, while resolving references (for > example in TI or CA), AST is required to detect aliases. Since 5.6 problem > will grow up, because will be possible to import function. > > > -- > Dawid Pakuła > +48 795 996 064 > > ___ > pdt-dev mailing list > pdt-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/pdt-dev > ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
[pdt-dev] Continue PDT performance improvements
Hi, again sorry for morning confusion. After couple months with PDT and DLTK code base I see many performance problems, which cannot be fixed without cooperate with DLTK team and/or modify API/architecture . TI - Type Inference CA - Code Assist DOMAst - old ast, used by formatter, syntax highlighter and many others ui elements. Not persisted. AST/Compiler AST - second ast, based on DLTK ast. 1. Imports: in theory PDT registering in model all imports. But, while resolving references (for example in TI or CA), AST is required to detect aliases. Since 5.6 problem will grow up, because will be possible to import function and constants. To fix this, we require bug 437856 [1] 2. PHPModelUtils: very useful and complex class, highly used while TI, but not designed to use with TI :P. Examples: a) White TI, IContext subclasses can contain SourceModule, ModuleDeclaration (AST), namespace name etc.. But methods in this class isn’tt using this, so many times they manually asking for source_module, namespace name… by AST or model traversing. b) Sometimes they are using IContext, sometimes IModelAccessCache, sometimes only type hierarchy, sometimes nothing like in traits [2] 3. Bindings: Now available for DOMAst only, and with very generic implementation. If I need IType from MethodInvocation: a) Traverse compiler ast to find IContext and corresponing ASTNode b) Run TI, with all performance problems (again many ask for ModuleDeclaration and traversing over it). c) Cache It for concrete AST node If IMethod/IField is required, collect all fields and methods by PHPModelUtils JDT works different: a) Binding resolver, always contain map DOMAst => CompilerAST (built while AST convert) - I’m still working on converter b) Contexts are not required, so probably we should build and cache context while ast convert c) Bindings are also cached on corresponding AST nodes and reused later (here we need small DLTK modification) We also should allow to get IBinding without DOMAst. Just like in JDT. 4. IModelAccessCache: Nice idea, but if TI traverse over more than one SourceModule, current implementation it’s usable only for superClass hierarchy. Maybe like attributes in IBuildContext 5. PDT extensions, any: They are not able to cache own informations while TI. Would be nice to extend PDT or DLTK for this use case. Maybe like attributes in IBuildContext ? 6. CodeAssistCompanion: Duplicate super hierarchy cache. This class should provide IModelAccessCache, and share it between contexts. 7. Traits: horrible to debug, nightmare to implement ;). Its not cached, not indexed, and not persisted in model. PHPModelUtils many times, have to traverse over AST to detect it, next traverse to collect it, and never cache it. Fortunately they are still not popular, but later they will degrade performance. I asked DLTK team in [1] how it should be implemented. Maybe instead of IImportDeclaration could be IMixinContainer / IMixinDeclaration / IMixinDetail 8. Array dereference: Now stored on each dereferencable node. So it’s not possible to provide one dedicated TI Evaluator and cache it. We should use ArrayAccess for this, like JDT :P. 9. Annotations: Still not standard in PHP, but probably they will be part of PHP6/ng and we should start thinking about it. DLTK haven’t annotation support yet. See IAnnotable in JDT I have also other ideas, but this simple list is most important for now and future. Sorry for my english :P [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=437856 [2] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=430316 -- Dawid Pakuła +48 795 996 064 w3des.net ul. Grabiszyńska 108/10 53-437 Wrocław NIP: 894-293-95-95 REGON: 340769757___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] Continue PDT performance improvements
Hi Kaloyan, 1 - One of most important to reduce AST lookup, should be easy to implement and I hope acceptable by DLTK team. They are now completely out of resources, so probably someone from us should help them. 7 - I’m still thinking about best, light and portable model for traits (IMixinDeclaration), each suggestion and later help with implementation are important! I have to check how it was done for other languages - perl6 (EPIC), Scalar IDE 3 - we probably can prepare workaround for this by IEvaluationStatisticsRequestor, small patch to DLTK should also be easy. 2, 4, 6, 8 - changes in architecture will be required, probably with better DLTK integration (like enterNamespace in ISourceElementRequestor). I’ll prepare bugs later (target for pdt 3.4 , 4.0 or future ?). 5 - We also can implement it in PDT only. 9 - is not yet required. Pending php rfc's [1] [2]. Later we can adopt current JDT annotation model into DLTK. [1] - https://wiki.php.net/rfc/annotations [2] - https://wiki.php.net/rfc/annotations-in-docblock -- Dawid Pakuła +48 795 996 064 From: Kaloyan Raev kaloya...@zend.com Reply: PDT Developers pdt-dev@eclipse.org Date: 23 czerwca 2014 at 16:03:36 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] Continue PDT performance improvements Hi Dawid, Thanks for this summary and your overall dedication on improving PDT in the last months. What kind of help are your looking for to continue? Any doubt that the required changes in DLTK will be accepted? :) Greetings, Kaloyan On Mon, Jun 23, 2014 at 4:14 PM, Dawid Pakuła wrote: Hi, again sorry for morning confusion. After couple months with PDT and DLTK code base I see many performance problems, which cannot be fixed without cooperate with DLTK team and/or modify API/architecture . TI - Type Inference CA - Code Assist DOMAst - old ast, used by formatter, syntax highlighter and many others ui elements. Not persisted. AST/Compiler AST - second ast, based on DLTK ast. 1. Imports: in theory PDT registering in model all imports. But, while resolving references (for example in TI or CA), AST is required to detect aliases. Since 5.6 problem will grow up, because will be possible to import function and constants. To fix this, we require bug 437856 [1] 2. PHPModelUtils: very useful and complex class, highly used while TI, but not designed to use with TI :P. Examples: a) White TI, IContext subclasses can contain SourceModule, ModuleDeclaration (AST), namespace name etc.. But methods in this class isn’tt using this, so many times they manually asking for source_module, namespace name… by AST or model traversing. b) Sometimes they are using IContext, sometimes IModelAccessCache, sometimes only type hierarchy, sometimes nothing like in traits [2] 3. Bindings: Now available for DOMAst only, and with very generic implementation. If I need IType from MethodInvocation: a) Traverse compiler ast to find IContext and corresponing ASTNode b) Run TI, with all performance problems (again many ask for ModuleDeclaration and traversing over it). c) Cache It for concrete AST node If IMethod/IField is required, collect all fields and methods by PHPModelUtils JDT works different: a) Binding resolver, always contain map DOMAst => CompilerAST (built while AST convert) - I’m still working on converter b) Contexts are not required, so probably we should build and cache context while ast convert c) Bindings are also cached on corresponding AST nodes and reused later (here we need small DLTK modification) We also should allow to get IBinding without DOMAst. Just like in JDT. 4. IModelAccessCache: Nice idea, but if TI traverse over more than one SourceModule, current implementation it’s usable only for superClass hierarchy. Maybe like attributes in IBuildContext 5. PDT extensions, any: They are not able to cache own informations while TI. Would be nice to extend PDT or DLTK for this use case. Maybe like attributes in IBuildContext ? 6. CodeAssistCompanion: Duplicate super hierarchy cache. This class should provide IModelAccessCache, and share it between contexts. 7. Traits: horrible to debug, nightmare to implement ;). Its not cached, not indexed, and not persisted in model. PHPModelUtils many times, have to traverse over AST to detect it, next traverse to collect it, and never cache it. Fortunately they are still not popular, but later they will degrade performance. I asked DLTK team in [1] how it should be implemented. Maybe instead of IImportDeclaration could be IMixinContainer / IMixinDeclaration / IMixinDetail 8. Array dereference: Now stored on each dereferencable node. So it’s not possible to provide one dedicated TI Evaluator and cache it. We should use ArrayAccess for this, like JDT :P. 9. Annotations: Still not standard in PHP, but probably they will be part of PHP6/ng and we should start thinking about it. DLTK haven’t annotation support yet. See IAnnotable in JDT I have also oth
Re: [pdt-dev] Problem with code pasting
Hi (cześć) and welcome, now we have little mess in formatter: org.eclipse.php.core: 1. Indentation strategies 2. Old PDT formatter : it’s based on indentation strategies 3. Universal bridge for formatter settings (indentation size, tabs vs spaces, etc…) org.eclipse.plugin.formatter.core: 1. New PDT formatter from Zend : it’s based on DOM AST (like JDT formatter), org.eclipse.php.ui: 1. autoedit strategies, based on indentation strategies 2. smart paste strategy Another tip, PHPAutoIndentStrategoy#smartPaste it's probably your problem. This method: 1. Create temporary document 2. Doing paste and indentation one by line (append, parse, calculate indent, replace line) 3. Detect intentation on target document 4. Cut from temporary document and paste into target I suggest checking how it was done in jdt/jsdt ;) Good luck! -- Dawid Pakuła +48 795 996 064 From: Jacek Pospychała jacek.pospych...@gmail.com Reply: PDT Developers pdt-dev@eclipse.org Date: 26 czerwca 2014 at 22:08:22 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] Problem with code pasting hi Michal, nice to meet you and welcome to the list! I'm affraid I can't give any useful tips beyond what you probably already found. Anyway, if you're really totally lost, you could have a look at recent pull requests (merged and pending), some of which were related to formatter. Can't wait to see your pull requests to PDT! cheers Jacek On Thu, Jun 26, 2014 at 4:01 PM, Michał Niewrzał wrote: > Hi All, > > I became a member of Zend Studio team so I probably will be a permanent > guest here:) Actually I'm working with problem that I found by accident but > after quick research I discovered that exists for some time. Pasting longer > php code (e.g. 1000 lines) takes a lot of time. > > I created a bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=438240 and I'm > currently looking for solution but I'm new in the area of code formatting so > it won't be easy task for me:) If someone can give me a tips or hint I will > be grateful. > > Thanks, > Michal > > ___ > pdt-dev mailing list > pdt-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/pdt-dev > ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
[pdt-dev] Namespace types
Hi, New problem, sorry, we really need a developer docs :P Someone remember why namespaces are implemented as ITypes 5 years ago by Michael Spector ? Problems with old DLTK api? I cannot find any informations in mailing list history. In theory this should be implemented by IElementRequestor.acceptPackage instead of IElementRequestor.acceptType. Advantages: 1. Performance: we don’t have to filter namespaces while search (for ex. group by namespaces in PHPExplorer, any findType call) 2. No more ugly green icon :P 3. Cleaner PHP outliner, more JDT like Disadvantages: 1. Migration ;) 2. Problem if file have more than one namespace, should be easy to fix by explorer and outliner content providers -- Dawid Pakuła +48 795 996 064 ___ 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
Re: [pdt-dev] 404 Errors on Documentation Links
I sent commit with lowercased links. Jacek, how I can update website? -- Dawid Pakuła +48 795 996 064 From: Jacek Pospychała jacek.pospych...@gmail.com Reply: PDT Developers pdt-dev@eclipse.org Date: 10 lipca 2014 at 20:50:01 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] 404 Errors on Documentation Links hi Steven, I'm sorry, but somehow toc.htm has upper-case links whereas actual filenames are lower-case. should be fine in few minutes... Jacek On Thu, Jul 10, 2014 at 5:34 PM, Steven Hollingsworth wrote: > Getting 404 not found on all the links from this page: > http://www.eclipse.org/pdt/help/html/toc.htm > > example: > http://www.eclipse.org/pdt/help/html/PHP.htm > > Anybody know where I can find the live links? > > TIA > > ./Steven > > ___ > 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
Re: [pdt-dev] 404 Errors on Documentation Links
Thanks! -- Dawid Pakuła +48 795 996 064 From: Jacek Pospychała jacek.pospych...@gmail.com Reply: PDT Developers pdt-dev@eclipse.org Date: 10 lipca 2014 at 21:12:54 To: PDT Developers pdt-dev@eclipse.org Subject: Re: [pdt-dev] 404 Errors on Documentation Links thanks Dawid! Website get's automatically updated within few minutes after each push. I've seen your commit and pushed some more changes with a help of little script that fixed the links in toc.htm. On Thu, Jul 10, 2014 at 9:04 PM, Dawid Pakuła wrote: > I sent commit with lowercased links. > > Jacek, how I can update website? > -- > Dawid Pakuła > +48 795 996 064 > > From: Jacek Pospychała jacek.pospych...@gmail.com > Reply: PDT Developers pdt-dev@eclipse.org > Date: 10 lipca 2014 at 20:50:01 > To: PDT Developers pdt-dev@eclipse.org > Subject: Re: [pdt-dev] 404 Errors on Documentation Links > > hi Steven, > I'm sorry, but somehow toc.htm has upper-case links whereas actual > filenames are lower-case. should be fine in few minutes... > > Jacek > > On Thu, Jul 10, 2014 at 5:34 PM, Steven Hollingsworth > wrote: >> Getting 404 not found on all the links from this page: >> http://www.eclipse.org/pdt/help/html/toc.htm >> >> example: >> http://www.eclipse.org/pdt/help/html/PHP.htm >> >> Anybody know where I can find the live links? >> >> TIA >> >> ./Steven >> >> ___ >> 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___ 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
Re: [pdt-dev] Styling for deprecated member
Hi, it was disabled due TI performance problems (example [1]). In PDT 3.3.0, most of them was fixed [2]. I created a bug to enable more highlighters [3]. [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=316637 [2] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=430049 [3] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=436044 -- Dawid Pakuła +48 795 996 064 From: Michał Niewrzał Reply: PDT Developers > Date: 11 sierpnia 2014 at 12:00:57 To: pdt-dev@eclipse.org > Subject: [pdt-dev] Styling for deprecated member Hi All, I want to ask about deprecated members styling. Lately in Studio we realize that this preference is off by default. Anybody know what is the reason for that? Is it disabled from the beginning or was it disabled because some coloring problems? For instance in JDT this option is enabled by default and in my opinion it is correct approach. Thanks in advance, Michal ___ 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] Luna SR1
Hi pdt-team Do we plan to release PDT 3.3.1 (Luna SR1 [1]) ? I’m asking because we haven’t PMI record now. [1] - https://wiki.eclipse.org/Luna/Simultaneous_Release_Plan -- Dawid Pakuła +48 795 996 064___ 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
Re: [pdt-dev] time for new project lead
Hi all, Kaloyan Raev clarified me all my concerns (thank a lot!), so if everybody agree, I can be a volunteer. -- Dawid Pakula On 11 September 2014 at 20:51:17, Jacek Pospychała (jacek.pospych...@gmail.com) wrote: Dear PDT Team, as you know, recently I've been only marginally involved in PDT developments. Since the project is quite healthy with active two committers (Dawid and Kaloyan) and some contributors (i.e. Michał, but others too), I feel no longer in "lead" position. Thus I'm looking for a volunteer (probably those most involved) willing to take over the little bureaucratic burden and most of all, take PDT in the new exciting directions. Any candidates? Jacek ___ 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] Upload on save feature
Hi team, the last thing that forces me to use netbeans sometimes is an upload-on-change/upload-on-demand feature. I wan’t add this feature to PDT but I have few questions: 1. It should be part of PDT, PDT-Incubator (reactivation is required), WTP common or new eclipse (sub)project? 2. If part of PDT, should be under “server” configuration or new tab (probably deploy) is needed? What do you think? -- Dawid Pakuła +48 795 996 064 ___ 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
Re: [pdt-dev] Upload on save feature
Hi, Netbeans have a feature called "remote project" I prefer naming it “deploy" It’s possible to deploy files in background via (ftp/sftp/fps): 1. Incrementaly (after each save operation or any other modification on file like rename, delete...) 2. On demand (RPM on dir and select upload) It’s also possible to download concrete dir (RPM on dir in project explorer -> download). Their implementation has several limitation like only one remote server per project, but in general this functionality is simple. -- Dawid Pakuła +48 795 996 064 From: Kaloyan Raev Reply: PDT Developers > Date: 17 września 2014 at 20:48:31 To: PDT Developers > Subject: Re: [pdt-dev] Upload on save feature Dawid, How do you imagine the exact workflow from user perspective? Clarifying this will help us identify the best place to implement this feature. Thanks, Kaloyan On Tue, Sep 16, 2014 at 11:45 PM, Dawid Pakuła wrote: Hi team, the last thing that forces me to use netbeans sometimes is an upload-on-change/upload-on-demand feature. I wan’t add this feature to PDT but I have few questions: 1. It should be part of PDT, PDT-Incubator (reactivation is required), WTP common or new eclipse (sub)project? 2. If part of PDT, should be under “server” configuration or new tab (probably deploy) is needed? What do you think? -- Dawid Pakuła +48 795 996 064 ___ 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
Re: [pdt-dev] PHP 5.6 support
Hi, most elements you will find in one commit : [1]. bug for php 5.6 is open [2] Steps: 1. Extend PHPVersion and where is used (projects wizard, project preferences and more…) 2. Generate code stubs and register it. Same for keywords 3. Copy/paste php 5.5 flexer and extend it. Two or three new tokens as I see(pow operator, variadic…) + tests 4. Create new AST nodes for DOM and Compiler tree 5. Copy/paste and extend parser. Current pdt parser are very close to original php parser, so their source code may be helpful + tests 6. Extend occurrences finder + tests 7. Extend formatter / syntax coloring + tests 8. Extend ASTMatcher + tests 9. Modify inference engine + tests 10. Modify CA + tests php 5.5 was in general easy to implement. With php 5.6 will be harder due new use function and use constant DLTK doesn’t allow to add additional informations to imports. Patch: [3] I hope it’s helpful. [1] - http://git.eclipse.org/c/pdt/org.eclipse.pdt.git/commit/?id=9034500b3b47f34efa42be4d8b18871d78493995 [2] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=435922 [3] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=437856 -- Dawid Pakuła +48 795 996 064 w3des.net ul. Grabiszyńska 108/10 53-437 Wrocław NIP: 894-293-95-95 REGON: 340769757 From: Michał Niewrzał Reply: PDT Developers > Date: 17 września 2014 at 23:53:02 To: PDT Developers > Subject: [pdt-dev] PHP 5.6 support Hi All, We (Zend Studio team) begin to think about support for PHP 5.6. Of course we need to start from PDT. It looks that I will be person most involved from our team and I want to start this conversation with at least general idea what need to be done. I heard that previous version 5.5 was implemented mostly by Dawid:) Dawid, can you write short (I hope) list with PDT parts that needs to be adjusted/extended? Thanks, Michal ___ 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
Re: [pdt-dev] Upload on save feature
@Kaloyan, I’m still thinking about this. (each time when I have to open NB ;) ). This feature could be based on facet framework + additional menu item in projects settings. Or as completely new project nature, with own project builder and settings. Or maybe as part of project server settings configuration. @Gadi, I hope no. It should be additional plugin, so will be always possible to disable it. -- Dawid Pakuła +48 795 996 064 From: Kaloyan Raev Reply: PDT Developers > Date: 18 września 2014 at 09:15:01 To: PDT Developers > Subject: Re: [pdt-dev] Upload on save feature I see. However, my question was how you imagine this implemented in PDT. Where do you see configurations and actions plugged into the existing UI. Kaloyan On Wed, Sep 17, 2014 at 11:17 PM, Dawid Pakuła wrote: Hi, Netbeans have a feature called "remote project" I prefer naming it “deploy" It’s possible to deploy files in background via (ftp/sftp/fps): 1. Incrementaly (after each save operation or any other modification on file like rename, delete...) 2. On demand (RPM on dir and select upload) It’s also possible to download concrete dir (RPM on dir in project explorer -> download). Their implementation has several limitation like only one remote server per project, but in general this functionality is simple. -- Dawid Pakuła +48 795 996 064 From: Kaloyan Raev Reply: PDT Developers > Date: 17 września 2014 at 20:48:31 To: PDT Developers > Subject: Re: [pdt-dev] Upload on save feature Dawid, How do you imagine the exact workflow from user perspective? Clarifying this will help us identify the best place to implement this feature. Thanks, Kaloyan On Tue, Sep 16, 2014 at 11:45 PM, Dawid Pakuła wrote: Hi team, the last thing that forces me to use netbeans sometimes is an upload-on-change/upload-on-demand feature. I wan’t add this feature to PDT but I have few questions: 1. It should be part of PDT, PDT-Incubator (reactivation is required), WTP common or new eclipse (sub)project? 2. If part of PDT, should be under “server” configuration or new tab (probably deploy) is needed? What do you think? -- Dawid Pakuła +48 795 996 064 ___ 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___ 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
Re: [pdt-dev] provide changelog or release notes to users
Hi, You probably have pdt-nightly on your software repositories list. We haven’t tools (and/or human resources) to provide changelog between snapshots. Now easiest way to see what was done (or is in plan), is a PMI [1] or subscription on bugzilla [1] - https://projects.eclipse.org/projects/tools.pdt/releases/3.3.1/bugs -- Dawid Pakuła +48 795 996 064 From: Thomas Koch Reply: PDT Developers > Date: 18 września 2014 at 12:03:56 To: pdt-dev@eclipse.org > Subject: [pdt-dev] provide changelog or release notes to users Hi, Eclipse proposes me every few days to install a pdt update which I do. It would however be nice, if I could see what changes are included in the update so that I could try new features or now that some bugs are fixed. Is there any possibility to show such a thing to the user in the eclipse installer? Best regards, Thomas Koch ___ 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
Re: [pdt-dev] PHP 5.6 support
Hi, Hi, I have some additional questions: 2. Generate code stubs and register it. Same for keywords Which part of code you are talking about exactly? See IPHPKeywordsInitializer and subclasses. Code stubs org.eclipse.php.core/Resources/language/php_ver (see README.txt howto generate it). Remember to update DefaultLanguageModelProvider after generation. 5. Copy/paste and extend parser. Current pdt parser are very close to original php parser, so their source code may be helpful + tests Can you point me place where I can find this original PHP parser? https://github.com/php/php-src/blob/PHP-5.6.1/Zend/zend_language_parser.y And one more question about generating language model. File "generate.php" is generating code based on loaded extensions. Is there a list of modules that need to be enabled during generation? This was my mistake while initial php 5.5 implementation. File names in languages/php5.5 are your list. Module_name.php ;) Thanks, Michal On Thu, Sep 18, 2014 at 12:12 AM, Dawid Pakuła wrote: Hi, most elements you will find in one commit : [1]. bug for php 5.6 is open [2] Steps: 1. Extend PHPVersion and where is used (projects wizard, project preferences and more…) 2. Generate code stubs and register it. Same for keywords 3. Copy/paste php 5.5 flexer and extend it. Two or three new tokens as I see(pow operator, variadic…) + tests 4. Create new AST nodes for DOM and Compiler tree 5. Copy/paste and extend parser. Current pdt parser are very close to original php parser, so their source code may be helpful + tests 6. Extend occurrences finder + tests 7. Extend formatter / syntax coloring + tests 8. Extend ASTMatcher + tests 9. Modify inference engine + tests 10. Modify CA + tests php 5.5 was in general easy to implement. With php 5.6 will be harder due new use function and use constant DLTK doesn’t allow to add additional informations to imports. Patch: [3] I hope it’s helpful. [1] - http://git.eclipse.org/c/pdt/org.eclipse.pdt.git/commit/?id=9034500b3b47f34efa42be4d8b18871d78493995 [2] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=435922 [3] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=437856 -- Dawid Pakuła +48 795 996 064 w3des.net ul. Grabiszyńska 108/10 53-437 Wrocław NIP: 894-293-95-95 REGON: 340769757 From: Michał Niewrzał Reply: PDT Developers > Date: 17 września 2014 at 23:53:02 To: PDT Developers > Subject: [pdt-dev] PHP 5.6 support Hi All, We (Zend Studio team) begin to think about support for PHP 5.6. Of course we need to start from PDT. It looks that I will be person most involved from our team and I want to start this conversation with at least general idea what need to be done. I heard that previous version 5.5 was implemented mostly by Dawid:) Dawid, can you write short (I hope) list with PDT parts that needs to be adjusted/extended? Thanks, Michal ___ 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
[pdt-dev] 3.3.1, 3.3.2 and mars release
Hi team, small 3.3.1 summary plus questions for upcoming release(s) 3.3.1: We are in quite week, code tagged as R3_3_1 Final p2 repository is waiting at [1], I’ll update pmi and website on friday We closed 76 bugs in this cycle! [2] 3.3.2: Do we plan it? If yes, maybe we should split streams? Mars release: Version number: probably 3.4 Are we waiting for DLTK mars announcement? What features or bugs you plan for this release? [1] - http://download.eclipse.org/tools/pdt/updates/3.3.1/ [2] - https://projects.eclipse.org/projects/tools.pdt/releases/3.3.1/bugs -- Dawid Pakuła +48 795 996 064 ___ 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
Re: [pdt-dev] 3.3.1, 3.3.2 and mars release
Hi, I’m 100% agree with often releases. But we still have to announce our participation before M4 with version declared in PMI (number, type, project plan…) [1]. Each version update have to be also announced. I'm going to ask PMC when (if) I'll be formally accepted as a project lead. So, can we prepare our initial plan for Mars release? From my side I want continue performance and memory consumption improvements, especially #438091 [2], #438087 [3], #438100 [4] + some tweaks for DLTK Besides on my todo / investigate / wish list are also: #369635 [5] - I’ll create another thread for this on our (spam)list soon ;) #443473 [6], #440965 [7], #438097 [8] [1] - https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#State_intent_early_.28M4.29 [2] - http://eclip.se/438091 [3] - http://eclip.se/438087 [4] - http://eclip.se/438100 [5] - http://eclip.se/369635 [6] - http://eclip.se/443473 [7] - http://eclip.se/440965 [8] - http://eclip.se/438097 -- Dawid Pakuła +48 795 996 064 On 23 września 2014 at 17:22:29, Kaloyan Raev (kaloya...@zend.com) wrote: Hi, In general, I believe, we should have three releases per year aligned with the Eclipse Simultaneous release: June - SR0, September - SR1 and February - SR2. Whether each release is "feature" or "maintenance" depends on the changes done in this release. So, if we apply the above, for Luna SR1 we are having the 3.3.1 maintenance release. As Michal started working on PHP 5.6 support and it will be ready by Luna SR2, then we may ship a 3.4 feature release for Luna SR2 and Mars M5. For the official Mars release we can ship either 3.4.1 and 3.5 depending on what's done by then. But it is too early to predict it at the moment. This way we ship faster new features to users and avoid having unnecessary spitting of code streams. This is actually the approach of the EGit project, it's not anything I am inventing right now :-) Thoughts? Kaloyan On Tue, Sep 23, 2014 at 3:48 PM, Dawid Pakuła wrote: Hi team, small 3.3.1 summary plus questions for upcoming release(s) 3.3.1: We are in quite week, code tagged as R3_3_1 Final p2 repository is waiting at [1], I’ll update pmi and website on friday We closed 76 bugs in this cycle! [2] 3.3.2: Do we plan it? If yes, maybe we should split streams? Mars release: Version number: probably 3.4 Are we waiting for DLTK mars announcement? What features or bugs you plan for this release? [1] - http://download.eclipse.org/tools/pdt/updates/3.3.1/ [2] - https://projects.eclipse.org/projects/tools.pdt/releases/3.3.1/bugs -- Dawid Pakuła +48 795 996 064 ___ 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
Re: [pdt-dev] 3.3.1, 3.3.2 and mars release
Hi team, I prepared two release records in PMI: 3.4 [1] - Luna SR1 3.4.1 [2] - Mars release Most of texts are based on Jacek Pospychała work. If you want add something to plan, please do it. ;) If no one raises an objection, I want to announce our Mars participation on Friday. [1] - https://projects.eclipse.org/projects/tools.pdt/releases/3.4 [2] - https://projects.eclipse.org/projects/tools.pdt/releases/3.4.1 -- Dawid Pakuła +48 795 996 064 On 24 września 2014 at 08:22:17, Kaloyan Raev (kaloya...@zend.com) wrote: Hi Dawid, I see there is an ongoing vote for you in Tools PMC mailing list [1], which will finish on Friday. For next release we plan to work on PHP 5.6 support [2]. I know Wojtek plans to contribute a few patches regarding servers and libraries. He will come up with bugs soon. We may work also on some other topics, but it's too early to commit to this at the moment. [1] https://dev.eclipse.org/mhonarc/lists/tools-pmc/msg02743.html [2] http://eclip.se/435922 Greetings, Kaloyan On Wed, Sep 24, 2014 at 12:22 AM, Dawid Pakuła wrote: Hi, I’m 100% agree with often releases. But we still have to announce our participation before M4 with version declared in PMI (number, type, project plan…) [1]. Each version update have to be also announced. I'm going to ask PMC when (if) I'll be formally accepted as a project lead. So, can we prepare our initial plan for Mars release? From my side I want continue performance and memory consumption improvements, especially #438091 [2], #438087 [3], #438100 [4] + some tweaks for DLTK Besides on my todo / investigate / wish list are also: #369635 [5] - I’ll create another thread for this on our (spam)list soon ;) #443473 [6], #440965 [7], #438097 [8] [1] - https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#State_intent_early_.28M4.29 [2] - http://eclip.se/438091 [3] - http://eclip.se/438087 [4] - http://eclip.se/438100 [5] - http://eclip.se/369635 [6] - http://eclip.se/443473 [7] - http://eclip.se/440965 [8] - http://eclip.se/438097 -- Dawid Pakuła +48 795 996 064 On 23 września 2014 at 17:22:29, Kaloyan Raev (kaloya...@zend.com) wrote: Hi, In general, I believe, we should have three releases per year aligned with the Eclipse Simultaneous release: June - SR0, September - SR1 and February - SR2. Whether each release is "feature" or "maintenance" depends on the changes done in this release. So, if we apply the above, for Luna SR1 we are having the 3.3.1 maintenance release. As Michal started working on PHP 5.6 support and it will be ready by Luna SR2, then we may ship a 3.4 feature release for Luna SR2 and Mars M5. For the official Mars release we can ship either 3.4.1 and 3.5 depending on what's done by then. But it is too early to predict it at the moment. This way we ship faster new features to users and avoid having unnecessary spitting of code streams. This is actually the approach of the EGit project, it's not anything I am inventing right now :-) Thoughts? Kaloyan On Tue, Sep 23, 2014 at 3:48 PM, Dawid Pakuła wrote: Hi team, small 3.3.1 summary plus questions for upcoming release(s) 3.3.1: We are in quite week, code tagged as R3_3_1 Final p2 repository is waiting at [1], I’ll update pmi and website on friday We closed 76 bugs in this cycle! [2] 3.3.2: Do we plan it? If yes, maybe we should split streams? Mars release: Version number: probably 3.4 Are we waiting for DLTK mars announcement? What features or bugs you plan for this release? [1] - http://download.eclipse.org/tools/pdt/updates/3.3.1/ [2] - https://projects.eclipse.org/projects/tools.pdt/releases/3.3.1/bugs -- Dawid Pakuła +48 795 996 064 ___ 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___ 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] PDT Help
Hi team, At begin, I was officially approved as new project lead. Thank you for a trust! From my side, I want introduce process of incremental cleaning up code and documentation. At first, it could be PDT User Manual. In past, we receive initial documentation from Zend Company (thank you for that). Unfortunately this documentation is now outdated and unmaintainable. Besides it’s also available in online mode only [1]. Would be good to convert it into more developer familiar format, update and move to org.eclipse.php.help plugin again. This also allow us to participate in eclipse info center [2]. Of course good documentation have also many other advantages. I have serveral propositions how we can do that: 1. Convert to eclipse wiki page, and compile to eclipse help on demand or while mvn clean install. Like Mylyn and Egit [3] advantages: * help can be updated by our user * webinterface disadvantages: * we haven’t full control on help * after each ui change, we have to remember about help update. Probably everybody forgot 2. Convert to creole wikitext / textile and put source directly inside help plugin repo. Like Xtext [3][4] advantages: * we can update help and source code in one patch * full control on help * gerrit :D disadvantages: * users need CLA signed to send contribution 3. Only cleanup html code and put to help plugin advantages: * probably everybody know HTML * same advantages as point 2 disadvantages: * more boilerplate code, probably unreadable without html editor + preview * same as point 2 4. Ignore me ;) My favourite is point 2. Our format can be Markdown, WikiText, Creole, Textile. [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=369635 [2] - https://help.eclipse.org/luna [3] - https://wiki.eclipse.org/DocumentationGuidelines/Example [4] - http://git.eclipse.org/c/tmf/org.eclipse.xtext.git/tree/docs/org.eclipse.xtext.doc.xdoc/xdoc -- Dawid Pakuła +48 795 996 064___ 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
Re: [pdt-dev] PHP 5.6 support
Hi, On 29 września 2014 at 15:19:34, Michał Niewrzał (micha...@zend.com) wrote: Hi, I started implementation of variadic parameters. Actually I'm not sure how exactly it should be done correctly, I don't know every part of PDT so it is hard to predict all implications. Probably none know now ;) I'm talking mainly about AST nodes structure. My first shot was to just extend FormalParameter with 'isVariadic' flag, but maybe it is to simple approach:) I will be grateful for every suggestion :) PHP 7 will introduce AST-based compilation, and as I see in parser [1] isReference and isVariadic are just a flags. So we can also use just a flag. We should remember about this flag in in TI, CA, Formatter and label providers. FormatParameter#isVariadic should simplify an access. But, if you introduce special field (like isOptional), you have to remember about ASTMatcher. [1] - https://github.com/php/php-src/blob/master/Zend/zend_language_parser.y#L546 Michal On Fri, Sep 26, 2014 at 12:23 PM, Michał Niewrzał wrote: Hi, I prepared first commit for PHP 5.6 support. It is just initial draft with 2 new elements: * Constant Scalar Expressions - https://wiki.php.net/rfc/const_scalar_exprs * Power Operator - https://wiki.php.net/rfc/pow-operator These two elements can be tested already. Any feedback (positive or negative) is appreciated :) Git Commit: https://git.eclipse.org/r/#/c/33947/ BTW, Language model is still not regenerated. Is there a simple way to install all necessary extensions? I tried to install them with pecl, but it is pretty slow method :) Thanks, Michal On Mon, Sep 22, 2014 at 2:58 PM, Dawid Pakuła wrote: Hi, Hi, I have some additional questions: 2. Generate code stubs and register it. Same for keywords Which part of code you are talking about exactly? See IPHPKeywordsInitializer and subclasses. Code stubs org.eclipse.php.core/Resources/language/php_ver (see README.txt howto generate it). Remember to update DefaultLanguageModelProvider after generation. 5. Copy/paste and extend parser. Current pdt parser are very close to original php parser, so their source code may be helpful + tests Can you point me place where I can find this original PHP parser? https://github.com/php/php-src/blob/PHP-5.6.1/Zend/zend_language_parser.y And one more question about generating language model. File "generate.php" is generating code based on loaded extensions. Is there a list of modules that need to be enabled during generation? This was my mistake while initial php 5.5 implementation. File names in languages/php5.5 are your list. Module_name.php ;) Thanks, Michal On Thu, Sep 18, 2014 at 12:12 AM, Dawid Pakuła wrote: Hi, most elements you will find in one commit : [1]. bug for php 5.6 is open [2] Steps: 1. Extend PHPVersion and where is used (projects wizard, project preferences and more…) 2. Generate code stubs and register it. Same for keywords 3. Copy/paste php 5.5 flexer and extend it. Two or three new tokens as I see(pow operator, variadic…) + tests 4. Create new AST nodes for DOM and Compiler tree 5. Copy/paste and extend parser. Current pdt parser are very close to original php parser, so their source code may be helpful + tests 6. Extend occurrences finder + tests 7. Extend formatter / syntax coloring + tests 8. Extend ASTMatcher + tests 9. Modify inference engine + tests 10. Modify CA + tests php 5.5 was in general easy to implement. With php 5.6 will be harder due new use function and use constant DLTK doesn’t allow to add additional informations to imports. Patch: [3] I hope it’s helpful. [1] - http://git.eclipse.org/c/pdt/org.eclipse.pdt.git/commit/?id=9034500b3b47f34efa42be4d8b18871d78493995 [2] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=435922 [3] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=437856 -- Dawid Pakuła +48 795 996 064 w3des.net ul. Grabiszyńska 108/10 53-437 Wrocław NIP: 894-293-95-95 REGON: 340769757 From: Michał Niewrzał Reply: PDT Developers > Date: 17 września 2014 at 23:53:02 To: PDT Developers > Subject: [pdt-dev] PHP 5.6 support Hi All, We (Zend Studio team) begin to think about support for PHP 5.6. Of course we need to start from PDT. It looks that I will be person most involved from our team and I want to start this conversation with at least general idea what need to be done. I heard that previous version 5.5 was implemented mostly by Dawid:) Dawid, can you write short (I hope) list with PDT parts that needs to be adjusted/extended? Thanks, Michal ___ 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:/
Re: [pdt-dev] PDT Help
Hi, others agree to option 2? What format you prefer? Markdown/Textile/Wikitext/Creole? My favourite is a markdown [1], very popular now. Wikitext have builtin editor with preview since last year. [1] - http://daringfireball.net/projects/markdown/syntax -- Dawid Pakuła +48 795 996 064 On 29 września 2014 at 09:24:36, Kaloyan Raev (kaloya...@zend.com) wrote: Hi Dawid, I completely agree that the PDT Help must be improved in the direction you suggest. Let's try option 2 as you suggest. I like the idea of having source and documentation together. We can build the habit of enforcing documentation updates when reviewing patches in Gerrit. Greetings, Kaloyan On Sat, Sep 27, 2014 at 2:47 PM, Dawid Pakuła wrote: Hi team, At begin, I was officially approved as new project lead. Thank you for a trust! From my side, I want introduce process of incremental cleaning up code and documentation. At first, it could be PDT User Manual. In past, we receive initial documentation from Zend Company (thank you for that). Unfortunately this documentation is now outdated and unmaintainable. Besides it’s also available in online mode only [1]. Would be good to convert it into more developer familiar format, update and move to org.eclipse.php.help plugin again. This also allow us to participate in eclipse info center [2]. Of course good documentation have also many other advantages. I have serveral propositions how we can do that: 1. Convert to eclipse wiki page, and compile to eclipse help on demand or while mvn clean install. Like Mylyn and Egit [3] advantages: * help can be updated by our user * webinterface disadvantages: * we haven’t full control on help * after each ui change, we have to remember about help update. Probably everybody forgot 2. Convert to creole wikitext / textile and put source directly inside help plugin repo. Like Xtext [3][4] advantages: * we can update help and source code in one patch * full control on help * gerrit :D disadvantages: * users need CLA signed to send contribution 3. Only cleanup html code and put to help plugin advantages: * probably everybody know HTML * same advantages as point 2 disadvantages: * more boilerplate code, probably unreadable without html editor + preview * same as point 2 4. Ignore me ;) My favourite is point 2. Our format can be Markdown, WikiText, Creole, Textile. [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=369635 [2] - https://help.eclipse.org/luna [3] - https://wiki.eclipse.org/DocumentationGuidelines/Example [4] - http://git.eclipse.org/c/tmf/org.eclipse.xtext.git/tree/docs/org.eclipse.xtext.doc.xdoc/xdoc -- Dawid Pakuła +48 795 996 064 ___ 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
Re: [pdt-dev] PHP 5.6 support
Hi, Good catch! I reported an issue to webmaster [1]. For now if this is same version, I think you can copy/paste it from php55 model. [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=446297 -- Dawid Pakuła +48 795 996 064 On 8 Oct 2014 at 13:30:33, Michał Niewrzał (micha...@zend.com) wrote: I'm not receiving notifications from gerrit, so it is possible that nobody know about update:). I rebuild almost whole language model, I had some problems with database extensions like ibm_db2 (these extensions are not updated), but core elements and most of other elements are up to date. Michal On Fri, Oct 3, 2014 at 1:07 PM, Michał Niewrzał wrote: I updated previous patch with new functionality: * Variadic Parameters * Unpacking Arguments Git Commit: https://git.eclipse.org/r/#/c/33947/ Michal On Mon, Sep 29, 2014 at 4:59 PM, Dawid Pakuła wrote: Hi, On 29 września 2014 at 15:19:34, Michał Niewrzał (micha...@zend.com) wrote: Hi, I started implementation of variadic parameters. Actually I'm not sure how exactly it should be done correctly, I don't know every part of PDT so it is hard to predict all implications. Probably none know now ;) I'm talking mainly about AST nodes structure. My first shot was to just extend FormalParameter with 'isVariadic' flag, but maybe it is to simple approach:) I will be grateful for every suggestion :) PHP 7 will introduce AST-based compilation, and as I see in parser [1] isReference and isVariadic are just a flags. So we can also use just a flag. We should remember about this flag in in TI, CA, Formatter and label providers. FormatParameter#isVariadic should simplify an access. But, if you introduce special field (like isOptional), you have to remember about ASTMatcher. [1] - https://github.com/php/php-src/blob/master/Zend/zend_language_parser.y#L546 Michal On Fri, Sep 26, 2014 at 12:23 PM, Michał Niewrzał wrote: Hi, I prepared first commit for PHP 5.6 support. It is just initial draft with 2 new elements: * Constant Scalar Expressions - https://wiki.php.net/rfc/const_scalar_exprs * Power Operator - https://wiki.php.net/rfc/pow-operator These two elements can be tested already. Any feedback (positive or negative) is appreciated :) Git Commit: https://git.eclipse.org/r/#/c/33947/ BTW, Language model is still not regenerated. Is there a simple way to install all necessary extensions? I tried to install them with pecl, but it is pretty slow method :) Thanks, Michal On Mon, Sep 22, 2014 at 2:58 PM, Dawid Pakuła wrote: Hi, Hi, I have some additional questions: 2. Generate code stubs and register it. Same for keywords Which part of code you are talking about exactly? See IPHPKeywordsInitializer and subclasses. Code stubs org.eclipse.php.core/Resources/language/php_ver (see README.txt howto generate it). Remember to update DefaultLanguageModelProvider after generation. 5. Copy/paste and extend parser. Current pdt parser are very close to original php parser, so their source code may be helpful + tests Can you point me place where I can find this original PHP parser? https://github.com/php/php-src/blob/PHP-5.6.1/Zend/zend_language_parser.y And one more question about generating language model. File "generate.php" is generating code based on loaded extensions. Is there a list of modules that need to be enabled during generation? This was my mistake while initial php 5.5 implementation. File names in languages/php5.5 are your list. Module_name.php ;) Thanks, Michal On Thu, Sep 18, 2014 at 12:12 AM, Dawid Pakuła wrote: Hi, most elements you will find in one commit : [1]. bug for php 5.6 is open [2] Steps: 1. Extend PHPVersion and where is used (projects wizard, project preferences and more…) 2. Generate code stubs and register it. Same for keywords 3. Copy/paste php 5.5 flexer and extend it. Two or three new tokens as I see(pow operator, variadic…) + tests 4. Create new AST nodes for DOM and Compiler tree 5. Copy/paste and extend parser. Current pdt parser are very close to original php parser, so their source code may be helpful + tests 6. Extend occurrences finder + tests 7. Extend formatter / syntax coloring + tests 8. Extend ASTMatcher + tests 9. Modify inference engine + tests 10. Modify CA + tests php 5.5 was in general easy to implement. With php 5.6 will be harder due new use function and use constant DLTK doesn’t allow to add additional informations to imports. Patch: [3] I hope it’s helpful. [1] - http://git.eclipse.org/c/pdt/org.eclipse.pdt.git/commit/?id=9034500b3b47f34efa42be4d8b18871d78493995 [2] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=435922 [3] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=437856 -- Dawid Pakuła +48 795 996 064 w3des.net ul. Grabiszyńska 108/10 53-437 Wrocław NIP: 894-293-95-95 REGON: 340769757 From: Michał Niewrzał Reply: PDT Developers > Date: 17 września 2014 at 23:53:02 To: PDT Developers > Subject: [pdt-dev] PHP 5.
Re: [pdt-dev] PDT Help
Hi, here is an initial patch [1] 1. I converted html to markdown (some issues have to be fixed manually) 2. Pages that was not connected to anything, was removed. This was documentation for Zend Studio features (like Semantic Analysis). After that documentation size is 2.2MB !!! 3. Whole documentation is no longer flat (see plugins/org.eclipse.php.help/docs/source) 4. Based on this structure, maven will generate IPHPContextsIds class, helpContexts.xml and toc.xml 5. Everything is done while maven clean install via ant and javascript (see plugins/org.eclipse.php.help/docs/source/build.xml and plugins/org.eclipse.php.help/docs/source/compile.js) 6. CSS is very similar to Github Atom markdown preview plugin. I hope you like it ;) Known issues: 1. Mylyn wikitext sometimes generate mailformed html code [2] 2. Some pages have wrong markdown code 3. We are using mylyn snapshots, due this issue [3] Maybe someone know better EPL friendly MarkdownToHTML converter? As an alternative, I could write it in JavaScript :/ [1] - https://git.eclipse.org/r/#/c/34783/ [2] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=446788 [3] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=445707 -- Dawid Pakuła On Mon, Sep 29, 2014 at 6:01 PM, Kaloyan Raev wrote: > I am used to both Markdown and Wikitext. > > Kaloyan > > On Mon, Sep 29, 2014 at 6:11 PM, Dawid Pakuła wrote: > >> Hi, >> >> others agree to option 2? >> >> What format you prefer? Markdown/Textile/Wikitext/Creole? >> My favourite is a markdown [1], very popular now. Wikitext have builtin >> editor with preview since last year. >> >> [1] - http://daringfireball.net/projects/markdown/syntax >> >> -- >> Dawid Pakuła >> +48 795 996 064 >> >> On 29 września 2014 at 09:24:36, Kaloyan Raev (kaloya...@zend.com) wrote: >> >> Hi Dawid, >> >> I completely agree that the PDT Help must be improved in the direction >> you suggest. >> >> Let's try option 2 as you suggest. I like the idea of having source and >> documentation together. We can build the habit of enforcing documentation >> updates when reviewing patches in Gerrit. >> >> Greetings, >> Kaloyan >> >> On Sat, Sep 27, 2014 at 2:47 PM, Dawid Pakuła wrote: >> >>> Hi team, >>> >>> At begin, I was officially approved as new project lead. Thank you for >>> a trust! >>> >>> From my side, I want introduce process of incremental cleaning up code >>> and documentation. At first, it could be PDT User Manual. >>> >>> In past, we receive initial documentation from Zend Company (thank you >>> for that). Unfortunately this documentation is now outdated and >>> unmaintainable. Besides it’s also available in online mode only [1]. >>> >>> Would be good to convert it into more developer familiar format, update >>> and move to org.eclipse.php.help plugin again. This also allow us to >>> participate in eclipse info center [2]. Of course good documentation have >>> also many other advantages. >>> >>> I have serveral propositions how we can do that: >>> >>> 1. Convert to eclipse wiki page, and compile to eclipse help on demand >>> or while mvn clean install. Like Mylyn and Egit [3] >>> advantages: >>>* help can be updated by our user >>>* webinterface >>> disadvantages: >>>* we haven’t full control on help >>>* after each ui change, we have to remember about help update. >>> Probably everybody forgot >>> >>> 2. Convert to creole wikitext / textile and put source directly inside >>> help plugin repo. Like Xtext [3][4] >>> advantages: >>>* we can update help and source code in one patch >>>* full control on help >>>* gerrit :D >>> disadvantages: >>>* users need CLA signed to send contribution >>> >>> 3. Only cleanup html code and put to help plugin >>> advantages: >>>* probably everybody know HTML >>>* same advantages as point 2 >>> disadvantages: >>>* more boilerplate code, probably unreadable without html editor + >>> preview >>>* same as point 2 >>> >>> 4. Ignore me ;) >>> >>> My favourite is point 2. Our format can be Markdown, WikiText, Creole, >>> Textile. >>> >>> [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=369635 >>> [2] - https://help.eclipse.org/luna >>> [3] - https://wiki.eclipse.org/DocumentationGuidelines/Example >>> [4] - >>> http://git.eclipse.org/
[pdt-dev] Debugger in Luna SR1
Hi, due many problems with debugger [1][2][3] in Luna SR1 I have a proposition to release current HEAD as PDT 3.3.2 and put it into marketplace [4]. As an alternative we can release special patch. What you think? [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=445903 [2] - https://www.eclipse.org/forums/index.php/t/823451/ [3] - http://stackoverflow.com/questions/26067892/xdebug-breakpoints-work-but-step-over-does-not [4] - https://marketplace.eclipse.org/content/php-development-tools -- Dawid Pakuła +48 795 996 064___ 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
Re: [pdt-dev] Debugger in Luna SR1
I prepared release record [1] and schedule to October 31, 2014. Let me know if you think that it’s too early. [1] - https://projects.eclipse.org/projects/tools.pdt/releases/3.3.2 -- Dawid Pakuła +48 795 996 064 On 22 Oct 2014 at 17:04:03, Jacek Pospychała (jacek.pospych...@gmail.com) wrote: +1 On Wed, Oct 22, 2014 at 4:42 PM, Kaloyan Raev wrote: I am OK with more frequent maintenance releases. On Wed, Oct 22, 2014 at 4:18 PM, Dawid Pakuła wrote: Hi, due many problems with debugger [1][2][3] in Luna SR1 I have a proposition to release current HEAD as PDT 3.3.2 and put it into marketplace [4]. As an alternative we can release special patch. What you think? [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=445903 [2] - https://www.eclipse.org/forums/index.php/t/823451/ [3] - http://stackoverflow.com/questions/26067892/xdebug-breakpoints-work-but-step-over-does-not [4] - https://marketplace.eclipse.org/content/php-development-tools -- Dawid Pakuła +48 795 996 064 ___ 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
Re: [pdt-dev] Debugger in Luna SR1
For the record, 3.3.2 build waiting on download server [1] [1] - http://download.eclipse.org/tools/pdt/updates/3.3.2 -- Dawid Pakuła +48 795 996 064 On 23 Oct 2014 at 01:39:08, Dawid Pakuła (zu...@w3des.net) wrote: I prepared release record [1] and schedule to October 31, 2014. Let me know if you think that it’s too early. [1] - https://projects.eclipse.org/projects/tools.pdt/releases/3.3.2 -- Dawid Pakuła +48 795 996 064 On 22 Oct 2014 at 17:04:03, Jacek Pospychała (jacek.pospych...@gmail.com) wrote: +1 On Wed, Oct 22, 2014 at 4:42 PM, Kaloyan Raev wrote: I am OK with more frequent maintenance releases. On Wed, Oct 22, 2014 at 4:18 PM, Dawid Pakuła wrote: Hi, due many problems with debugger [1][2][3] in Luna SR1 I have a proposition to release current HEAD as PDT 3.3.2 and put it into marketplace [4]. As an alternative we can release special patch. What you think? [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=445903 [2] - https://www.eclipse.org/forums/index.php/t/823451/ [3] - http://stackoverflow.com/questions/26067892/xdebug-breakpoints-work-but-step-over-does-not [4] - https://marketplace.eclipse.org/content/php-development-tools -- Dawid Pakuła +48 795 996 064 ___ 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
Re: [pdt-dev] Debugger in Luna SR1
It’s empty. Bugzilla should remember latest selection. -- Dawid Pakuła +48 795 996 064 On 28 Oct 2014 at 20:47:55, Michał Niewrzał (micha...@zend.com) wrote: Dawid, can you check default PDT version for bugzilla? By default I have 3.2.2 for new bug:) Michal On Tue, Oct 28, 2014 at 11:09 AM, Dawid Pakuła wrote: For the record, 3.3.2 build waiting on download server [1] [1] - http://download.eclipse.org/tools/pdt/updates/3.3.2 -- Dawid Pakuła +48 795 996 064 On 23 Oct 2014 at 01:39:08, Dawid Pakuła (zu...@w3des.net) wrote: I prepared release record [1] and schedule to October 31, 2014. Let me know if you think that it’s too early. [1] - https://projects.eclipse.org/projects/tools.pdt/releases/3.3.2 -- Dawid Pakuła +48 795 996 064 On 22 Oct 2014 at 17:04:03, Jacek Pospychała (jacek.pospych...@gmail.com) wrote: +1 On Wed, Oct 22, 2014 at 4:42 PM, Kaloyan Raev wrote: I am OK with more frequent maintenance releases. On Wed, Oct 22, 2014 at 4:18 PM, Dawid Pakuła wrote: Hi, due many problems with debugger [1][2][3] in Luna SR1 I have a proposition to release current HEAD as PDT 3.3.2 and put it into marketplace [4]. As an alternative we can release special patch. What you think? [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=445903 [2] - https://www.eclipse.org/forums/index.php/t/823451/ [3] - http://stackoverflow.com/questions/26067892/xdebug-breakpoints-work-but-step-over-does-not [4] - https://marketplace.eclipse.org/content/php-development-tools -- Dawid Pakuła +48 795 996 064 ___ 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 ___ 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
Re: [pdt-dev] Debugger in Luna SR1
Hi, PDT 3.3.2 released [1][2][3]. [1] - http://download.eclipse.org/tools/pdt/updates/3.3.2/ [2] - http://git.eclipse.org/c/pdt/org.eclipse.pdt.git/tag/?id=R3_3_2 [3] - https://marketplace.eclipse.org/content/php-development-tools -- Dawid Pakuła +48 795 996 064 On 28 Oct 2014 at 20:54:41, Michał Niewrzał (micha...@zend.com) wrote: So it looks that by accident I set my previous reported bug as 3.2.2:) Thanks On Tue, Oct 28, 2014 at 8:51 PM, Dawid Pakuła wrote: It’s empty. Bugzilla should remember latest selection. -- Dawid Pakuła +48 795 996 064 On 28 Oct 2014 at 20:47:55, Michał Niewrzał (micha...@zend.com) wrote: Dawid, can you check default PDT version for bugzilla? By default I have 3.2.2 for new bug:) Michal On Tue, Oct 28, 2014 at 11:09 AM, Dawid Pakuła wrote: For the record, 3.3.2 build waiting on download server [1] [1] - http://download.eclipse.org/tools/pdt/updates/3.3.2 -- Dawid Pakuła +48 795 996 064 On 23 Oct 2014 at 01:39:08, Dawid Pakuła (zu...@w3des.net) wrote: I prepared release record [1] and schedule to October 31, 2014. Let me know if you think that it’s too early. [1] - https://projects.eclipse.org/projects/tools.pdt/releases/3.3.2 -- Dawid Pakuła +48 795 996 064 On 22 Oct 2014 at 17:04:03, Jacek Pospychała (jacek.pospych...@gmail.com) wrote: +1 On Wed, Oct 22, 2014 at 4:42 PM, Kaloyan Raev wrote: I am OK with more frequent maintenance releases. On Wed, Oct 22, 2014 at 4:18 PM, Dawid Pakuła wrote: Hi, due many problems with debugger [1][2][3] in Luna SR1 I have a proposition to release current HEAD as PDT 3.3.2 and put it into marketplace [4]. As an alternative we can release special patch. What you think? [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=445903 [2] - https://www.eclipse.org/forums/index.php/t/823451/ [3] - http://stackoverflow.com/questions/26067892/xdebug-breakpoints-work-but-step-over-does-not [4] - https://marketplace.eclipse.org/content/php-development-tools -- Dawid Pakuła +48 795 996 064 ___ 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 ___ 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
[pdt-dev] Static latest repository for stable and nightly releases
Hi again :P I have a proposition to create two composite [1] update sites for nightly and stable, similar to mylyn latest [2]: http://download.eclipse.org/tools/pdt/updates/latest http://download.eclipse.org/tools/pdt/updates/latest-nightly Why they are important? Now is not easy to be on “always latest release” or “always latest nightly". Users need to check updates on our sites, and add new update sites to his eclipse installation. latest and latest-nightly will also simplify adopters life ;) My questions: 1. What you think about this? Do you agree or no? 2. latest artifacts should also contain link to corresponding DLTK update site? [1] - https://wiki.eclipse.org/Equinox/p2/Composite_Repositories_%28new%29 [2] - http://download.eclipse.org/mylyn/releases/latest -- Dawid Pakuła +48 795 996 064___ 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
Re: [pdt-dev] New PDT commiter - Me
Welcome! -- Dawid Pakuła +48 795 996 064 On 17 Nov 2014 at 16:18:50, Peter Janovic (sn...@seznam.cz) wrote: I'm really happy, when I see new contributor to the PDT project. -- Původní zpráva -- Od: Kaloyan Raev Datum: 17. 11. 2014 v 15:38:22 Předmět: Re: [pdt-dev] New PDT commiter - Me Congratulations, Michal! Looking forward for your next great contributions! Let the force be with you :-) Kaloyan On Mon, Nov 17, 2014 at 4:35 PM, Michał Niewrzał wrote: Hi All, Just a moment ago I received info that all necessary paperwork is accepted and I'm new full PDT commiter:) Thank you for choosing me and all your votes ;) I believe that together will make PDT greater tool for all PHP developers;) Cheers! Michał ___ 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
Re: [pdt-dev] pdt-dev Digest, Vol 93, Issue 4
Hi, you need DLTK 5.0. Add this update site to your software list and try again: http://download.eclipse.org/technology/dltk/updates-dev/5.0/ -- Dawid Pakuła +48 795 996 064 On 18 Nov 2014 at 19:54:16, Scott Miller (smact...@slightlysuspect.com) wrote: Hi, I am having trouble installing PDT. I get the following errors: Cannot complete the install because one or more required items could not be found. Software being installed: PHP Development Tools (PDT) 3.3.2.201410231314 (org.eclipse.php.feature.group 3.3.2.201410231314) Missing requirement: PHP Development Tools (PDT) 3.3.2.201410231314 (org.eclipse.php.feature.group 3.3.2.201410231314) requires 'org.eclipse.dltk.core.feature.group 5.0.0' but it could not be found I am using Juno and I have tried reloading the available software sites solution I saw in the list archive. Any help is appreciated, Scott ___ 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
Re: [pdt-dev] Static latest repository for stable and nightly releases
Hi, I created composite repositories: http://download.eclipse.org/tools/pdt/updates/latest http://download.eclipse.org/tools/pdt/updates/latest-nightly My question about DLTK in composite repository is still actual. -- Dawid Pakuła +48 795 996 064 On 31 Oct 2014 at 10:25:06, Michał Niewrzał (micha...@zend.com) wrote: 1. I totally agree:) It will give users instant update without any additional work. 2. I'm not sure what would be best approach. Ps. Main site (http://eclipse.org/pdt/) needs to be updated to 3.3.2;) Michal On Fri, Oct 31, 2014 at 10:09 AM, Dawid Pakuła wrote: Hi again :P I have a proposition to create two composite [1] update sites for nightly and stable, similar to mylyn latest [2]: http://download.eclipse.org/tools/pdt/updates/latest http://download.eclipse.org/tools/pdt/updates/latest-nightly Why they are important? Now is not easy to be on “always latest release” or “always latest nightly". Users need to check updates on our sites, and add new update sites to his eclipse installation. latest and latest-nightly will also simplify adopters life ;) My questions: 1. What you think about this? Do you agree or no? 2. latest artifacts should also contain link to corresponding DLTK update site? [1] - https://wiki.eclipse.org/Equinox/p2/Composite_Repositories_%28new%29 [2] - http://download.eclipse.org/mylyn/releases/latest -- Dawid Pakuła +48 795 996 064 ___ 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] Prepare 3.4.* release
Hi, just for notification. I updated plugin versions to 3.4.0 and moved nightly update site to 3.4-nightly [1] When bug 454635 [2] will be fixed, I’ll move promote script to hudson job. [1] - http://download.eclipse.org/tools/pdt/updates/3.4-nightly/ [2] - http://eclip.se/454635 -- Dawid Pakuła +48 795 996 064___ 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
Re: [pdt-dev] Add Automated Error Reporting to all EPP packages
+1 -- Dawid Pakuła +48 795 996 064 On 12 Jan 2015 at 09:56:18, Michał Niewrzał (micha...@zend.com) wrote: +1. Michal On Mon, Jan 12, 2015 at 9:52 AM, Kaloyan Raev wrote: Hi, There is a discussion in https://bugs.eclipse.org/bugs/show_bug.cgi?id=457180 to add the automated error reporting to all EPP packages. I believe this will help us to improve the quality of PDT and we should have it in the PHP package. Any objections? Greetings, Kaloyan ___ 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] 3.4 release review
Hi Team, I have to prepare release review for 3.4, so I need some help from you ;) Here [1] I prepared basic New & Noteworthy page, feel free to update it. If you have any new feature for this release, please merge it and fill N&N page until Friday . I want to generate and send IP Log on Friday. After that only commiter contributions will be allowed. [1] - https://wiki.eclipse.org/PDT/NewIn34 -- Dawid Pakuła +48 795 996 064___ 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
Re: [pdt-dev] 3.4 release review
Hi Kaloyan, I’m very happy since I’ve read latest update on this bug ;) I should collect review documentation, send IP Log and request an approval from PMC before SR2 RC1 which will be released in next Friday. [1] [1] - https://wiki.eclipse.org/Luna/Simultaneous_Release_Plan -- Dawid Pakuła +48 795 996 064 On 12 Jan 2015 at 15:50:02, Kaloyan Raev (kaloya...@zend.com) wrote: Hi Dawid, I plan to contribute the PHP Refactoring capabilities of Zend Studio to the Eclipse PDT project. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=149818#c12 I wondered when is the deadline for having it in the 3.4 release. I will push the code in Gerrit in the next few days, but I guess we need to go for an IP review, which may take some time. Greetings, Kaloyan On Mon, Jan 12, 2015 at 11:58 AM, Dawid Pakuła wrote: Hi Team, I have to prepare release review for 3.4, so I need some help from you ;) Here [1] I prepared basic New & Noteworthy page, feel free to update it. If you have any new feature for this release, please merge it and fill N&N page until Friday . I want to generate and send IP Log on Friday. After that only commiter contributions will be allowed. [1] - https://wiki.eclipse.org/PDT/NewIn34 -- Dawid Pakuła +48 795 996 064 ___ 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
Re: [pdt-dev] Patch for Bug 457201
Hi, Thierry like You, is a commiter, so no. See also this diagram [1] [1] - https://eclipse.org/legal/EclipseLegalProcessPoster.pdf -- Dawid Pakuła +48 795 996 064 On 13 Jan 2015 at 00:00:11, Michał Niewrzał (micha...@zend.com) wrote: Hi, I just tested patch for https://bugs.eclipse.org/bugs/show_bug.cgi?id=457201. Should I create CQ for it before I will merge it (+1090 lines)? Thanks, Michal ___ 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
Re: [pdt-dev] PDT Help
Hi, I just rebased and fixed couple issues. Can we release it as part of PDT 3.4.0 ? -- Dawid Pakuła +48 795 996 064 On 13 Oct 2014 at 02:13:01, Dawid Pakuła (zu...@w3des.net) wrote: Hi, here is an initial patch [1] 1. I converted html to markdown (some issues have to be fixed manually) 2. Pages that was not connected to anything, was removed. This was documentation for Zend Studio features (like Semantic Analysis). After that documentation size is 2.2MB !!! 3. Whole documentation is no longer flat (see plugins/org.eclipse.php.help/docs/source) 4. Based on this structure, maven will generate IPHPContextsIds class, helpContexts.xml and toc.xml 5. Everything is done while maven clean install via ant and javascript (see plugins/org.eclipse.php.help/docs/source/build.xml and plugins/org.eclipse.php.help/docs/source/compile.js) 6. CSS is very similar to Github Atom markdown preview plugin. I hope you like it ;) Known issues: 1. Mylyn wikitext sometimes generate mailformed html code [2] 2. Some pages have wrong markdown code 3. We are using mylyn snapshots, due this issue [3] Maybe someone know better EPL friendly MarkdownToHTML converter? As an alternative, I could write it in JavaScript :/ [1] - https://git.eclipse.org/r/#/c/34783/ [2] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=446788 [3] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=445707 -- Dawid Pakuła On Mon, Sep 29, 2014 at 6:01 PM, Kaloyan Raev wrote: I am used to both Markdown and Wikitext. Kaloyan On Mon, Sep 29, 2014 at 6:11 PM, Dawid Pakuła wrote: Hi, others agree to option 2? What format you prefer? Markdown/Textile/Wikitext/Creole? My favourite is a markdown [1], very popular now. Wikitext have builtin editor with preview since last year. [1] - http://daringfireball.net/projects/markdown/syntax -- Dawid Pakuła +48 795 996 064 On 29 września 2014 at 09:24:36, Kaloyan Raev (kaloya...@zend.com) wrote: Hi Dawid, I completely agree that the PDT Help must be improved in the direction you suggest. Let's try option 2 as you suggest. I like the idea of having source and documentation together. We can build the habit of enforcing documentation updates when reviewing patches in Gerrit. Greetings, Kaloyan On Sat, Sep 27, 2014 at 2:47 PM, Dawid Pakuła wrote: Hi team, At begin, I was officially approved as new project lead. Thank you for a trust! From my side, I want introduce process of incremental cleaning up code and documentation. At first, it could be PDT User Manual. In past, we receive initial documentation from Zend Company (thank you for that). Unfortunately this documentation is now outdated and unmaintainable. Besides it’s also available in online mode only [1]. Would be good to convert it into more developer familiar format, update and move to org.eclipse.php.help plugin again. This also allow us to participate in eclipse info center [2]. Of course good documentation have also many other advantages. I have serveral propositions how we can do that: 1. Convert to eclipse wiki page, and compile to eclipse help on demand or while mvn clean install. Like Mylyn and Egit [3] advantages: * help can be updated by our user * webinterface disadvantages: * we haven’t full control on help * after each ui change, we have to remember about help update. Probably everybody forgot 2. Convert to creole wikitext / textile and put source directly inside help plugin repo. Like Xtext [3][4] advantages: * we can update help and source code in one patch * full control on help * gerrit :D disadvantages: * users need CLA signed to send contribution 3. Only cleanup html code and put to help plugin advantages: * probably everybody know HTML * same advantages as point 2 disadvantages: * more boilerplate code, probably unreadable without html editor + preview * same as point 2 4. Ignore me ;) My favourite is point 2. Our format can be Markdown, WikiText, Creole, Textile. [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=369635 [2] - https://help.eclipse.org/luna [3] - https://wiki.eclipse.org/DocumentationGuidelines/Example [4] - http://git.eclipse.org/c/tmf/org.eclipse.xtext.git/tree/docs/org.eclipse.xtext.doc.xdoc/xdoc -- Dawid Pakuła +48 795 996 064 ___ 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/pd
Re: [pdt-dev] PDT Help
Run make install on help plugin. I have to register external build runner for help project. -- Dawid Pakuła +48 795 996 064 On 13 Jan 2015 at 13:59:16, Michał Niewrzał (micha...@zend.com) wrote: I fetched patch from gerrit and I have problem with deleted IPHPHelpContextIds. I missed something? Michal On Tue, Jan 13, 2015 at 1:52 PM, Dawid Pakuła wrote: Hi, I just rebased and fixed couple issues. Can we release it as part of PDT 3.4.0 ? -- Dawid Pakuła +48 795 996 064 On 13 Oct 2014 at 02:13:01, Dawid Pakuła (zu...@w3des.net) wrote: Hi, here is an initial patch [1] 1. I converted html to markdown (some issues have to be fixed manually) 2. Pages that was not connected to anything, was removed. This was documentation for Zend Studio features (like Semantic Analysis). After that documentation size is 2.2MB !!! 3. Whole documentation is no longer flat (see plugins/org.eclipse.php.help/docs/source) 4. Based on this structure, maven will generate IPHPContextsIds class, helpContexts.xml and toc.xml 5. Everything is done while maven clean install via ant and javascript (see plugins/org.eclipse.php.help/docs/source/build.xml and plugins/org.eclipse.php.help/docs/source/compile.js) 6. CSS is very similar to Github Atom markdown preview plugin. I hope you like it ;) Known issues: 1. Mylyn wikitext sometimes generate mailformed html code [2] 2. Some pages have wrong markdown code 3. We are using mylyn snapshots, due this issue [3] Maybe someone know better EPL friendly MarkdownToHTML converter? As an alternative, I could write it in JavaScript :/ [1] - https://git.eclipse.org/r/#/c/34783/ [2] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=446788 [3] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=445707 -- Dawid Pakuła On Mon, Sep 29, 2014 at 6:01 PM, Kaloyan Raev wrote: I am used to both Markdown and Wikitext. Kaloyan On Mon, Sep 29, 2014 at 6:11 PM, Dawid Pakuła wrote: Hi, others agree to option 2? What format you prefer? Markdown/Textile/Wikitext/Creole? My favourite is a markdown [1], very popular now. Wikitext have builtin editor with preview since last year. [1] - http://daringfireball.net/projects/markdown/syntax -- Dawid Pakuła +48 795 996 064 On 29 września 2014 at 09:24:36, Kaloyan Raev (kaloya...@zend.com) wrote: Hi Dawid, I completely agree that the PDT Help must be improved in the direction you suggest. Let's try option 2 as you suggest. I like the idea of having source and documentation together. We can build the habit of enforcing documentation updates when reviewing patches in Gerrit. Greetings, Kaloyan On Sat, Sep 27, 2014 at 2:47 PM, Dawid Pakuła wrote: Hi team, At begin, I was officially approved as new project lead. Thank you for a trust! From my side, I want introduce process of incremental cleaning up code and documentation. At first, it could be PDT User Manual. In past, we receive initial documentation from Zend Company (thank you for that). Unfortunately this documentation is now outdated and unmaintainable. Besides it’s also available in online mode only [1]. Would be good to convert it into more developer familiar format, update and move to org.eclipse.php.help plugin again. This also allow us to participate in eclipse info center [2]. Of course good documentation have also many other advantages. I have serveral propositions how we can do that: 1. Convert to eclipse wiki page, and compile to eclipse help on demand or while mvn clean install. Like Mylyn and Egit [3] advantages: * help can be updated by our user * webinterface disadvantages: * we haven’t full control on help * after each ui change, we have to remember about help update. Probably everybody forgot 2. Convert to creole wikitext / textile and put source directly inside help plugin repo. Like Xtext [3][4] advantages: * we can update help and source code in one patch * full control on help * gerrit :D disadvantages: * users need CLA signed to send contribution 3. Only cleanup html code and put to help plugin advantages: * probably everybody know HTML * same advantages as point 2 disadvantages: * more boilerplate code, probably unreadable without html editor + preview * same as point 2 4. Ignore me ;) My favourite is point 2. Our format can be Markdown, WikiText, Creole, Textile. [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=369635 [2] - https://help.eclipse.org/luna [3] - https://wiki.eclipse.org/DocumentationGuidelines/Example [4] - http://git.eclipse.org/c/tmf/org.eclipse.xtext.git/tree/docs/org.eclipse.xtext.doc.xdoc/xdoc -- Dawid Pakuła +48 795 996 064 ___ 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
Re: [pdt-dev] PDT Help
Hi, now everything should be ok. Documentation is still outdated. I planned to fix this while RC phase. -- Dawid Pakuła +48 795 996 064 On 13 Jan 2015 at 14:22:35, Michał Niewrzał (micha...@zend.com) wrote: Thanks. Now PDT is compiling and help is working, but lots of pages got exception like this or similar: org.xml.sax.SAXParseException; lineNumber: 9; columnNumber: 20; The element type "tr" must be terminated by the matching end-tag "". at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257) I didn't mark all of them in gerrit because too much of links are broken. I just clicked through whole PDT User Guide tree. And I also noticed that we need to add PHP 5.6 in plugins/org.eclipse.php.help/docs/source/016-concepts/008-php_support.md. Michal On Tue, Jan 13, 2015 at 2:00 PM, Dawid Pakuła wrote: Run make install on help plugin. I have to register external build runner for help project. -- Dawid Pakuła +48 795 996 064 On 13 Jan 2015 at 13:59:16, Michał Niewrzał (micha...@zend.com) wrote: I fetched patch from gerrit and I have problem with deleted IPHPHelpContextIds. I missed something? Michal On Tue, Jan 13, 2015 at 1:52 PM, Dawid Pakuła wrote: Hi, I just rebased and fixed couple issues. Can we release it as part of PDT 3.4.0 ? -- Dawid Pakuła +48 795 996 064 On 13 Oct 2014 at 02:13:01, Dawid Pakuła (zu...@w3des.net) wrote: Hi, here is an initial patch [1] 1. I converted html to markdown (some issues have to be fixed manually) 2. Pages that was not connected to anything, was removed. This was documentation for Zend Studio features (like Semantic Analysis). After that documentation size is 2.2MB !!! 3. Whole documentation is no longer flat (see plugins/org.eclipse.php.help/docs/source) 4. Based on this structure, maven will generate IPHPContextsIds class, helpContexts.xml and toc.xml 5. Everything is done while maven clean install via ant and javascript (see plugins/org.eclipse.php.help/docs/source/build.xml and plugins/org.eclipse.php.help/docs/source/compile.js) 6. CSS is very similar to Github Atom markdown preview plugin. I hope you like it ;) Known issues: 1. Mylyn wikitext sometimes generate mailformed html code [2] 2. Some pages have wrong markdown code 3. We are using mylyn snapshots, due this issue [3] Maybe someone know better EPL friendly MarkdownToHTML converter? As an alternative, I could write it in JavaScript :/ [1] - https://git.eclipse.org/r/#/c/34783/ [2] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=446788 [3] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=445707 -- Dawid Pakuła On Mon, Sep 29, 2014 at 6:01 PM, Kaloyan Raev wrote: I am used to both Markdown and Wikitext. Kaloyan On Mon, Sep 29, 2014 at 6:11 PM, Dawid Pakuła wrote: Hi, others agree to option 2? What format you prefer? Markdown/Textile/Wikitext/Creole? My favourite is a markdown [1], very popular now. Wikitext have builtin editor with preview since last year. [1] - http://daringfireball.net/projects/markdown/syntax -- Dawid Pakuła +48 795 996 064 On 29 września 2014 at 09:24:36, Kaloyan Raev (kaloya...@zend.com) wrote: Hi Dawid, I completely agree that the PDT Help must be improved in the direction you suggest. Let's try option 2 as you suggest. I like the idea of having source and documentation together. We can build the habit of enforcing documentation updates when reviewing patches in Gerrit. Greetings, Kaloyan On Sat, Sep 27, 2014 at 2:47 PM, Dawid Pakuła wrote: Hi team, At begin, I was officially approved as new project lead. Thank you for a trust! From my side, I want introduce process of incremental cleaning up code and documentation. At first, it could be PDT User Manual. In past, we receive initial documentation from Zend Company (thank you for that). Unfortunately this documentation is now outdated and unmaintainable. Besides it’s also available in online mode only [1]. Would be good to convert it into more developer familiar format, update and move to org.eclipse.php.help plugin again. This also allow us to participate in eclipse info center [2]. Of course good documentation have also many other advantages. I have serveral propositions how we can do that: 1. Convert to eclipse wiki page, and compile to eclipse help on demand or while mvn clean install. Like Mylyn and Egit [3] advantages: * help can be updated by our user * webinterface disadvantages: * we haven’t full control on help * after each ui change, we have to remember about help update. Probably everybody forgot 2. Convert to creole wikitext / textile and put source directly inside help plugin repo. Like Xtext [3][4] advantages: * we can update help and source code in one patch * full control on help * gerrit :D disadvantages: * users need CLA signed to send contribution 3. Only cleanup html code and put to help plugin advantages: * probably everybody know HTML * same advant
Re: [pdt-dev] rhino/nashorn js-scripts - jdk8
Hi, Thank you for that! As I see in bug, make it compatible with JDK8 should be simple. It’s time to install JDK 8 on my test machine ;) -- Dawid Pakuła +48 795 996 064 On 19 Jan 2015 at 14:16:09, Patrik Plihal (patrik.pli...@gmail.com) wrote: Hello, just wanted to point out that while pdt compiled fine with jdk8 (and afaik should still) - a recent addition (compile.js somwhere in the help package under /docs/build ) requires jdk < 8 since it uses the 'importPackage' statement, which in JDK8 does not exists anymore. see https://stackoverflow.com/questions/22531159/ant-script-importpackage-does-not-work-after-upgrading-to-ant-1-9-2 and https://bugs.openjdk.java.net/browse/JDK-8025132 Regards Patrik ___ 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
Re: [pdt-dev] Refactoring component in Bugzila
Good point! Who should be a default owner? php.core-inbox, php.ui-inbox or should I request dedicated account for this component only: php.refactoring-inbox (similar to debugger component)? -- Dawid Pakuła +48 795 996 064 On 20 Jan 2015 at 13:23:09, Michał Niewrzał (micha...@zend.com) wrote: Hi All, Since we have refactoring functionality I think we need component in Bugzilla for it:) Michal ___ 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
Re: [pdt-dev] 3.4 release review
Hi, I forgot write here, sorry :/ I have to resend our ip log, I planned do it on next Friday (Jan 29), so we have additional week for non-commiter patches. -- Dawid Pakuła +48 795 996 064 On 22 Jan 2015 at 11:06:33, Michał Niewrzał (micha...@zend.com) wrote: Hi Dawid, You wrote: I want to generate and send IP Log on Friday. After that only commiter contributions will be allowed. Does it mean we should not merge patches from non-commiters? Michal On Mon, Jan 12, 2015 at 5:49 PM, Kaloyan Raev wrote: OK. I will try to hurry up. If I cannot make it for Luna SR2, we will have it for Mars. On Monday, January 12, 2015, thierry blind wrote: Hi Kaloyan, that's great news! :) From: kaloya...@zend.com Date: Mon, 12 Jan 2015 16:49:19 +0200 To: pdt-dev@eclipse.org Subject: Re: [pdt-dev] 3.4 release review Hi Dawid, I plan to contribute the PHP Refactoring capabilities of Zend Studio to the Eclipse PDT project. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=149818#c12 I wondered when is the deadline for having it in the 3.4 release. I will push the code in Gerrit in the next few days, but I guess we need to go for an IP review, which may take some time. Greetings, Kaloyan On Mon, Jan 12, 2015 at 11:58 AM, Dawid Pakuła wrote: Hi Team, I have to prepare release review for 3.4, so I need some help from you ;) Here [1] I prepared basic New & Noteworthy page, feel free to update it. If you have any new feature for this release, please merge it and fill N&N page until Friday . I want to generate and send IP Log on Friday. After that only commiter contributions will be allowed. [1] - https://wiki.eclipse.org/PDT/NewIn34 -- Dawid Pakuła +48 795 996 064 ___ 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___ 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
Re: [pdt-dev] Refactoring component in Bugzila
Hi, just now I created refactoring component on bugzilla. Default assignee set to : php.refactoring-in...@eclipse.org -- Dawid Pakuła +48 795 996 064 On 26 Jan 2015 at 23:09:34, Michał Niewrzał (micha...@zend.com) wrote: I started topic and I forgot to be active, sorry:/ I think to be consistent we can create - php.refactoring-inbox. If not then php.core-inbox (similar to formatter) has my vote :) Michal On Tue, Jan 20, 2015 at 1:57 PM, Dawid Pakuła wrote: Good point! Who should be a default owner? php.core-inbox, php.ui-inbox or should I request dedicated account for this component only: php.refactoring-inbox (similar to debugger component)? -- Dawid Pakuła +48 795 996 064 On 20 Jan 2015 at 13:23:09, Michał Niewrzał (micha...@zend.com) wrote: Hi All, Since we have refactoring functionality I think we need component in Bugzilla for it:) Michal ___ 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
[pdt-dev] IPLog for PDT 3.4.0
Hi, just for a reminder. Tomorrow (friday) is last day to merge changes from non-committers. -- Dawid Pakuła +48 795 996 064 ___ 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] 3.4 release
Hi, just for remind. We are while 3.4 release review [1] After 9 days we go to quite week, so there will be no more builds for 3.4 release (18 Feb. 2015 is a last day). PS. Now is best time to review and update our documentation ;) [1] - https://projects.eclipse.org/projects/tools.pdt/releases/3.4/review -- Dawid Pakuła +48 795 996 064 ___ 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
Re: [pdt-dev] 3.4 release
Hi, reminder: tomorrow is last day to update our builds for Luna SR2 release. Current RC is waiting here: http://download.eclipse.org/tools/pdt/updates/3.4-rc4/ -- Dawid Pakuła +48 795 996 064 On 9 Feb 2015 at 21:52:29, Dawid Pakuła (zu...@w3des.net) wrote: Hi, just for remind. We are while 3.4 release review [1] After 9 days we go to quite week, so there will be no more builds for 3.4 release (18 Feb. 2015 is a last day). PS. Now is best time to review and update our documentation ;) [1] - https://projects.eclipse.org/projects/tools.pdt/releases/3.4/review -- Dawid Pakuła +48 795 996 064 ___ 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
Re: [pdt-dev] 3.4 release
Hi, thanks, SR2 contribution updated [1] [1] - http://download.eclipse.org/tools/pdt/updates/3.4-rc4a/ -- Dawid Pakuła +48 795 996 064 On 17 Feb 2015 at 19:28:51, Kaloyan Raev (kaloya...@zend.com) wrote: Hi again, I am done with this. Kaloyan On Tue, Feb 17, 2015 at 5:32 PM, Kaloyan Raev wrote: Hi Dawid, I am working on the PHP Refactoring documentation. I will finish it later today. Greetings, Kaloyan On Tue, Feb 17, 2015 at 5:30 PM, Dawid Pakuła wrote: Hi, reminder: tomorrow is last day to update our builds for Luna SR2 release. Current RC is waiting here: http://download.eclipse.org/tools/pdt/updates/3.4-rc4/ -- Dawid Pakuła +48 795 996 064 On 9 Feb 2015 at 21:52:29, Dawid Pakuła (zu...@w3des.net) wrote: Hi, just for remind. We are while 3.4 release review [1] After 9 days we go to quite week, so there will be no more builds for 3.4 release (18 Feb. 2015 is a last day). PS. Now is best time to review and update our documentation ;) [1] - https://projects.eclipse.org/projects/tools.pdt/releases/3.4/review -- Dawid Pakuła +48 795 996 064 ___ 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] Formalize commit / patch description patterns
Hi, I have two proposition for today. 1. Since around year, most (if not all) commit messages follow this pattern at first line: Bug 12345 / No bug - Short bug description I propose to make it as a standard and put information about this into our Contribution Guide [1] 2. As you probably noticed, since couple days (weeks) gerrit automatically add patch and commit links to our bugs. To avoid confusion and questions like “Is this ready to review / IP process?” i have a proposition to add “[WIP]” prefix before bug description: Bug 1234 - [WIP] Description Alternative could be: [WIP] Bug 1234 - Description Platform UI standard. But this probably also disable gerrit bot until message update (I’m not sure). What do you think / prefer? [1] - https://wiki.eclipse.org/PDT/Contributing -- Dawid Pakuła +48 795 996 064___ 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] Google Summer of Code 2015
Hi, Here is an official eclipse wiki page for GSoC 2015 [1] and announcement from eclipse soc-dev mailing list [2] Everyone are welcome to provide ideas [3]. [1] - https://wiki.eclipse.org/Google_Summer_of_Code_2015 [2] - https://dev.eclipse.org/mhonarc/lists/soc-dev/msg00493.html [3] - https://wiki.eclipse.org/Google_Summer_of_Code_2015_Ideas -- Dawid Pakuła +48 795 996 064 ___ 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] Rename 3.4.1 to 3.5
Hi team! Due recent and upcoming changes in PDT debugger like [1], and other that for example will require us to use never DLTK ([2],[3]) I think we should abandon 3.4.1 and deliver 3.5 to eclipse mars. What you think? BTW: 3.4 is released ;) [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=459507 [2] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=457621 [3] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=438087 -- Dawid Pakuła +48 795 996 064 ___ 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
Re: [pdt-dev] Rename 3.4.1 to 3.5
Hi, I updated release record [1] and sent announcement to cross-project list [2]. I also sent request to rename version on bugzilla [3] [1] - https://projects.eclipse.org/projects/tools.pdt/releases/3.5 [2] - https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg11603.html [3] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=461146 -- Dawid Pakuła +48 795 996 064 On 28 Feb 2015 at 10:58:01, thierry blind (thierrybl...@msn.com) wrote: > Hi, > same for me, +1 for version 3.5 :) > Thank you for everybody's hard work, PDT is really getting better and better! > :) > > Thierry. > > Date: Fri, 27 Feb 2015 20:30:44 +0100 > From: micha...@zend.com > To: pdt-dev@eclipse.org > Subject: Re: [pdt-dev] Rename 3.4.1 to 3.5 > > Hi,+1 for version 3.5. Almost 500 PHP SR2 downloads till now;) Thanks for all > your work! > Michal > On Fri, Feb 27, 2015 at 8:13 PM, Kaloyan Raev wrote: > Hi Dawid, > Yes, of course. We should have 3.5 for Mars. You should announce this on the > cross-project-issues > mailing list as changed version in PDT participation in Mars. > Greetings,Kaloyan > On Fri, Feb 27, 2015 at 9:03 PM, Dawid Pakuła wrote: > Hi team! > > > > Due recent and upcoming changes in PDT debugger like [1], and other that for > example will > require us to use never DLTK ([2],[3]) I think we should abandon 3.4.1 and > deliver 3.5 > to eclipse mars. > > > > What you think? > > > > BTW: 3.4 is released ;) > > > > [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=459507 > > [2] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=457621 > > [3] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=438087 > > > > -- > > Dawid Pakuła > > +48 795 996 064 > > > > > > ___ > > 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 ___ 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
Re: [pdt-dev] Formalize commit / patch description patterns
Hi, I upgraded our contribution guide: https://wiki.eclipse.org/PDT/Contributing#Patch_naming_conventions -- Dawid Pakuła +48 795 996 064 On 20 Feb 2015 at 00:10:38, thierry blind (thierrybl...@msn.com) wrote: > +1 for "[WIP] Bug 1234 - Description" :) > > From: kaloya...@zend.com > Date: Thu, 19 Feb 2015 08:04:10 +0200 > To: pdt-dev@eclipse.org > Subject: Re: [pdt-dev] Formalize commit / patch description patterns > > +1 I like conventions. I don't have any preference for the WIP. > Kaloyan > On Thu, Feb 19, 2015 at 12:29 AM, Michał Niewrzał wrote: > Hello,+1 from me:) I prefer version:[WIP] Bug 1234 - Description but it is > only matter > of taste ;) > Michal > On Wed, Feb 18, 2015 at 9:10 PM, Dawid Pakuła wrote: > Hi, > I have two proposition for today. > 1. Since around year, most (if not all) commit messages follow this pattern > at first line: > Bug 12345 / No bug - Short bug description > I propose to make it as a standard and put information about this into our > Contribution > Guide [1] > 2. As you probably noticed, since couple days (weeks) gerrit automatically > add patch > and commit links to our bugs. > To avoid confusion and questions like "Is this ready to review / IP process?" > i have a proposition > to add "[WIP]" prefix before bug description: > Bug 1234 - [WIP] Description > Alternative could be:[WIP] Bug 1234 - Description > Platform UI standard. But this probably also disable gerrit bot until message > update > (I'm not sure). > What do you think / prefer? > [1] - https://wiki.eclipse.org/PDT/Contributing > --Dawid Pakuła +48 795 996 064 > ___ > > 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 ___ 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
Re: [pdt-dev] Rename 3.4.1 to 3.5
Hi again, I updated versions to 3.5.0. Direct nightly p2 url: http://download.eclipse.org/tools/pdt/updates/3.5-nightly Universal nightly p2 url: http://download.eclipse.org/tools/pdt/updates/latest-nightly -- Dawid Pakuła +48 795 996 064 On 1 Mar 2015 at 13:26:51, Dawid Pakuła (zu...@w3des.net) wrote: > Hi, > > I updated release record [1] and sent announcement to cross-project list [2]. > > I also sent request to rename version on bugzilla [3] > > [1] - https://projects.eclipse.org/projects/tools.pdt/releases/3.5 > [2] - > https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg11603.html > [3] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=461146 > > -- > Dawid Pakuła > +48 795 996 064 > > > On 28 Feb 2015 at 10:58:01, thierry blind (thierrybl...@msn.com) wrote: > > Hi, > > same for me, +1 for version 3.5 :) > > Thank you for everybody's hard work, PDT is really getting better and > > better! :) > > > > Thierry. > > > > Date: Fri, 27 Feb 2015 20:30:44 +0100 > > From: micha...@zend.com > > To: pdt-dev@eclipse.org > > Subject: Re: [pdt-dev] Rename 3.4.1 to 3.5 > > > > Hi,+1 for version 3.5. Almost 500 PHP SR2 downloads till now;) Thanks for > > all your work! > > Michal > > On Fri, Feb 27, 2015 at 8:13 PM, Kaloyan Raev wrote: > > Hi Dawid, > > Yes, of course. We should have 3.5 for Mars. You should announce this on > > the cross-project-issues > > mailing list as changed version in PDT participation in Mars. > > Greetings,Kaloyan > > On Fri, Feb 27, 2015 at 9:03 PM, Dawid Pakuła wrote: > > Hi team! > > > > > > > > Due recent and upcoming changes in PDT debugger like [1], and other that > > for example > will > > require us to use never DLTK ([2],[3]) I think we should abandon 3.4.1 and > > deliver 3.5 > > to eclipse mars. > > > > > > > > What you think? > > > > > > > > BTW: 3.4 is released ;) > > > > > > > > [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=459507 > > > > [2] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=457621 > > > > [3] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=438087 > > > > > > > > -- > > > > Dawid Pakuła > > > > +48 795 996 064 > > > > > > > > > > > > ___ > > > > 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 > > ___ 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
Re: [pdt-dev] Google Summer of Code 2015
Hi, +1 from me. Thoughts? PDT.incubator reactivation? Composer became the same thing for php, like bower for JS. And bower toolkit will be part of JSDT since mars (CQ still pending) ;) Gossi, see also official eclipse GSoC2015 wiki page: https://wiki.eclipse.org/Google_Summer_of_Code_2015 -- Dawid Pakuła +48 795 996 064 On 12 Mar 2015 at 15:48:48, Thomas Gossmann (ecli...@gos.si) wrote: > Hello, > > I have an idea for a GSOC project, which I already posted on the PEX > Group, so some of you might already know about this. I would like to > contribute the Composer Plugin to PDT. As the request on PEX looks still > pending, as PEX contributors need to agree, take it with that grain of salt. > > All Information about this idea: > https://groups.google.com/forum/#!topic/pdt-extensions-platform/Bnh8ugkp0wc > > I'm posting this here already because I think this is whole process is > in a hurry. > > P.S. What would be the next steps (given this idea gets an ok) > > gossi > > Am 19.02.15 um 17:34 schrieb Dawid Pakuła: > > Hi, > > > > Here is an official eclipse wiki page for GSoC 2015 [1] and announcement > > from eclipse > soc-dev mailing list [2] > > > > Everyone are welcome to provide ideas [3]. > > > > [1] - https://wiki.eclipse.org/Google_Summer_of_Code_2015 > > [2] - https://dev.eclipse.org/mhonarc/lists/soc-dev/msg00493.html > > [3] - https://wiki.eclipse.org/Google_Summer_of_Code_2015_Ideas > > > > > > -- > > Dawid Pakuła > > +48 795 996 064 > > > > > > ___ > > 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
Re: [pdt-dev] Removing old PHP versions
Hi, I thinking about this since half year :D In mars we could drop 4.0. 5.0-5.2 it’s still very popular [1] so maybe later. [1] - http://w3techs.com/technologies/details/pl-php/5/all -- Dawid Pakuła +48 795 996 064 On 21 Mar 2015 at 17:30:22, Michał Niewrzał (micha...@zend.com) wrote: > Hi All, > I want to start small discussion:) Few months ago (about 5) in Zend Studio > we "hide" oldest versions of PHP: PHP 4 and PHP 5.1/5.2. Since then no one > ask about it:) I think we can think about removing these versions for PDT > (maybe for Mars?). As I said in Studio we just remove it from list and for > PDT removing it from code will be more complex task, but I think it will > help simplify and clarify some things. If someone will still need removed > version then previous versions of PDT are always available. > > This year will bring PHP7 and in my opinion supporting 7 versions of > parser/lexer is not necessary:) What do you think about it? > > Michal > ___ > 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
Re: [pdt-dev] Recent problems with build
Hi, it’s because on your pc tests run in different order. I prepared patch with simple fix: https://git.eclipse.org/r/#/c/44763/ -- Dawid Pakuła +48 795 996 064 On 27 Mar 2015 at 13:32:22, Michał Niewrzał (micha...@zend.com) wrote: > Hi, > Recently I noticed that my local build is failing on tests. Tests started > with maven and from Eclipse ends with failure. Because our builds on Hudson > are working correctly I started to search problem on my machine, but for > now without success. Failing tests: > > assist[workspace/codeassist/php55/testMagicMethod7.pdtt](org.eclipse.php.core.tests.codeassist.CodeAssistTests): > > > assist[workspace/codeassist/php55/testMagicMethod7.pdtt](org.eclipse.php.core.tests.codeassist.CodeAssistTests): > > > I tried to reproduce test problem in PDT manually, but everything is > working ok. Problem is only visible during build. Any idea what is going > on?:) > > Thanks, > Michal > ___ > 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
Re: [pdt-dev] Recent problems with build
Hi, @thierry, on inference tests, or also in another? Can you open a bug? I have couple ideas where can be a problem, but I'll check when (if) I find windows workstation :P -- Dawid Pakuła +48 795 996 064 On 27 Mar 2015 at 18:03:29, thierry blind (thierrybl...@msn.com) wrote: > That's a different problem, but in my case junit tests often fail on Windows > machines > because files cannot be deleted : > org.eclipse.core.internal.resources.ResourceException: Problems encountered > while deleting resources. at > org.eclipse.core.internal.resources.Resource.delete(Resource.java:816) > at org.eclipse.core.internal.resources.Project.delete(Project.java:344) at > org.eclipse.php.core.tests.typeinference.TypeInferenceTests.tearDownSuite(TypeInferenceTests.java:109) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > > at java.lang.reflect.Method.invoke(Method.java:597) at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > > at > org.eclipse.php.core.tests.runner.PDTTList$AfterStatement.evaluate(PDTTList.java:299) > > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at > org.junit.runners.Suite.runChild(Suite.java:127) > at org.junit.runners.Suite.runChild(Suite.java:26) at > org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at > org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at > org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) > > at > org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > > at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > > at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > > at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > > at > org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:62) > > at > org.eclipse.pde.internal.junit.runtime.PlatformUITestHarness$1.run(PlatformUITestHarness.java:47) > > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at > org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4147) at > org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3764) at > org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > > at > org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at > org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > > at > org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) at > org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at > org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at > org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > > at > org.eclipse.pde.internal.junit.runtime.NonUIThreadTestApplication.runApp(NonUIThreadTestApplication.java:54) > > at > org.eclipse.pde.internal.junit.runtime.UITestApplication.runApp(UITestApplication.java:47) > > at > org.eclipse.pde.internal.junit.runtime.NonUIThreadTestApplication.start(NonUIThreadTestApplication.java:48) > > at > org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > > at > org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > > at > org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > > at > org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) > at > org.eclipse.cor
Re: [pdt-dev] Extensions section on website
Hi, I think it would be better to start collecting extensions via xml/json file(s), like we started on wiki page [1]. After that, prepare web interface for list will be very easy to implement (xslt, php, js) and more powerful than these three direct links (marketplace “install” buttons). We also will be able to reuse collection for bug 433676 [2] [1] - https://wiki.eclipse.org/PDT/Extensions [2] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=433676 -- Dawid Pakuła +48 795 996 064 On 30 Mar 2015 at 22:42:06, Kaloyan Raev (kaloya...@zend.com) wrote: > Hi, > > I opened bug http://eclip.se/463423 to propose a change to the PDT web > site. > I'd like to hear your opinion. > > Thanks, > Kaloyan > ___ > 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
Re: [pdt-dev] Extensions section on website
Hi, Once I finish refactoring support for doctrine/symfony plugins, this is my next item on todo list ;) Anyway, if other commiters agree we off course can add these links to our website, I just have to ask pmc/emo how look foundation policy in such case. -- Dawid Pakuła +48 795 996 064 On 31 Mar 2015 at 11:23:59, Kaloyan Raev (kaloya...@zend.com) wrote: > Hi, > > I agree that having the wiki page completed is the better approach, but the > effort did not take up when I started it some time ago. It still requires a > significant effort to complete it and make it meaningful. > > The simple change I am proposing to the web site is a low-effort low > hanging fruit that promotes available PDT extensions. I don't mind > replacing it with a link to the wiki page once it's ready. > > Kaloyan > > On Tue, Mar 31, 2015 at 11:52 AM, Dawid Pakuła wrote: > > > Hi, > > > > I think it would be better to start collecting extensions via xml/json > > file(s), like we started on wiki page [1]. > > > > After that, prepare web interface for list will be very easy to implement > > (xslt, php, js) and more powerful than these three direct links > > (marketplace “install” buttons). We also will be able to reuse collection > > for bug 433676 [2] > > > > [1] - https://wiki.eclipse.org/PDT/Extensions > > [2] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=433676 > > > > -- > > Dawid Pakuła > > +48 795 996 064 > > > > On 30 Mar 2015 at 22:42:06, Kaloyan Raev (kaloya...@zend.com) wrote: > > > Hi, > > > > > > I opened bug http://eclip.se/463423 to propose a change to the PDT web > > > site. > > > I'd like to hear your opinion. > > > > > > Thanks, > > > Kaloyan > > > ___ > > > 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
Re: [pdt-dev] Extensions section on website
Hi, Looks much better. Michal, Thierry what you think? -- Dawid Pakuła +48 795 996 064 On 1 Apr 2015 at 14:13:43, Kaloyan Raev (kaloya...@zend.com) wrote: > I meant exactly "seemlessly"... But perhaps, it would be best to drop the > word completely. > > Dawid, what's your opinion on the latest screenshot I've sent? > > On Wed, Apr 1, 2015 at 3:09 PM, Jacek Pospychała > > wrote: > > > oh ok now even better. I see typo "seemlessly" shouldn't be seamlessly? > > unless it's a tribute to http://en.wikipedia.org/wiki/Seemless :-) > > > > On Wed, Apr 1, 2015 at 12:30 PM, Kaloyan Raev wrote: > > > >> Hi again, > >> > >> Attached is another update. Looks good? > >> > >> Kaloyan > >> > >> On Wed, Apr 1, 2015 at 11:39 AM, Kaloyan Raev wrote: > >> > >>> Hi Jacek, > >>> > >>> The Zend bullets are not ready at all. I just wanted to know your > >>> opinion on the first bullet. I will send another update soon. > >>> > >>> Kaloyan > >>> > >>> On Wed, Apr 1, 2015 at 11:34 AM, Jacek Pospychała < > >>> jacek.pospych...@gmail.com> wrote: > >>> > >>>> it's imho better, more informative now. > >>>> On aesthetics side, the white space in Zend bullets looks a bit > >>>> awkward. Maybe put some some text (at least product names, because > >>>> they're > >>>> gone now), or link (from screenshot I can't see if image is clickable)? > >>>> or > >>>> maybe resize images? > >>>> > >>>> > >>>> On Tue, Mar 31, 2015 at 4:11 PM, Kaloyan Raev > >>>> wrote: > >>>> > >>>>> How about something like on the attached screenshot? > >>>>> Each of the listed features is a link to the corresponding section on > >>>>> the http://p2-dev.pdt-extensions.org/ web site. > >>>>> > >>>>> Kaloyan > >>>>> > >>>>> On Tue, Mar 31, 2015 at 3:45 PM, Jacek Pospychała < > >>>>> jacek.pospych...@gmail.com> wrote: > >>>>> > >>>>>> I'd go with list of all 30 features and make the list look simple. > >>>>>> That way it'd be easy to add new ones and remove outdated. > >>>>>> > >>>>>> On Tue, Mar 31, 2015 at 2:26 PM, Kaloyan Raev > >>>>>> wrote: > >>>>>> > >>>>>>> Hi Jacek, > >>>>>>> > >>>>>>> I took the name and slogan from the web site: > >>>>>>> http://p2-dev.pdt-extensions.org/ > >>>>>>> I am not a marketing guru and I am completely open for changes :-) > >>>>>>> > >>>>>>> Which ones of the ~30 plugins of the "PDT Extensions group" do you > >>>>>>> want to emphasize on? > >>>>>>> > >>>>>>> Kaloyan > >>>>>>> > >>>>>>> On Tue, Mar 31, 2015 at 2:21 PM, Jacek Pospychała < > >>>>>>> jacek.pospych...@gmail.com> wrote: > >>>>>>> > >>>>>>>> this is super nice. > >>>>>>>> although having "Extensions group" in "Extensions" section is not > >>>>>>>> very informative. Shouldn't there be a list all specific features > >>>>>>>> from PDT > >>>>>>>> extensions group, like "PHP Symfony", "PHP Maven", etc etc? > >>>>>>>> > >>>>>>>> On Tue, Mar 31, 2015 at 12:01 PM, Kaloyan Raev > >>>>>>>> wrote: > >>>>>>>> > >>>>>>>>> Sure, ask the PMC/EMO. As far as I can recall the rules, it is > >>>>>>>>> about vendor neutrality. Promoting of open source or proprietary > >>>>>>>>> extensions > >>>>>>>>> is fine as long as it is allowed to everyone to participate. > >>>>>>>>> > >>>>>>>>> Kaloyan > >>>>>>>>> > >>>>>>>>> On Tue, Mar 31, 2015 at 12:48 PM, Dawid Pakuła > >>>>>>>>> wrote: >
