Re: [pdt-dev] Fwd: Providing an All-In-One PDT Eclipse distribution
Hi all, i'm unexpectedly working on larger project right now which will last until the end of the year, so unfortunately the all-in-one package i've been working on has been discontinued for now. However, if what i've come up with so far helps with the EPP package, feel free to fork it: https://github.com/pulse00/lennard-php regards -robert On Tue, Jul 30, 2013 at 3:15 PM, Kaloyan Raev kaloya...@zend.com wrote: Jacek, It's great to hear that the PHP package will be back. I'd like to help you with this. Greetings, Kaloyan On Mon, Jul 29, 2013 at 9:41 PM, Jacek Pospychała jacek.pospych...@gmail.com wrote: I was waiting with this until the end of Kepler release rush and it looks like the time has come. There's a bug open against EPP with initial PHP package contribution to kickstart things: https://bugs.eclipse.org/bugs/show_bug.cgi?id=413941 Jacek On Thu, Jul 25, 2013 at 6:51 PM, Mike Milinkovich mike.milinkov...@eclipse.org wrote: On 03/06/2013 9:48 AM, Kaloyan Raev wrote: Hi Robert, Having an Eclipse-based PHP all-in-one package is a really nice initiative. However, I agree with Jacek, that if it is an Eclipse.org EPP package, it would have greater chance to be adopted by users. The Eclipse.org download page is a really famous one. I am curious about where this conversation went? ___ 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 -- phone +43 676 64 57 240 Zieglergasse 65/6 1070 Vienna Austria twitter.com/pulse00 github.com/pulse00 ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] Fwd: Providing an All-In-One PDT Eclipse distribution
fyi: I've released the first alpha version of the PHP build: https://github.com/pulse00/lennard-php I'll try to find some testers for Windows and Linux, as i'm developing on OSX and don't have the resources to fully test on all platforms. Any feedback on the featureset of the build would be great. regard -robert On Wed, May 15, 2013 at 7:33 PM, Mike Milinkovich mike.milinkov...@eclipse.org wrote: As far as I know, it was discontinued because the company which was funding the work decided that it was not where they wanted to put their resources. I've been hoping ever since that someone from the community would step forward to resurrect it. Mike Milinkovich mike.milinkov...@eclipse.org +1.613.220.3223 *From: *Seva Lapsha *Sent: *Wednesday, May 15, 2013 3:27 PM *To: *PDT Developers *Reply To: *PDT Developers *Subject: *Re: [pdt-dev] Fwd: Providing an All-In-One PDT Eclipse distribution Yes, I was wondering why it was discontinued... On Wed, May 15, 2013 at 5:11 AM, Mike Milinkovich mike.milinkov...@eclipse.org wrote: As a historical note, once upon a time, there was a very successful PHP package on the download page. It would be great to see one again. Mike Milinkovich mike.milinkov...@eclipse.org +1.613.220.3223 *From: *Jacek Pospychała *Sent: *Wednesday, May 15, 2013 11:08 AM *To: *PDT Developers *Reply To: *PDT Developers *Subject: *[pdt-dev] Fwd: Providing an All-In-One PDT Eclipse distribution meh... I accidentally only sent to pdt-eg mailing list. -- Forwarded message -- From: Jacek Pospychała jacek.pospych...@gmail.com Date: Wed, May 15, 2013 at 11:07 AM Subject: Re: Providing an All-In-One PDT Eclipse distribution To: pdt-extensions-platf...@googlegroups.com hi Robert, it's a great initiative and I'd love to see you succeed! If there's anything specific from PDT side that you're missing please don't hesitate to bug me about it. I'll do anything I can. From Eclipse Foundation side of things, I always wanted to see Eclipse PHP package listed on http://www.eclipse.org/downloads. IMHO it has great visibility, downloads rates for some packages are just enormous (e.g. magnitude higher than top marketplace packages) and it's sad that there's no package for PHP devs. Now that you're looking into packaging, have you considered the EPP initiative? It has it's own constraints, but maybe would be interesting to you. Jacek On Wed, May 15, 2013 at 10:44 AM, Robert Gründler r.gruend...@gmail.com wrote: Hi all, after over 2 years of maintaining PDT related plugins, i've come to the following conclusions: A lot of people have a hard time setting up an eclipse instance to suite their needs for PHP development - with the multitude of all the existing plugins available. More and more people move over to PHPStorm The migration to PHPStorm imho has 2 main reasons: Out-Of-The-Box experience: simply download the thing and start working Better performance I think both issues can be addressed by providing a plain Eclipse distribution targeting especially the needs of PHP / Web developers. By releasing a custom distribution, we can for example provide a tweaked eclipse.ini with optimized JVM settings. Also, a custom distribution could pre-configure other features to improve the performance / user experience, for example by disabling useless validators etc. I've therefore started working on a tycho-built eclipse distro based on the following features (so far): - DLTK 5.0 - PDT 3.2 - PDT Extensions Core - Composer Plugin - PHP Tool Integration - MakeGood - Json Editor - Yaml Editor Another reason why a custom distribution would be an advantage is that we don't have to rely on patches being applied to the Eclipse runtime, like this one here, which would be a rather great improvement for anyone working with webapplications: https://bugs.eclipse.org/bugs/show_bug.cgi?id=351303 Here's what the distro could provide on an Eclipse-Runtime Level: - Register an eclipse:// URL protocol, so Stack-Trace links in the browser could be opened directly in eclipse (like Sublimetext or Textmate work on osx) - Provide a Listener-Extension for the SWT.OpenDocument event, so plugins can import existing projects by drag drop onto Eclipse The product i'm working on will be fully open-source and free of charge, however i'm also thinking of ways to fund the development of new features to PDT Core / PDT-Extensions or any other related plugin. My main ideas are: - Go down the crowd-funding route, for example like py-dev has been doing: http://www.indiegogo.com/projects/pydev-and-liclipse-for-a-fast-sexy-and-dark-eclipse - Find sponsors for new features, similar to what travis-ci does: https://travis-ci.org/ Any feedback greatly appreciated. regards -robert -- You received this message because you
Re: [pdt-dev] Fwd: Providing an All-In-One PDT Eclipse distribution
Hi all, that's odd. I've actually made the repository public before writing the email, and it suddenly was private again... Anyway, it's public now again, i've tested it while being logged out from github: https://github.com/pulse00/lennard-php regards -robert On Thu, May 30, 2013 at 3:24 PM, Mike Milinkovich mike.milinkov...@eclipse.org wrote: Is anyone else getting a 404 on that link? Mike Milinkovich +1.613.220.3223 mike.milinkov...@eclipse.org On 2013-05-30, at 6:43 AM, Robert Gründler r.gruend...@gmail.com wrote: fyi: I've released the first alpha version of the PHP build: https://github.com/pulse00/lennard-php I'll try to find some testers for Windows and Linux, as i'm developing on OSX and don't have the resources to fully test on all platforms. Any feedback on the featureset of the build would be great. regard -robert On Wed, May 15, 2013 at 7:33 PM, Mike Milinkovich mike.milinkov...@eclipse.org wrote: As far as I know, it was discontinued because the company which was funding the work decided that it was not where they wanted to put their resources. I've been hoping ever since that someone from the community would step forward to resurrect it. Mike Milinkovich mike.milinkov...@eclipse.org +1.613.220.3223 *From: *Seva Lapsha *Sent: *Wednesday, May 15, 2013 3:27 PM *To: *PDT Developers *Reply To: *PDT Developers *Subject: *Re: [pdt-dev] Fwd: Providing an All-In-One PDT Eclipse distribution Yes, I was wondering why it was discontinued... On Wed, May 15, 2013 at 5:11 AM, Mike Milinkovich mike.milinkov...@eclipse.org wrote: As a historical note, once upon a time, there was a very successful PHP package on the download page. It would be great to see one again. Mike Milinkovich mike.milinkov...@eclipse.org +1.613.220.3223 *From: *Jacek Pospychała *Sent: *Wednesday, May 15, 2013 11:08 AM *To: *PDT Developers *Reply To: *PDT Developers *Subject: *[pdt-dev] Fwd: Providing an All-In-One PDT Eclipse distribution meh... I accidentally only sent to pdt-eg mailing list. -- Forwarded message -- From: Jacek Pospychała jacek.pospych...@gmail.com Date: Wed, May 15, 2013 at 11:07 AM Subject: Re: Providing an All-In-One PDT Eclipse distribution To: pdt-extensions-platf...@googlegroups.com hi Robert, it's a great initiative and I'd love to see you succeed! If there's anything specific from PDT side that you're missing please don't hesitate to bug me about it. I'll do anything I can. From Eclipse Foundation side of things, I always wanted to see Eclipse PHP package listed on http://www.eclipse.org/downloads. IMHO it has great visibility, downloads rates for some packages are just enormous (e.g. magnitude higher than top marketplace packages) and it's sad that there's no package for PHP devs. Now that you're looking into packaging, have you considered the EPP initiative? It has it's own constraints, but maybe would be interesting to you. Jacek On Wed, May 15, 2013 at 10:44 AM, Robert Gründler r.gruend...@gmail.com wrote: Hi all, after over 2 years of maintaining PDT related plugins, i've come to the following conclusions: A lot of people have a hard time setting up an eclipse instance to suite their needs for PHP development - with the multitude of all the existing plugins available. More and more people move over to PHPStorm The migration to PHPStorm imho has 2 main reasons: Out-Of-The-Box experience: simply download the thing and start working Better performance I think both issues can be addressed by providing a plain Eclipse distribution targeting especially the needs of PHP / Web developers. By releasing a custom distribution, we can for example provide a tweaked eclipse.ini with optimized JVM settings. Also, a custom distribution could pre-configure other features to improve the performance / user experience, for example by disabling useless validators etc. I've therefore started working on a tycho-built eclipse distro based on the following features (so far): - DLTK 5.0 - PDT 3.2 - PDT Extensions Core - Composer Plugin - PHP Tool Integration - MakeGood - Json Editor - Yaml Editor Another reason why a custom distribution would be an advantage is that we don't have to rely on patches being applied to the Eclipse runtime, like this one here, which would be a rather great improvement for anyone working with webapplications: https://bugs.eclipse.org/bugs/show_bug.cgi?id=351303 Here's what the distro could provide on an Eclipse-Runtime Level: - Register an eclipse:// URL protocol, so Stack-Trace links in the browser could be opened directly in eclipse (like Sublimetext or Textmate work on osx) - Provide a Listener-Extension for the SWT.OpenDocument event, so plugins can import existing projects by drag drop onto Eclipse The product i'm working on will be fully open-source
Re: [pdt-dev] Code formatter contribution for PDT
one more question: Will the new formatter be released with Kepler?
regards
-robert
On Wed, May 15, 2013 at 8:43 AM, Robert Gründler r.gruend...@gmail.comwrote:
Cool, thanks a lot for the info.
The formatter has one major advantage over the one written by atlanto: it
supports region based formatting.
I've noticed it has the same issue like the pdt-eg formatter, it doesn't
preserve indentation for fluent interface calls, e.g:
$this
-getMockBuilder('SomeClass')
-disableOriginalConstructor()
-getMock()
;
will be formatted to:
$this-getMockBuilder('SomeClass')
-disableOriginalConstructor()
-getMock();
But that's minor i guess ;)
-robert
On Mon, May 13, 2013 at 10:18 PM, Seva Lapsha seva.lap...@gmail.comwrote:
That's great news!
On Mon, May 13, 2013 at 3:43 PM, Jacek Pospychała
jacek.pospych...@gmail.com wrote:
hi,
I'd like to draw your attention to this bugzilla:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=407768
There's a new code formatter contribution for PDT. It's now scheduled
for IP review and after that is highly likely to be included into PDT.
Early adopters and PDT extenders, please don't hesitate to give it a
try and share your feedback!
thanks
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
--
phone +43 676 64 57 240
Zieglergasse 65/6
1070 Vienna
Austria
twitter.com/pulse00
github.com/pulse00
--
phone +43 676 64 57 240
Zieglergasse 65/6
1070 Vienna
Austria
twitter.com/pulse00
github.com/pulse00
___
pdt-dev mailing list
pdt-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] Code formatter contribution for PDT
great, thanks for the info.
On Mon, May 20, 2013 at 11:22 AM, Jacek Pospychała
jacek.pospych...@gmail.com wrote:
yes.
It already went through IP review and was added to the nightly builds,
so there's nothing to stop it from Kepler.
On Mon, May 20, 2013 at 11:13 AM, Robert Gründler r.gruend...@gmail.com
wrote:
one more question: Will the new formatter be released with Kepler?
regards
-robert
On Wed, May 15, 2013 at 8:43 AM, Robert Gründler r.gruend...@gmail.com
wrote:
Cool, thanks a lot for the info.
The formatter has one major advantage over the one written by atlanto:
it
supports region based formatting.
I've noticed it has the same issue like the pdt-eg formatter, it doesn't
preserve indentation for fluent interface calls, e.g:
$this
-getMockBuilder('SomeClass')
-disableOriginalConstructor()
-getMock()
;
will be formatted to:
$this-getMockBuilder('SomeClass')
-disableOriginalConstructor()
-getMock();
But that's minor i guess ;)
-robert
On Mon, May 13, 2013 at 10:18 PM, Seva Lapsha seva.lap...@gmail.com
wrote:
That's great news!
On Mon, May 13, 2013 at 3:43 PM, Jacek Pospychała
jacek.pospych...@gmail.com wrote:
hi,
I'd like to draw your attention to this bugzilla:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=407768
There's a new code formatter contribution for PDT. It's now scheduled
for IP review and after that is highly likely to be included into PDT.
Early adopters and PDT extenders, please don't hesitate to give it a
try and share your feedback!
thanks
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
--
phone +43 676 64 57 240
Zieglergasse 65/6
1070 Vienna
Austria
twitter.com/pulse00
github.com/pulse00
--
phone +43 676 64 57 240
Zieglergasse 65/6
1070 Vienna
Austria
twitter.com/pulse00
github.com/pulse00
___
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
--
phone +43 676 64 57 240
Zieglergasse 65/6
1070 Vienna
Austria
twitter.com/pulse00
github.com/pulse00
___
pdt-dev mailing list
pdt-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] Code formatter contribution for PDT
Cool, thanks a lot for the info.
The formatter has one major advantage over the one written by atlanto: it
supports region based formatting.
I've noticed it has the same issue like the pdt-eg formatter, it doesn't
preserve indentation for fluent interface calls, e.g:
$this
-getMockBuilder('SomeClass')
-disableOriginalConstructor()
-getMock()
;
will be formatted to:
$this-getMockBuilder('SomeClass')
-disableOriginalConstructor()
-getMock();
But that's minor i guess ;)
-robert
On Mon, May 13, 2013 at 10:18 PM, Seva Lapsha seva.lap...@gmail.com wrote:
That's great news!
On Mon, May 13, 2013 at 3:43 PM, Jacek Pospychała
jacek.pospych...@gmail.com wrote:
hi,
I'd like to draw your attention to this bugzilla:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=407768
There's a new code formatter contribution for PDT. It's now scheduled
for IP review and after that is highly likely to be included into PDT.
Early adopters and PDT extenders, please don't hesitate to give it a
try and share your feedback!
thanks
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
--
phone +43 676 64 57 240
Zieglergasse 65/6
1070 Vienna
Austria
twitter.com/pulse00
github.com/pulse00
___
pdt-dev mailing list
pdt-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/pdt-dev
[pdt-dev] Providing an All-In-One PDT Eclipse distribution
Hi all, after over 2 years of maintaining PDT related plugins, i've come to the following conclusions: 1. A lot of people have a hard time setting up an eclipse instance to suite their needs for PHP development - with the multitude of all the existing plugins available. 2. More and more people move over to PHPStorm The migration to PHPStorm imho has 2 main reasons: 1. Out-Of-The-Box experience: simply download the thing and start working 2. Better performance I think both issues can be addressed by providing a plain Eclipse distribution targeting especially the needs of PHP / Web developers. By releasing a custom distribution, we can for example provide a tweaked eclipse.ini with optimized JVM settings. Also, a custom distribution could pre-configure other features to improve the performance / user experience, for example by disabling useless validators etc. I've therefore started working on a tycho-built eclipse distro based on the following features (so far): - DLTK 5.0 - PDT 3.2 - PDT Extensions Core https://github.com/pdt-eg/Core-Plugin - Composer Plugin https://github.com/pulse00/Composer-Eclipse-Plugin - PHP Tool Integration https://github.com/PHPsrc/PHP-Tool-Integration - MakeGood https://github.com/piece/makegood - Json Editor https://github.com/pulse00/Json-Eclipse-Plugin - Yaml Editor https://github.com/oyse/yedit Another reason why a custom distribution would be an advantage is that we don't have to rely on patches being applied to the Eclipse runtime, like this one here, which would be a rather great improvement for anyone working with webapplications: https://bugs.eclipse.org/bugs/show_bug.cgi?id=351303 Here's what the distro could provide on an Eclipse-Runtime Level: - Register an *eclipse://* URL protocol, so Stack-Trace links in the browser could be opened directly in eclipse (like Sublimetext or Textmate work on osx) - Provide a Listener-Extension for the *SWT.OpenDocument* event, so plugins can import existing projects by drag drop onto Eclipse The product i'm working on will be fully open-source and free of charge, however i'm also thinking of ways to fund the development of new features to PDT Core / PDT-Extensions or any other related plugin. My main ideas are: - Go down the crowd-funding route, for example like py-dev has been doing: http://www.indiegogo.com/projects/pydev-and-liclipse-for-a-fast-sexy-and-dark-eclipse - Find sponsors for new features, similar to what travis-ci does: https://travis-ci.org/ Any feedback greatly appreciated. regards -robert ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] Providing an All-In-One PDT Eclipse distribution
On Wed, May 15, 2013 at 11:07 AM, Jacek Pospychała jacek.pospych...@gmail.com wrote: it's a great initiative and I'd love to see you succeed! If there's anything specific from PDT side that you're missing please don't hesitate to bug me about it. I'll do anything I can. thanks. so far i didn't run into any major issues. From Eclipse Foundation side of things, I always wanted to see Eclipse PHP package listed on http://www.eclipse.org/downloads. IMHO it has great visibility, downloads rates for some packages are just enormous (e.g. magnitude higher than top marketplace packages) and it's sad that there's no package for PHP devs. yep, it would be the goal to show up there. As Mike mentioned, there has been a package available, but it has been removed a couple of years ago. As far as i remember the maintainer said it would be too much work to keep maintaining it. From what i've seen playing around with my existing tycho build, it shouldn't be that much work to maintain it though. Now that you're looking into packaging, have you considered the EPP initiative? It has it's own constraints, but maybe would be interesting to you. Nope, thanks for the hint. regards -robert ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] Customizing the PDT for Jaggery
Hi Rajeeva, i've done something similar for Twig [1] some time ago. You need to implement a custom Jflex Lexer/Parser for your language (based on the one from PDT) and then contribute a DocumentModel [2]. Afaik there is no cleaner way to write an HTML editor with a nested templating language based on the existing WTP HTML editor. Hope this helps, -robert [1] https://github.com/pulse00/Twig-Eclipse-Plugin/tree/master/com.dubture.twig.core/Resources/parserTools [2] https://github.com/pulse00/Twig-Eclipse-Plugin/tree/master/com.dubture.twig.core/src/com/dubture/twig/core/documentModel On Mon, Apr 22, 2013 at 12:37 PM, Jacek Pospychała jacek.pospych...@gmail.com wrote: hi Rajeeva, PDT editor builds heavily on top of structured source editing API (SSE, found in org.eclipse.wst.sse.ui plugin), which in turn builds on top of Eclipse Text editor API. HTML editor (in org.eclipse.wst.html.ui plugin) and Javascript editor (in org.eclipse.jsdt.ui plugin) are also built on top of SSE API so that in similar to PDT way, they implement similar mechanisms for HTML and JS languages. SSE uses document partitioning, so that each partition of edited file can be handled by different plugins providing specific highlighting/formatting/etc. for different languages That's how it works from fairly high level. I'd recommend you look up more about how SSE works. Jacek On Mon, Apr 22, 2013 at 11:46 AM, Rajeeva Uthayasangar u3ra...@gmail.com wrote: Hi All, I'm developing a Eclipse IDE for Jaggery [1]. So I'm trying to customize the PDT to my purpose. In PDT how the syntax coloring id done for keywords, comments etc. I need to have support of HTML and Javascript in my Jaggery editor. So if some one explains how the HTML and Javascript are integrated with PHP Editor it would help me lot? [1]. http://jaggeryjs.org/ Thanks. Rajeeva. ___ 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 -- phone +43 676 64 57 240 Zieglergasse 65/6 1070 Vienna Austria twitter.com/pulse00 github.com/pulse00 ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
[pdt-dev] isContainerEntry() is undefined for the type IBuildPathEntry
Hi all, after updating to the latest PDT and DLTK versions i'm getting the above error see [1] and [2]. Has anything changed in the project setup lately? regards -robert [1] https://github.com/eclipse/pdt/blob/master/plugins/org.eclipse.php.core/src/org/eclipse/php/internal/core/language/LanguageModelInitializer.java#L181 [2] https://github.com/eclipse/dltk.core/blob/master/core/plugins/org.eclipse.dltk.core/model/org/eclipse/dltk/core/IBuildpathEntry.java ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] isContainerEntry() is undefined for the type IBuildPathEntry
sorry, i should have looked at the DLTK commits first: https://github.com/eclipse/dltk.core/commit/254122bcb1df65eaa17f05f3b6e9eb447ef7b0ed I guess the DLTK changes have not been adopted yet in PDT. regards -robert On Tue, Feb 12, 2013 at 8:32 AM, Robert Gründler r.gruend...@gmail.comwrote: Hi all, after updating to the latest PDT and DLTK versions i'm getting the above error see [1] and [2]. Has anything changed in the project setup lately? regards -robert [1] https://github.com/eclipse/pdt/blob/master/plugins/org.eclipse.php.core/src/org/eclipse/php/internal/core/language/LanguageModelInitializer.java#L181 [2] https://github.com/eclipse/dltk.core/blob/master/core/plugins/org.eclipse.dltk.core/model/org/eclipse/dltk/core/IBuildpathEntry.java ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] Separate builds for Kepler and Juno
thanks Alexey, i got it working now. fyi: I don't know if it's the changes in Kepler / DLTK or PDT itself, but PDT seems a lot faster running the latest versions under kepler. Great job! regards -robert On Thu, Jan 3, 2013 at 11:34 AM, Alexey Panchenko alex.panche...@gmail.comwrote: Hi, You need nightly build of DLTK, at the moment available only from https://hudson.eclipse.org/hudson/job/dltk-nightly/ Regards, Alex On Thu, Jan 3, 2013 at 5:31 PM, Robert Gründler r.gruend...@gmail.comwrote: Alright thanks. I've tried the Kepler build now, and it seems contentassist is broken (stack trace at the end of the mail). Do i need to upgrade to a specific DLTK version too? Right now the following has been installed during dependency resolution: Dynamic Languages Toolkit - Core Frameworks 4.0.0.201206120848org.eclipse.dltk.core.feature.groupEclipse.org If you think it's a regression, i can file a bug in bugzilla. regards -robert Here's the trace: Caused by: java.lang.NoSuchMethodError: org.eclipse.dltk.ui.text.completion.ScriptCompletionProposal.setProposalInfo(Lorg/eclipse/dltk/ui/text/completion/ICompletionProposalInfo;)V at org.eclipse.php.internal.ui.editor.contentassist.PHPCompletionProposalCollector.createTypeProposal(PHPCompletionProposalCollector.java:291) at org.eclipse.php.internal.ui.editor.contentassist.PHPCompletionProposalCollector.createScriptCompletionProposal(PHPCompletionProposalCollector.java:119) at org.eclipse.dltk.ui.text.completion.ScriptCompletionProposalCollector.processUnprocessedProposal(ScriptCompletionProposalCollector.java:315) at org.eclipse.dltk.ui.text.completion.ScriptCompletionProposalCollector.processUnprocessedProposals(ScriptCompletionProposalCollector.java:291) at org.eclipse.dltk.ui.text.completion.ScriptCompletionProposalCollector.getScriptCompletionProposals(ScriptCompletionProposalCollector.java:273) at org.eclipse.dltk.ui.text.completion.ScriptCompletionProposalComputer.computeScriptCompletionProposals(ScriptCompletionProposalComputer.java:219) at org.eclipse.dltk.ui.text.completion.ScriptCompletionProposalComputer.computeCompletionProposals(ScriptCompletionProposalComputer.java:266) at org.eclipse.dltk.ui.text.completion.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:346) at org.eclipse.dltk.ui.text.completion.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:276) at org.eclipse.dltk.ui.text.completion.ContentAssistProcessor.collectProposals(ContentAssistProcessor.java:291) at org.eclipse.dltk.ui.text.completion.ContentAssistProcessor.computeCompletionProposals(ContentAssistProcessor.java:247) at org.eclipse.wst.sse.ui.internal.contentassist.CompoundContentAssistProcessor.computeCompletionProposals(CompoundContentAssistProcessor.java:127) at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1839) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:566) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:563) at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:498) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:492) at org.eclipse.jface.text.contentassist.ContentAssistant$2.run(ContentAssistant.java:378) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3965) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3642) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1049) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:939) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:79) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:587) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:542) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication
Re: [pdt-dev] Separate builds for Kepler and Juno
I've been comparing it to 4.2, with a fairly large project i'm working on at the moment. It seems i'm seeing the latest performance improvements implemented in the 4.3 dev builds. It's hard to say and very subjective, but it feels like the UI is responding a lot faster, for example: - Selecting the project in the explorer and holding the down arrow: this has been quite slow in 4.2. Now it's a lot faster - Opening large files has been sluggish in 4.2 sometimes, i didn't see this in 4.3. Files open instantly, also with a lot of open tabs. - Typing in general does not show any lags so far which i encountered in 4.2. -robert On Fri, Jan 4, 2013 at 9:55 AM, Jacek Pospychała jace...@zend.com wrote: Interesting! Do you have any examples what feels faster? (and you compared to 3.8 or 4.2?) It seems that Eclipse platform 4.3 (Kepler) dev builds were improved a lot in terms of GUI performance. On PDT side we didn't touch lately anything performance-related. Jacek On Fri, Jan 4, 2013 at 9:50 AM, Robert Gründler r.gruend...@gmail.com wrote: thanks Alexey, i got it working now. fyi: I don't know if it's the changes in Kepler / DLTK or PDT itself, but PDT seems a lot faster running the latest versions under kepler. Great job! regards -robert On Thu, Jan 3, 2013 at 11:34 AM, Alexey Panchenko alex.panche...@gmail.com wrote: Hi, You need nightly build of DLTK, at the moment available only from https://hudson.eclipse.org/hudson/job/dltk-nightly/ Regards, Alex On Thu, Jan 3, 2013 at 5:31 PM, Robert Gründler r.gruend...@gmail.com wrote: Alright thanks. I've tried the Kepler build now, and it seems contentassist is broken (stack trace at the end of the mail). Do i need to upgrade to a specific DLTK version too? Right now the following has been installed during dependency resolution: Dynamic Languages Toolkit - Core Frameworks4.0.0.201206120848 org.eclipse.dltk.core.feature.groupEclipse.org If you think it's a regression, i can file a bug in bugzilla. regards -robert Here's the trace: Caused by: java.lang.NoSuchMethodError: org.eclipse.dltk.ui.text.completion.ScriptCompletionProposal.setProposalInfo(Lorg/eclipse/dltk/ui/text/completion/ICompletionProposalInfo;)V at org.eclipse.php.internal.ui.editor.contentassist.PHPCompletionProposalCollector.createTypeProposal(PHPCompletionProposalCollector.java:291) at org.eclipse.php.internal.ui.editor.contentassist.PHPCompletionProposalCollector.createScriptCompletionProposal(PHPCompletionProposalCollector.java:119) at org.eclipse.dltk.ui.text.completion.ScriptCompletionProposalCollector.processUnprocessedProposal(ScriptCompletionProposalCollector.java:315) at org.eclipse.dltk.ui.text.completion.ScriptCompletionProposalCollector.processUnprocessedProposals(ScriptCompletionProposalCollector.java:291) at org.eclipse.dltk.ui.text.completion.ScriptCompletionProposalCollector.getScriptCompletionProposals(ScriptCompletionProposalCollector.java:273) at org.eclipse.dltk.ui.text.completion.ScriptCompletionProposalComputer.computeScriptCompletionProposals(ScriptCompletionProposalComputer.java:219) at org.eclipse.dltk.ui.text.completion.ScriptCompletionProposalComputer.computeCompletionProposals(ScriptCompletionProposalComputer.java:266) at org.eclipse.dltk.ui.text.completion.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:346) at org.eclipse.dltk.ui.text.completion.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:276) at org.eclipse.dltk.ui.text.completion.ContentAssistProcessor.collectProposals(ContentAssistProcessor.java:291) at org.eclipse.dltk.ui.text.completion.ContentAssistProcessor.computeCompletionProposals(ContentAssistProcessor.java:247) at org.eclipse.wst.sse.ui.internal.contentassist.CompoundContentAssistProcessor.computeCompletionProposals(CompoundContentAssistProcessor.java:127) at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1839) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:566) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:563) at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:498) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:492) at org.eclipse.jface.text.contentassist.ContentAssistant$2.run(ContentAssistant.java:378) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35
Re: [pdt-dev] Separate builds for Kepler and Juno
thanks for the info Jacek and happy new year ;) -robert On Fri, Dec 21, 2012 at 2:10 PM, Jacek Pospychała jace...@zend.com wrote: hi, I just created branch for PDT maintenance builds for Juno SR2 release. So if you're using Juno, please use p2 repository: http://download.eclipse.org/tools/pdt/updates/3.1-nightly/ If you're using Kepler developer builds, please use p2 repository: http://download.eclipse.org/tools/pdt/updates/3.2-nightly/ Previously I was hoping that it'd be possible to have just a single repository that works for everyone. Unfortunately it doesn't work, because other projects that we depend on grow quickly and become backward incompatible. The repository url that we used until now (http://download.eclipse.org/tools/pdt/updates/nightly/) will point to the Juno builds. so please update your urls! thanks! 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] Separate builds for Kepler and Juno
Using http://download.eclipse.org/tools/pdt/updates/3.2-nightly/ gives me the following pdt version PHP Development Tools (PDT)3.1.2.201212311412 Is this the correct one? I would have thought it should be 3.2.xxx regards -robert On Thu, Jan 3, 2013 at 9:59 AM, Robert Gründler r.gruend...@gmail.comwrote: thanks for the info Jacek and happy new year ;) -robert On Fri, Dec 21, 2012 at 2:10 PM, Jacek Pospychała jace...@zend.comwrote: hi, I just created branch for PDT maintenance builds for Juno SR2 release. So if you're using Juno, please use p2 repository: http://download.eclipse.org/tools/pdt/updates/3.1-nightly/ If you're using Kepler developer builds, please use p2 repository: http://download.eclipse.org/tools/pdt/updates/3.2-nightly/ Previously I was hoping that it'd be possible to have just a single repository that works for everyone. Unfortunately it doesn't work, because other projects that we depend on grow quickly and become backward incompatible. The repository url that we used until now (http://download.eclipse.org/tools/pdt/updates/nightly/) will point to the Juno builds. so please update your urls! thanks! 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] Separate builds for Kepler and Juno
) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) at org.eclipse.equinox.launcher.Main.run(Main.java:1443) On Thu, Jan 3, 2013 at 10:44 AM, Jacek Pospychała jace...@zend.com wrote: It's correct one. Version numbers haven't been updated yet. They should be shortly... On Thu, Jan 3, 2013 at 10:40 AM, Robert Gründler r.gruend...@gmail.com wrote: Using http://download.eclipse.org/tools/pdt/updates/3.2-nightly/ gives me the following pdt version PHP Development Tools (PDT)3.1.2.201212311412 Is this the correct one? I would have thought it should be 3.2.xxx regards -robert On Thu, Jan 3, 2013 at 9:59 AM, Robert Gründler r.gruend...@gmail.com wrote: thanks for the info Jacek and happy new year ;) -robert On Fri, Dec 21, 2012 at 2:10 PM, Jacek Pospychała jace...@zend.com wrote: hi, I just created branch for PDT maintenance builds for Juno SR2 release. So if you're using Juno, please use p2 repository: http://download.eclipse.org/tools/pdt/updates/3.1-nightly/ If you're using Kepler developer builds, please use p2 repository: http://download.eclipse.org/tools/pdt/updates/3.2-nightly/ Previously I was hoping that it'd be possible to have just a single repository that works for everyone. Unfortunately it doesn't work, because other projects that we depend on grow quickly and become backward incompatible. The repository url that we used until now (http://download.eclipse.org/tools/pdt/updates/nightly/) will point to the Juno builds. so please update your urls! thanks! 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] Using org.eclipse.php.ui.quickFixProcessors extensions point
Hi all, i've been implementing some quickFixProcessors today and was wondering how to properly use the IProblemIdentifier / IProblem API. The extension point passes the id of the problem to hasCorrections() as int, but the DefaultProblem API from DLTK seems to deprecate the usage of ints and moves to IProblemIdentifier API: https://github.com/eclipse/dltk.core/blob/master/core/plugins/org.eclipse.dltk.core/compiler/org/eclipse/dltk/compiler/problem/DefaultProblem.java#L67. Does anyone know an example of a proper implementation of that extension point using the IProblemIdentifier API instead? regards -robert ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] PDT nightly repo URL is changing
Thanks for the update. One question though: How should extenders handle stable/nightly versions? Will there be a 3.1.1 tag / branch in PDT we can use to reflect this? cheers -robert On Tue, Sep 25, 2012 at 12:13 PM, Jacek Pospychała jace...@zend.com wrote: hi, PDT nightly repository URL is changing from OLD: http://download.eclipse.org/tools/pdt/updates/3.1.1/nightly to NEW: http://download.eclipse.org/tools/pdt/updates/nightly As you know we're releasing 3.1.1 in next few days and the old URL wouldn't be good anymore. I hope that new URL will serve us for good. Old repository will stay here for a while, new repository is already set, so if you enjoy using latest-and-greatest at the cost of stability, you can switch now. enjoy, 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] Resurrect #pdt IRC channel
On Monday, September 24, 2012 12:09:13 PM UTC+2, Jacek Pospychała wrote: haha, cool! I'm on my way there. let's see if we'll make it to reach +5 people within next few weeks :) we've reached 7 users a moment ago ;) If can make it to change to topic from PDT 2.1 to something more recent, we might actually make it to over 10 ! -robert ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] migration to Git
that's great news, thanks for your efforts! -robert ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] PDT Sources
On Tue, Jul 24, 2012 at 9:43 AM, Stephan Hochdörfer s.hochdoer...@bitexpert.de wrote: as I just figured out the annoying bugs when cp code are fixed in the latest 3.1.1 version or at least seem to work for me again. But I am hitting another problem right now when editing a docblock comment. When I enter a text (e.g. @param) and hit the tab key the text is converted into an HTML element (@param/@param) which for me is not appropriate. Are you using zen-coding? If so, it's zen-coding which does that. I've alreday contacted [1] the author if it's possible to exclude specific files, but apparently it's not. cheers -robert [1] https://github.com/sergeche/eclipse-zencoding/issues/28 ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] Migrating to Git
sounds great! good look for the next steps :) -robert On Fri, Jul 13, 2012 at 2:37 PM, Jacek Pospychała jace...@zend.com wrote: Fyi, I switched PDT to Tycho today, so starting from now we have new build system and are a little closer to switching to Git. Let's see what the new week will bring...! Jacek -- *From:* pdt-dev-boun...@eclipse.org [pdt-dev-boun...@eclipse.org] on behalf of Robert Gruendler [r.gruend...@gmail.com] *Sent:* 06 July 2012 15:03 *To:* PDT Developers *Subject:* Re: [pdt-dev] Migrating to Git Hi, thanks for the info. The main reason i was asking is because i was unsure if the cvs tree i'm using is still being used. Migrating it together with switching to maven/tycho absolutely makes sense! regards -robert On 7/6/12 14:52 , Jacek Pospychała wrote: One thing that's holding us back wrt migration is that PDT is still being built with Athena CBI. System that once popular, has been abandoned a while ago and it doesn't nicely support Git. I wanted to migrate to Git together with jump to Maven/Tycho based build, but it's more work. But if you're asking then maybe indeed we should switch to Git sooner while staying with current build. -- *From:* pdt-dev-boun...@eclipse.org [pdt-dev-boun...@eclipse.org] on behalf of Robert Gründler [r.gruend...@gmail.com] *Sent:* 06 July 2012 00:36 *To:* PDT Developers *Subject:* Re: [pdt-dev] Migrating to Git are there any news on the git migration? regards -robert ___ pdt-dev mailing listpdt-dev@eclipse.orghttps://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] Future of PDT development
Hi Seva, if you're interested in the pdt-extensions discussion, feel free to join us: https://groups.google.com/forum/?fromgroups#!forum/pdt-extensions-platform regards -robert ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] Future of PDT development
Hi Jacek, On Wed, Jul 11, 2012 at 10:47 AM, Jacek Pospychała jace...@zend.com wrote: Hi Robert, it's great to hear about your plans. We always enjoyed seeing new plugins for PDT as this confirms there's strong PHP community around Eclipse. I'm even more happy now to hear that there's more to come. Where can I follow your current discussion to better understand what you're planning/doing? Why not discuss or even develop this pdt-extension platform directly in PDT? right now there's a github group [1] with a wiki and a google group where our discussion is taking place [2]. Currently we're still in the planning phase. It would be great if the core features could be discussed/developed directly with the PDT team. From Zend pov, in the past the features that you mention were supposed to differentiate PDT and Zend Studio. Nowadays Zend Studio has gone in slightly different direction, and also more free alternatives popped up, so it's not argument any more. But simply moving features between products takes us time, risk of regressions and gives no short term benefits. So although there's consensus in Zend that we could contribute back to PDT, it's hard to actually find time for that. I understand. What i see for some features though is that there will be (or already are) duplicate implementations (see [3] for a small list what i've come up with). So maybe we can coordinate this so those features are at least somehow distinct for the end-user in the menu structure (e.g. getter/setter generator or the new class wizard). It would be optimal imho if we could merge some of this stuff in the future as the current situation leads to unnecessary workload on both sides ;) In short term, until October we're very busy with next Zend Studio, but as part of that we want to get formatter better (bug 320130) and improve debugger. After that, we'll be more into bug fixing and planning next year, it'll be also good time to give more love to PDT. By the end of the year we're also migrating PDT to Git and probably change it's build system. That sounds great! Our short term goal is to provide a common p2 repository for all existing pdt extensions and figure out which parts of our plugins can be refactored into a more abstracted codebase. The overall plan can be found on the wiki i've linked below. Does this answer your questions? Absolutely ;) regards -robert [1] https://github.com/phpsrc [2] https://groups.google.com/forum/?fromgroups#!forum/pdt-extensions-platform ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
[pdt-dev] Future of PDT development
Dear PDT team, we are a group of PDT extenders who are working on the following plugins: http://www.phpsrc.org/projects/pti-php-codesniffer/wiki/ http://www.phpsrc.org/projects/pti-phpunit/wiki/ http://www.phpsrc.org/projects/pti-phpdepend/wiki/ http://www.phpsrc.org/projects/pti-phpcpd/wiki/ http://www.phpsrc.org/projects/pti-php-checker/wiki/ http://www.php-maven.org/branches/2.0-SNAPSHOT/tut-usingeclipse.html http://symfony.dubture.com/ http://twig.dubture.com/ http://pde.dubture.com/ We think that Eclipse is a great development platform, however PDT lacked some basic features, which is the reason why we started working on extensions to overcome limitations like - Code formatting - Refactoring (getter/setter generation, renaming of variables, etc) - PHPUnit integration - Codesniffer support - Proper support for object oriented projects (Class generator, validation, etc) As we are now thinking about joining those efforts into a single pdt-extension platform, we’d like to get some feedback from the PDT development team regarding the future of PDT itself. In our view there have been no feature enhancements in PDT for quite some time, especially regarding some of those base features mentioned above. As most of those features are implemented in Zend-Studio but not in PDT, we are wondering what’s the rationale behind keeping those features closed source. A lot of the Zend-Studio features are available through our contributions on an open-source basis. In our opinion it would be better for both PDT and Zend-Studio if the basic featureset of PDT could compare with that of other editors of scripting-languages in Eclipse and/or competing IDEs. So basically we would like to get some info about the future strategy of Zend regarding PDT and the open-source community (fyi: we've tried to collect all known pdt extensions so far in our wiki [1] ) regards -robert [1] https://github.com/PHPsrc/wiki/wiki/PDT-Extension-project-list ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] [cross-project-issues-dev] Does this behavior violate EPL or community prinicples
Hi Jacek, thanks for the info. Could this nightly updatesite be mentioned here? http://www.eclipse.org/projects/project.php?id=tools.pdt Looks like there's quite some confusion going an among users: http://www.eclipse.org/forums/index.php/t/366539/ regards -robert On Fri, Jul 6, 2012 at 9:33 AM, Jacek Pospychała jace...@zend.com wrote: hi, you're right there's been a bit of mess with PDT lately. Although we continuously work on the project, there was nobody since Indigo SR2 to update project version (3.0.1-3.1) and promote it regularly, hence Juno release train ended up with same PDT package as Indigo SR2, dated 2012-01-11. We want to fix this for Juno SR1, which will have PDT version 3.1.1. Our friendly Zend QA team is currently verifying about 200 fixed bugs from last months in PDT bugzilla. We just started publishing nightly builds update site at http://download.eclipse.org/tools/pdt/updates/3.1.1/nightly so you can give it a try as well. It's also available as zip at pdt downloads. In June we also provided a fresh all-in-one package at www.zend.com/pdt/downloads if you prefer a complete bundle. Jacek Pospychala, PDT lead -- *From:* pdt-dev-boun...@eclipse.org [pdt-dev-boun...@eclipse.org] on behalf of Mike Milinkovich [mike.milinkov...@eclipse.org] *Sent:* 05 July 2012 15:23 *To:* 'Cross project issues' *Cc:* 'Tools PMC mailing list'; pdt-dev@eclipse.org *Subject:* Re: [pdt-dev] [cross-project-issues-dev] Does this behavior violate EPL or community prinicples +Tools PMC (note bolded comment below) +PDT dev list (please see https://bugs.eclipse.org/bugs/show_bug.cgi?id=383977) *From:* cross-project-issues-dev-boun...@eclipse.org [mailto: cross-project-issues-dev-boun...@eclipse.org] *On Behalf Of *zhu kane *Sent:* July-05-12 1:53 AM *To:* Cross project issues *Subject:* Re: [cross-project-issues-dev] Does this behavior violate EPL or community prinicples I also appreciate the effort of PDT team made, it's great to release maintenance version in Indigo SR2 time frame. And it still works well in Juno. I don't think development team is possible to mess up the release version. Anyway *I would like to see comments from PDT and PMC*. Mengxin On Wed, Jul 4, 2012 at 3:04 PM, Ed Willink e...@willink.me.uk wrote: Hi The situation doesn't seem nearly as bad as you make out. The public promoted builds on http://www.eclipse.org/pdt/downloads/ show a 2-Jan-2012 3.0.0 Maintenance build as the most recent and examining the ZIP content reveals 3.0.1 content. Installing the Juno release train installs a 2-Jan-2012 3.0.1, which correlates with the Eclipse CVS. The Hudson build job https://hudson.eclipse.org/hudson/job/cbi-pdt-3.0-juno/changes shows active public development of 3.1 in the Eclipse CVS. So it seems there are some releng difficulties that cause 3.0.1 to be listed as 3.0.0 on the download page, and some over-enthusiasm that causes a 3.0.1 contribution to be called 3.1. A rename can fix the download page. A resubmission of the review slides can fix the misleading version claim. Perhaps Kepler should be 3.2 to avoid more confusion. Regards Ed Willink On 04/07/2012 06:17, zhu kane wrote: Hello community, I hesitated about raising such question in here. But I can't get any response from PDT project even if filing critical bug for it[1]. PDT team announced PDT 3.1 was released[2] with Juno simultaneous release. PDT 3.1 also is listed in highlighted Juno project list[3]. But none of Eclipse users knows how to install it. I would like to believe it's just a bug, however nobody of PDT project takes action for it. In my understanding all projects of Eclipse.org are open source, everybody can browse the latest source code even under developing. I'm astonished that I can't find any commit related to PDT 3.1 from its source repository[4]. Looks like PDT 3.1 doesn't have any public nightly build and integration build. I only find a build[5] for 3.0 in Hudson. I'm wondering whether Eclipse.org/EPL allows a project under it that is not really open source and just declared its new release. Hope experienced people help resolve my doubts. Thank you. [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=383977 [2] https://bugs.eclipse.org/bugs/attachment.cgi?id=216929 [3] http://eclipse.org/juno/projects.php [4] http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.pdt/features/org.eclipse.php-feature/?root=Tools_Project [5] https://hudson.eclipse.org/hudson/job/cbi-pdt-3.0-juno/changes Mengxin Zhu ___ 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] [cross-project-issues-dev] Does this behavior violate EPL or community prinicples
this seems to be the correct one: http://www.zend.com/en/community/pdt/downloads After the migration to tycho/maven, the PDT team could provide a non-branded version too again ;) cheers -robert On Fri, Jul 6, 2012 at 7:02 PM, Jeff Dafoe jeffda...@gmail.com wrote: In June we also provided a fresh all-in-one package at www.zend.com/pdt/downloads if you prefer a complete bundle. I'm not seeing the bundle there, there's a Page not found. -Jeff ___ 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] Migrating to Git
are there any news on the git migration? regards -robert ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] [cross-project-issues-dev] Does this behavior violate EPL or community prinicples
On Thu, Jul 5, 2012 at 3:23 PM, Mike Milinkovich mike.milinkov...@eclipse.org wrote: Installing the Juno release train installs a 2-Jan-2012 3.0.1, which correlates with the Eclipse CVS. I can't confirm this. The juno update site shows: PHP Development Tools (PDT) SDK Feature 3.0.0.v201201110400-77-184_2BEICRgM_fMVcz0M4Va9O regards -robert ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] Install latest nightly from hudson
any news on this?
regards
-robert
On Fri, Sep 16, 2011 at 8:11 AM, Roy Ganor r...@zend.com wrote:
Hi Sergio,
The testing fails because of a missing Emma plugins that's the reason I
disabled testing...
I contacted Eclipse webmaster to allow me to install emma again on the
Hudson build machine.
Best regards,
Roy
-Original Message-
From: pdt-dev-boun...@eclipse.org [mailto:pdt-dev-boun...@eclipse.org] On
Behalf Of Sergio Mart?n Morillas
Sent: Thursday, September 15, 2011 9:22 PM
To: PDT Developers
Subject: Re: [pdt-dev] Install latest nightly from hudson
Roy, please can you enable testing again?
org.eclipse.pdt/org.eclipse.pdt.releng/testing.properties
+testPluginsToRun=org.eclipse.php.core.tests
In the last build vnc connect to server, but no test has been defined:
[exec] all:
[exec] [echo] testPluginDirRoot:
/opt/users/hudsonbuild/.hudson/jobs/cbi-pdt-3.0-indigo/workspace/build/N201109150911/testing/target/eclipse/dropins/pdt/eclipse/plugins
[exec]
[exec] genHtml:
[exec] [echo] ** Warning! No test results found in
/opt/public/jobs/cbi-pdt-3.0-indigo/workspace/build/N201109150911/testing/N201109150911/testing/results/xml!
**
Succesful build:
[exec] all:
[exec] [echo] testPluginDirRoot:
/opt/users/hudsonbuild/.hudson/jobs/cbi-pdt-3.0-indigo/workspace/build/N201108100912/testing/target/eclipse/dropins/pdt/eclipse/plugins
[exec] [echo] testPluginName: org.eclipse.php.core.tests
[exec] [echo] Run
/opt/users/hudsonbuild/.hudson/jobs/cbi-pdt-3.0-indigo/workspace/build/N201108100912/testing/target/eclipse/dropins/pdt/eclipse/plugins/org.eclipse.php.core.tests_3.0.0.v201108100912/test.xml:
Thank you very much.
2011/9/14 Sergio Martín Morillas smartinmoril...@gmail.com:
It seems the workaround has worked. But now it fails to run tests :(
I compared the console log from 196 build with the failed build log
and I found this:
[exec] Use DISPLAY port :41
[exec] [runtests] Using X server: 'Xvnc :41 -geometry 1024x768
-depth 24 -ac'
[exec] xhost: unable to open display localhost:41.0
Could this be the problem?
2011/9/13 Sergio Martín Morillas smartinmoril...@gmail.com:
As a workaround, maybe you can setup proxy manually in build.xml file:
setproxy proxyhost=proxy.eclipse.org proxyport=9898 /
On Mon, Sep 12, 2011 at 11:26 AM, Roy Ganor r...@zend.com wrote:
For some reason, both properties are not set. We need to fix it in the
sh script.
check-proxy:
[subant] Failure for target 'postFetch' of:
/opt/users/hudsonbuild/.hudson/jobs/cbi-pdt-3.0-indigo/workspace/build/org.eclipse.pdt.releng/buildExtra.xml
[subant] The following error occurred while executing this line:
[subant]
/opt/users/hudsonbuild/.hudson/jobs/cbi-pdt-3.0-indigo/workspace/build/org.eclipse.pdt.releng/buildExtra.xml:22:
The following error occurred while executing this line:
[subant]
/opt/users/hudsonbuild/.hudson/jobs/cbi-pdt-3.0-indigo/workspace/build/org.eclipse.pdt.releng/buildExtra.xml:58:
Properties 'http.proxyHost' and 'http.proxyPort' are both not set.
Roy
-Original Message-
From: pdt-dev-boun...@eclipse.org [mailto:pdt-dev-boun...@eclipse.org]
On Behalf Of Sergio Mart?n Morillas
Sent: Sunday, September 11, 2011 7:36 PM
To: PDT Developers
Subject: Re: [pdt-dev] Install latest nightly from hudson
Hi Roy,
It seems that cbi-pdt-2.2-helios was the same problem. Comment
reported by Jacek Pospychala:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=322828#c23
Please add this check to build.xml:
target name=check-proxy description=Checks that proxy properties
are set before proceeding -- fails with diagnosis otherwise.
condition property=check-proxy.hostAndPortBothNotSet
and
notisset property=http.proxyHost//not
notisset property=http.proxyPort//not
/and
/condition
fail if=check-proxy.hostAndPortBothNotSetProperties
'http.proxyHost' and 'http.proxyPort' are both not set./fail
condition property=check-proxy.hostSetOnly
and
isset property=http.proxyHost/
notisset property=http.proxyPort//not
/and
/condition
fail if=check-proxy.hostSetOnlyProperty 'http.proxyHost' set to
'${http.proxyHost}' but 'http.proxyPort' not set./fail
condition property=check-proxy.portSetOnly
and
isset property=http.proxyPort/
notisset property=http.proxyHost//not
/and
/condition
fail if=check-proxy.portSetOnlyProperty 'http.proxyPort' set to
'${http.proxyPort}' but 'http.proxyHost' not set./fail
echoProperty 'http.proxyHost' is set to '${http.proxyHost}' and
property 'http.proxyPort' is set to '${http.proxyPort}'./echo
/target
This code is from Virgo project [1], they had a similar problem:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=325824
[1]
Re: [pdt-dev] Initialize buildpath and project structure in new project wizard
Hi Krzysztof,
at which point in your wizard is this code executed?
cheers
-robert
On Mon, Sep 19, 2011 at 9:52 AM, Krzysztof Maziarz
krzysztof.mazi...@compactsolutionsllc.com wrote:
Hi Robert,
For me the following piece of code works fine:
IScriptProject scriptProject = DLTKCore.create(project.getProject());
if (scriptProject != null) {
ListIBuildpathEntry entries = new LinkedListIBuildpathEntry();
IPath yiiFrameworkPath = new
Path(org.eclipse.dltk.core.environment.localEnvironment/:,this.getFrameworkLocation());
IBuildpathEntry entry = DLTKCore.newBuiltinEntry(yiiFrameworkPath,
new
IAccessRule[0], new IBuildpathAttribute[0], new IPath[0], new IPath[0],
false, true);
entries.add(entry);
try {
BuildPathUtils.addEntriesToBuildPath(scriptProject,
entries);
} catch (ModelException e) {
YiiBundle.logError(e.getMessage(), e);
}
}
Best regards,
Krzysztof
On Mon, 2011-09-19 at 09:21 +0200, Robert Gruendler wrote:
Hi,
i'm extending the PDT Project Wizard to initialize new Projects with the
structure for the Symfony framework
Basically i'm doing the following:
1. Iterate the skeleton project and create the project folders/files
recursively.
2. Create a IBuildpathEntry for the source folders
3. Call init() passing the script project and the buildpathentries.
The code of the wizard page can be found here:
https://github.com/pulse00/Symfony-2-Eclipse-Plugin/blob/master/com.dubture.symfony.ui/src/com/dubture/symfony/ui/wizards/project/SymfonyProjectWizardThirdPage.java#L53
The problem is that the Buildpathentries show up in the UI of the wizard
and also the project structure is initialized correctly,
but the .buildpath file does not contain the correct entries. It's the
same like the default one from the PDT project wizard.
Has anyone an idea what i'm missing here? Or is there a better way to
achieve the initialization of a project?
regards
-robert
___
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] Index Non-PHP Sourcefiles
On 6/29/11 6:01 AM, 赵忠伟 wrote: I think you need ask this question in dltk group,after debugging,I think the DLTK indexer only can visit ISourceModule ok, this isn't a big problem, i can still use my own indexer then for non-php files. as your another question,we can not get ISourceModule from PhpIndexingVisitor,so you still can not visit the XML/Yaml config files:( hm, this is bad news for me ;) The reason is because Symfony2 declares the same framework elements in different places, like Route-Patterns for example. They can be declared in XML/Yaml files and also inside PHP DocBlocks. So my custom index looks a little bit different than the DLTK index, where each ModelElement found during indexing is tied to the parent container/resource. Which means that all my custom model elements need to have the IScriptProject as their parent, so when i search for them, i basically always search inside a project-scope. When i don't have a handle to the Project / SourceModule inside the PHPIndexingVisitor, i cant' make this relation to my custom elements. I hope my explanation is somewhat understandable ;) Is there maybe another way to get the containing SourceModule or at least the IScriptProject from within an PHPIndexingVisitor? Maybe by using some Utility class i haven't found yet? I've already searched a lot through the DLTK/PDT code, but unfortunately i couldn't find a way to do this. thanks again for your help! regards -robert 2011/6/27 Robert Gründler r.gruend...@gmail.com mailto:r.gruend...@gmail.com Hi, the framework i'm writing a plugin for uses XML/Yaml config files. Those files define domainspecific elements, which i'm currently indexing using a custom H2/SQL implementation. I'm wondering if it's possible to get the DLTK/PHP indexer to also visit those XML/Yaml files, so i can use the existing Indexing framwork - probably store those elements as IModelElement.USER_ELEMENT and encode everything i need into the metadata (i'm doing this already for TemplateVariables). All i'm need to do is to parse some xml/yaml attributes, which can then later be used for code-hints and Hyperlink-detection etc. I've tried already a couple of things, even to provide my own LanguageToolkit, but it seems DLTK only allows one toolkit per IScriptProject. Any hints if this is possible? Or should i stay with my own indexer? regards -robert ___ pdt-dev mailing list pdt-dev@eclipse.org mailto:pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev -- Thanks! Best Regards! Zhao ___ 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] Index Non-PHP Sourcefiles
that sounds great, thanks ;) -robert On 6/29/11 3:38 PM, 赵忠伟 wrote: hi, Do not worry,I think it is not a big problem that we pass SourceModule to PHPIndexingVisitor:) 2011/6/29 Robert Gründler r.gruend...@gmail.com mailto:r.gruend...@gmail.com On 6/29/11 6:01 AM, 赵忠伟 wrote: I think you need ask this question in dltk group,after debugging,I think the DLTK indexer only can visit ISourceModule ok, this isn't a big problem, i can still use my own indexer then for non-php files. as your another question,we can not get ISourceModule from PhpIndexingVisitor,so you still can not visit the XML/Yaml config files:( hm, this is bad news for me ;) The reason is because Symfony2 declares the same framework elements in different places, like Route-Patterns for example. They can be declared in XML/Yaml files and also inside PHP DocBlocks. So my custom index looks a little bit different than the DLTK index, where each ModelElement found during indexing is tied to the parent container/resource. Which means that all my custom model elements need to have the IScriptProject as their parent, so when i search for them, i basically always search inside a project-scope. When i don't have a handle to the Project / SourceModule inside the PHPIndexingVisitor, i cant' make this relation to my custom elements. I hope my explanation is somewhat understandable ;) Is there maybe another way to get the containing SourceModule or at least the IScriptProject from within an PHPIndexingVisitor? Maybe by using some Utility class i haven't found yet? I've already searched a lot through the DLTK/PDT code, but unfortunately i couldn't find a way to do this. thanks again for your help! regards -robert 2011/6/27 Robert Gründler r.gruend...@gmail.com mailto:r.gruend...@gmail.com Hi, the framework i'm writing a plugin for uses XML/Yaml config files. Those files define domainspecific elements, which i'm currently indexing using a custom H2/SQL implementation. I'm wondering if it's possible to get the DLTK/PHP indexer to also visit those XML/Yaml files, so i can use the existing Indexing framwork - probably store those elements as IModelElement.USER_ELEMENT and encode everything i need into the metadata (i'm doing this already for TemplateVariables). All i'm need to do is to parse some xml/yaml attributes, which can then later be used for code-hints and Hyperlink-detection etc. I've tried already a couple of things, even to provide my own LanguageToolkit, but it seems DLTK only allows one toolkit per IScriptProject. Any hints if this is possible? Or should i stay with my own indexer? regards -robert ___ pdt-dev mailing list pdt-dev@eclipse.org mailto:pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev -- Thanks! Best Regards! Zhao ___ 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 -- Thanks! Best Regards! Zhao ___ 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] Index Non-PHP Sourcefiles
i've created a patch that passes the SourceModule over to the extension
(attached).
Would this implementation be ok for you?
regards
-robert
On 6/29/11 3:38 PM, 赵忠伟 wrote:
hi,
Do not worry,I think it is not a big problem that we pass SourceModule
to PHPIndexingVisitor:)
2011/6/29 Robert Gründler r.gruend...@gmail.com
mailto:r.gruend...@gmail.com
On 6/29/11 6:01 AM, 赵忠伟 wrote:
I think you need ask this question in dltk group,after
debugging,I think the DLTK indexer only can visit ISourceModule
ok, this isn't a big problem, i can still use my own indexer then
for non-php files.
as your another question,we can not get ISourceModule from
PhpIndexingVisitor,so you still can not visit the XML/Yaml config
files:(
hm, this is bad news for me ;)
The reason is because Symfony2 declares the same framework
elements in different places, like Route-Patterns for example. They
can be declared in XML/Yaml files and also inside PHP DocBlocks.
So my custom index looks a little bit different than the DLTK
index, where each ModelElement found during indexing
is tied to the parent container/resource.
Which means that all my custom model elements need to have the
IScriptProject as their parent, so when i search for them, i basically
always search inside a project-scope.
When i don't have a handle to the Project / SourceModule inside
the PHPIndexingVisitor, i cant' make this relation to my custom
elements.
I hope my explanation is somewhat understandable ;)
Is there maybe another way to get the containing SourceModule or
at least the IScriptProject from within an PHPIndexingVisitor? Maybe
by using some Utility class i haven't found yet?
I've already searched a lot through the DLTK/PDT code, but
unfortunately i couldn't find a way to do this.
thanks again for your help!
regards
-robert
2011/6/27 Robert Gründler r.gruend...@gmail.com
mailto:r.gruend...@gmail.com
Hi,
the framework i'm writing a plugin for uses XML/Yaml config
files. Those files define domainspecific
elements, which i'm currently indexing using a custom H2/SQL
implementation.
I'm wondering if it's possible to get the DLTK/PHP indexer to
also visit those XML/Yaml files, so i can
use the existing Indexing framwork - probably store those
elements as IModelElement.USER_ELEMENT
and encode everything i need into the metadata (i'm doing
this already for TemplateVariables).
All i'm need to do is to parse some xml/yaml attributes,
which can then later be used for code-hints
and Hyperlink-detection etc.
I've tried already a couple of things, even to provide my own
LanguageToolkit, but it seems DLTK
only allows one toolkit per IScriptProject.
Any hints if this is possible? Or should i stay with my own
indexer?
regards
-robert
___
pdt-dev mailing list
pdt-dev@eclipse.org mailto:pdt-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/pdt-dev
--
Thanks!
Best Regards!
Zhao
___
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
--
Thanks!
Best Regards!
Zhao
___
pdt-dev mailing list
pdt-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/pdt-dev
### Eclipse Workspace Patch 1.0
#P org.eclipse.php.core
Index: src/org/eclipse/php/core/index/PhpIndexingVisitorExtension.java
===
RCS file:
/cvsroot/tools/org.eclipse.pdt/plugins/org.eclipse.php.core/src/org/eclipse/php/core/index/PhpIndexingVisitorExtension.java,v
retrieving revision 1.2
diff -u -r1.2 PhpIndexingVisitorExtension.java
--- src/org/eclipse/php/core/index/PhpIndexingVisitorExtension.java 27 Jun
2011 12:27:02 - 1.2
+++ src/org/eclipse/php/core/index/PhpIndexingVisitorExtension.java 29 Jun
2011 18:46:26 -
@@ -13,6 +13,7 @@
import org.eclipse.dltk.ast.ASTNode;
import org.eclipse.dltk.ast.ASTVisitor;
+import org.eclipse.dltk.core.ISourceModule;
import org.eclipse.dltk.core.index2.IIndexingRequestor;
import org.eclipse.dltk.core.index2.IIndexingRequestor.DeclarationInfo;
import org.eclipse.dltk.core.index2.IIndexingRequestor.ReferenceInfo;
@@ -26,6 +27,7 @@
public abstract class PhpIndexingVisitorExtension extends ASTVisitor {
protected IIndexingRequestor requestor;
+ protected ISourceModule sourceModule
[pdt-dev] Retrieving a handle to the SourceModule in PhpIndexingVisitorExtension
Hi, i've read through the PDT code, but i can't find a way to retrieve the current SourceModule in the PhpIndexingVisitorExtension. The reason i would need this is because i need to index a mapping between some fields in specific classes and the path they reside in. Can this be done, or is there a reason why the SourceModule is not accessible in this visitor? thanks again! -robert ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] Provide type-hints for variables declared in different SourceModule
so the patch will be part of your next release? if so, any estimations when
this will be?
I'm asking because i can't provide my plugin to testers before that.
thanks!
-robert
On 6/27/11 9:57 AM, 赵忠伟 wrote:
hi,
yes,I just want to make a patch like yours for you:)
2011/6/27 Robert Gründler r.gruend...@gmail.com
mailto:r.gruend...@gmail.com
Hi,
yes, i've tried that, but the extensions array in the
PHPIndexingVisitor is private,
so i can't simply override the constructor and cast them to my own
Extensions.
This is the plugin.xml of my current implementation:
https://github.com/pulse00/Symfony-2-Eclipse-Plugin/blob/master/org.eclipse.symfony.core/plugin.xml#L63
I've created a patch though to pass the requestor over to the
PhpIndexingVisitorExtension (attached).
Couldn't find another way to actually add elements to the Sql Index.
Am i missing something?
-robert
On 6/27/11 8:52 AM, 赵忠伟 wrote:
hi Robert ,
Do you implement your own IndexingVisitor?
btw,does it make sense if we pass requestor(IIndexingRequestor)
to PhpIndexingVisitorExtension ?
2011/6/25 Robert Gründler r.gruend...@gmail.com
mailto:r.gruend...@gmail.com
sorry for spamming the list, but there's really not much
information in the net available concerning PDT indexing.
I've followed the contributing to index chapter in the wiki
http://wiki.eclipse.org/Extending_PDT_2.2#Contributing_to_index
but i'm not sure if this is still up-to-date, because when i
contribute additional fields to a TypeDeclaration,
nothing appears in code assist for $this- in that class.
What confuses me is that a PDT Indexing Extension needs to
subclass PhpIndexingVisitorExtension
and provide declarationinfos using modifyDeclaration() calls.
However, the modifyDeclaration() method in the
PhpIndexingVisitorExtension is completely empty,
as apposed to the PhpIndexingVisitor which calls
requestor.addDeclaration(info) in this method.
The requestor is not available to extensions though.
My IndexingVisitor does basically the same like the one in
the Wiki (inside the endVisit(TypeDeclaration) method):
DeclarationInfo info = new
DeclarationInfo(IModelElement.FIELD,
Modifiers.AccPublic, start, length,
start, length, name,
null, null, namespace.getName(),
currentClass.getName());
modifyDeclaration(field, info);
Do i need to specify an implementation for the
modifyDeclaration() method in my indexer as well?
thanks!
-robert
2011/6/24 Robert Gründler r.gruend...@gmail.com
mailto:r.gruend...@gmail.com
Hi,
a lot of PHP Frameworks implement the MVC pattern, and
i'm wondering what's the
best way to provide codeassist for PHP variables in files
that have been declared
in other SourceModules.
Let's say you have the class UserController with the
method showUser() (in /UserController.php)
... class declaration
public function showUser() {
$user = UserDAO::retrieveUserByID($id);
return array('showUser.php', array('user' = $user'))
}
The framework then renders the file 'showUser.php' and
passes in the $user object
as a variable named $user.
What i have done right now is the following:
1. In the SourceElementRequestor extension i visit the
ReturnStatements of methods in Controller
classes.
2. I detect the variables returned by that method and
store it in some custom Singleton.
3. Register a completionContext/Strategy which retrieves
the correct variables for the current php file from the
Singleton.
This approach works, though it doesn't feel properly
integrated into the DLTK/PDT model, as
1. I'm simply storing the ViewVariable in-memory in my
singleton, so after Eclipse relaunches, the whole project
needs to be rebuilt for completion to work.
2. I'm getting ConcurrentModificationExceptions in my
Singleton class during the BuildPhase as apparently the
SourceParsing
takes place in multiple threads.
So my question is, is there a way to contribute those
Variables which are being passed to the View-Templates
properly to the DLTK/PDT model ?
regards,
-robert
___
pdt-dev mailing list
pdt-dev@eclipse.org mailto:pdt-dev
Re: [pdt-dev] Provide type-hints for variables declared in different SourceModule
just to be sure: is this the nightly build that fails?
https://hudson.eclipse.org/hudson/job/cbi-pdt-3.0-indigo/
so i can check for updates.
regards
-robert
On 27.06.11 10:13, 赵忠伟 wrote:
hmmm,I am not sure the time,I think I will apply the patch today.But
now there is a something wrong with our pdt build on eclipse,so the
nightly build always fails.And we will fix it asap,but for release
version,I am not sure.
2011/6/27 Robert Gründler r.gruend...@gmail.com
mailto:r.gruend...@gmail.com
so the patch will be part of your next release? if so, any
estimations when
this will be?
I'm asking because i can't provide my plugin to testers before that.
thanks!
-robert
On 6/27/11 9:57 AM, 赵忠伟 wrote:
hi,
yes,I just want to make a patch like yours for you:)
2011/6/27 Robert Gründler r.gruend...@gmail.com
mailto:r.gruend...@gmail.com
Hi,
yes, i've tried that, but the extensions array in the
PHPIndexingVisitor is private,
so i can't simply override the constructor and cast them to
my own Extensions.
This is the plugin.xml of my current implementation:
https://github.com/pulse00/Symfony-2-Eclipse-Plugin/blob/master/org.eclipse.symfony.core/plugin.xml#L63
I've created a patch though to pass the requestor over to the
PhpIndexingVisitorExtension (attached).
Couldn't find another way to actually add elements to the Sql
Index.
Am i missing something?
-robert
On 6/27/11 8:52 AM, 赵忠伟 wrote:
hi Robert ,
Do you implement your own IndexingVisitor?
btw,does it make sense if we pass
requestor(IIndexingRequestor) to PhpIndexingVisitorExtension ?
2011/6/25 Robert Gründler r.gruend...@gmail.com
mailto:r.gruend...@gmail.com
sorry for spamming the list, but there's really not much
information in the net available concerning PDT indexing.
I've followed the contributing to index chapter in the
wiki
http://wiki.eclipse.org/Extending_PDT_2.2#Contributing_to_index
but i'm not sure if this is still up-to-date, because
when i contribute additional fields to a TypeDeclaration,
nothing appears in code assist for $this- in that class.
What confuses me is that a PDT Indexing Extension needs
to subclass PhpIndexingVisitorExtension
and provide declarationinfos using modifyDeclaration()
calls.
However, the modifyDeclaration() method in the
PhpIndexingVisitorExtension is completely empty,
as apposed to the PhpIndexingVisitor which calls
requestor.addDeclaration(info) in this method.
The requestor is not available to extensions though.
My IndexingVisitor does basically the same like the one
in the Wiki (inside the endVisit(TypeDeclaration) method):
DeclarationInfo info = new
DeclarationInfo(IModelElement.FIELD,
Modifiers.AccPublic, start,
length, start, length, name,
null, null, namespace.getName(),
currentClass.getName());
modifyDeclaration(field, info);
Do i need to specify an implementation for the
modifyDeclaration() method in my indexer as well?
thanks!
-robert
2011/6/24 Robert Gründler r.gruend...@gmail.com
mailto:r.gruend...@gmail.com
Hi,
a lot of PHP Frameworks implement the MVC pattern,
and i'm wondering what's the
best way to provide codeassist for PHP variables in
files that have been declared
in other SourceModules.
Let's say you have the class UserController with the
method showUser() (in /UserController.php)
... class declaration
public function showUser() {
$user = UserDAO::retrieveUserByID($id);
return array('showUser.php', array('user' = $user'))
}
The framework then renders the file 'showUser.php'
and passes in the $user object
as a variable named $user.
What i have done right now is the following:
1. In the SourceElementRequestor extension i visit
the ReturnStatements of methods in Controller
classes.
2. I detect the variables returned by that method
and store it in some custom Singleton.
3. Register a completionContext/Strategy which
retrieves the correct variables for the current php
file from the Singleton
[pdt-dev] org.eclipse.wst.sse.ui.semanticHighlighting extension
Hi again, i tried to follow the Wiki entry to add SemanticHighlighting to my plugin for PHP Annotations: http://wiki.eclipse.org/PDT/Dev2Dev/Semantic by adding an extension point like this: extension point=org.eclipse.wst.sse.ui.semanticHighlighting highlighting class=org.eclipse.symfony.ui.editor.highlighting.AnnotationHighlighting target=org.eclipse.php.core.phpsource /highlighting /extension I'm getting a ClassNotFoundException during startup for org.eclipse.symfony.ui.editor.highlighting.AnnotationHighlighting, although my plugin is exporting the necessary packages. According to the eclipse irc channel, the way the SemanticHighlighting extensions are loaded by the PDT plugin will only work for internal pdt-bundle classes (in SemanticHighlightingManager line 71). Is this a bug in PDT or am i just not providing the extension point correctly? thanks! -robert ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] org.eclipse.wst.sse.ui.semanticHighlighting extension
nope, i'm still getting the ClassNotFoundException for my extension.
according to the irc channel the problem is line 71:
AbstractSemanticHighlighting instance = clazz.newInstance();
which should look more like this:
final Object o = element.createExecutableExtension(class);
if (o instanceof AbstractSemanticHighlighting) {
AbstractSemanticHighlighting instance = (AbstractSemanticHighlighting) o;
rules.add(instance);
}
not sure though if this causes the ClassNotFoundException though.
regards
-robert
On 27.06.11 14:21, 赵忠伟 wrote:
hi,
Does this patch work?
2011/6/27 Robert Gründler r.gruend...@gmail.com
mailto:r.gruend...@gmail.com
Hi again,
i tried to follow the Wiki entry to add SemanticHighlighting to my
plugin for
PHP Annotations:
http://wiki.eclipse.org/PDT/Dev2Dev/Semantic
by adding an extension point like this:
extension
point=org.eclipse.wst.sse.ui.semanticHighlighting
highlighting
class=org.eclipse.symfony.ui.editor.highlighting.AnnotationHighlighting
target=org.eclipse.php.core.phpsource
/highlighting
/extension
I'm getting a ClassNotFoundException during startup for
org.eclipse.symfony.ui.editor.highlighting.AnnotationHighlighting,
although my plugin is exporting the necessary packages.
According to the eclipse irc channel, the way the
SemanticHighlighting extensions are loaded by the PDT plugin will
only work for internal pdt-bundle classes (in
SemanticHighlightingManager line 71).
Is this a bug in PDT or am i just not providing the extension
point correctly?
thanks!
-robert
___
pdt-dev mailing list
pdt-dev@eclipse.org mailto:pdt-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/pdt-dev
--
Thanks!
Best Regards!
Zhao
___
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] Provide type-hints for variables declared in different SourceModule
sorry for spamming the list, but there's really not much information in the
net available concerning PDT indexing.
I've followed the contributing to index chapter in the wiki
http://wiki.eclipse.org/Extending_PDT_2.2#Contributing_to_index
but i'm not sure if this is still up-to-date, because when i contribute
additional fields to a TypeDeclaration,
nothing appears in code assist for $this- in that class.
What confuses me is that a PDT Indexing Extension needs to subclass
PhpIndexingVisitorExtension
and provide declarationinfos using modifyDeclaration() calls.
However, the modifyDeclaration() method in the PhpIndexingVisitorExtension
is completely empty,
as apposed to the PhpIndexingVisitor which calls
requestor.addDeclaration(info) in this method.
The requestor is not available to extensions though.
My IndexingVisitor does basically the same like the one in the Wiki (inside
the endVisit(TypeDeclaration) method):
DeclarationInfo info = new
DeclarationInfo(IModelElement.FIELD,
Modifiers.AccPublic, start, length, start, length,
name,
null, null, namespace.getName(),
currentClass.getName());
modifyDeclaration(field, info);
Do i need to specify an implementation for the modifyDeclaration() method in
my indexer as well?
thanks!
-robert
2011/6/24 Robert Gründler r.gruend...@gmail.com
Hi,
a lot of PHP Frameworks implement the MVC pattern, and i'm wondering what's
the
best way to provide codeassist for PHP variables in files that have been
declared
in other SourceModules.
Let's say you have the class UserController with the method showUser() (in
/UserController.php)
... class declaration
public function showUser() {
$user = UserDAO::retrieveUserByID($id)**;
return array('showUser.php', array('user' = $user'))
}
The framework then renders the file 'showUser.php' and passes in the $user
object
as a variable named $user.
What i have done right now is the following:
1. In the SourceElementRequestor extension i visit the ReturnStatements of
methods in Controller
classes.
2. I detect the variables returned by that method and store it in some
custom Singleton.
3. Register a completionContext/Strategy which retrieves the correct
variables for the current php file from the Singleton.
This approach works, though it doesn't feel properly integrated into the
DLTK/PDT model, as
1. I'm simply storing the ViewVariable in-memory in my singleton, so after
Eclipse relaunches, the whole project needs to be rebuilt for completion to
work.
2. I'm getting ConcurrentModificationExceptio**ns in my Singleton class
during the BuildPhase as apparently the SourceParsing
takes place in multiple threads.
So my question is, is there a way to contribute those Variables which are
being passed to the View-Templates properly to the DLTK/PDT model ?
regards,
-robert
___
pdt-dev mailing list
pdt-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/pdt-dev
[pdt-dev] Provide type-hints for variables declared in different SourceModule
Hi,
a lot of PHP Frameworks implement the MVC pattern, and i'm wondering
what's the
best way to provide codeassist for PHP variables in files that have been
declared
in other SourceModules.
Let's say you have the class UserController with the method showUser()
(in /UserController.php)
... class declaration
public function showUser() {
$user = UserDAO::retrieveUserByID($id);
return array('showUser.php', array('user' = $user'))
}
The framework then renders the file 'showUser.php' and passes in the
$user object
as a variable named $user.
What i have done right now is the following:
1. In the SourceElementRequestor extension i visit the ReturnStatements
of methods in Controller
classes.
2. I detect the variables returned by that method and store it in some
custom Singleton.
3. Register a completionContext/Strategy which retrieves the correct
variables for the current php file from the Singleton.
This approach works, though it doesn't feel properly integrated into the
DLTK/PDT model, as
1. I'm simply storing the ViewVariable in-memory in my singleton, so
after Eclipse relaunches, the whole project needs to be rebuilt for
completion to work.
2. I'm getting ConcurrentModificationExceptions in my Singleton class
during the BuildPhase as apparently the SourceParsing
takes place in multiple threads.
So my question is, is there a way to contribute those Variables which
are being passed to the View-Templates properly to the DLTK/PDT model ?
regards,
-robert
___
pdt-dev mailing list
pdt-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/pdt-dev
[pdt-dev] Manipulating the PHPTokenizers grammar
Hi,
after receiving the correct JFlex.jar i managed to modify and compile
the PHPTokenizer.jflex
grammar into the PHPTokinezer Java class.
The tokenizing of the template languages structures is working by and
large, the plugin implementing
it can be found here:
https://github.com/pulse00/Twig-Eclipse-Plugin
However, there's some minor bugs which are related to the way the jflex
grammar has been extended, and
hopefully someone from the list can help me out.
The tokens of the templating language reside inside the XML content,
this is:
div
{{ template code }}
/div
My problem is that the rule for generic XML content of the grammar
always overrides my rule for opening Template tags:
// initial rule to go to the Template content state
// will always be overriden by the rule below, as it will always match more
// characters
YYINITIAL {{{Whitespace}* {
// switch to template content state
}
// initial rule to go to the XML content state
YYINITIAL [^%]*|[%]{S}+{Name}[^%]*|[%]{Name}([^;%]*|{S}+;*) {
// switch to xml content state
}
If the input to the tokenizer is only {{, then the first rule matches. But as
soon as there's any other
characters following ({{ foo), the second rule matches because the match is
longer - as described in the
jflex documentation.
It seems the authors of the original smarty plugin also had the same problem,
that's probably why they chose to
detect the opening template tags via a custom function (findTwigDelimiter):
Here's the code for it:
https://github.com/pulse00/Twig-Eclipse-Plugin/blob/master/org.eclipse.twig.core/Resources/parserTools/TwigTokenizer.jflex#L1951
Has anyone a hint how i can extend the PHPTokenizer in a way that the
opening template tags will always match - and not be matched
by the generic xml-content rule?
any hints would be greatly appreciated!
thanks,
-robert
___
pdt-dev mailing list
pdt-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] compile jflex grammar
Hi Roy,
thanks for your tips. As i'm still completely new to jflex, i think i'd
need to answer myself
a couple of questions to get this going.
At the moment i got a working plugin where i have simply ported the
tokenizer created by
the smartyplugin. This way, i got syntax highlighting and also the
CompletionProposalComputer
is calling my extension.
Now to the fun part:
I've had a look at how jflex is used in pdt. The build.xml in
Resources/parserTools works fine
and compiles all the Lexers and Scanners. There's one commented line
though, which unfortunately
is the one i need (at least i think) :
!-- Disabled automatic generation, since JFlex 1.2.2 is not available
for download --
!-- ant dir=${antfile.dir}/highlighting/
antfile=generatePHPTokenizer.xml / --
It seems that's exactly the file the smarty developer manipulated to
extend the syntax highlighting
in smarty templates:
http://code.google.com/p/smartypdt/source/browse/trunk/org.eclipse.php.smarty.core/src/org/eclipse/php/smarty/internal/core/documentModel/parser/devTools/SmartyTokenizer.jflex
When i uncomment the generatePHPTokenizer.xml, i'm getting the same
error like with the SmartyTokenizer.jflex:
Error: Incorrect skeleton file (wrong number of sections).
I've tried to alter the generatePHPTokenizer.xml to use the same targets
as the other ant builds, without luck.
So my main question is: How can i generate the PHPTokenizer:
org.eclipse.php.internal.core.documentModel.parser.PHPTokenizer ?
thanks for your help,
-robert
On 6/12/11 8:39 PM, Roy Ganor wrote:
Hi Robert, this is great news, thanks!
Actually I did it very long time ago, and since then several things (not too
much though) have been changed in the way we compile the flex resources.
My suggestion is to start with the current jflex (which is compatible with
1.4.3) and make the small changes to make twig/smarty support it.
Does this help or you need more leads?
Roy
-Original Message-
From: pdt-dev-boun...@eclipse.org [mailto:pdt-dev-boun...@eclipse.org] On
Behalf Of Robert Gr?ndler
Sent: Sunday, June 12, 2011 8:59 PM
To: PDT Developers
Subject: [pdt-dev] compile jflex grammar
Hi,
i'm trying to extend the php editor to support a templating language (twig).
There's a smarty plugin which does something similar:
http://code.google.com/p/smartypdt/
The authors have manipulated the .jflex grammar PDT uses to generate the
parser/tokenizer.
However, the skeleton files of in DevTools don't compile against the
current jflex version (1.4.3).
Anyone knows how to compile those .jflex files with a recent version of
jflex?
If not, is the old version (1.2.2) of jflex available somewhere in the
PDT repository? It seems the
binary isn't available anymore on the jflex page for that version.
regards
-robert
___
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] compile jflex grammar
Hi, i'm trying to extend the php editor to support a templating language (twig). There's a smarty plugin which does something similar: http://code.google.com/p/smartypdt/ The authors have manipulated the .jflex grammar PDT uses to generate the parser/tokenizer. However, the skeleton files of in DevTools don't compile against the current jflex version (1.4.3). Anyone knows how to compile those .jflex files with a recent version of jflex? If not, is the old version (1.2.2) of jflex available somewhere in the PDT repository? It seems the binary isn't available anymore on the jflex page for that version. regards -robert ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
[pdt-dev] Implement support for annotations
Hi, i'm working on a PDT extension for a php framework which uses annotations in PHPDocBlocks. An annotation basically has a similar syntax of a PHP class constructor: use Symfony\Component\Config\Annotations\Route; -- UseStatement /** * @Route(/, name=foo) // */ However, the parameters of the annotation do not match the parameters of the annotationclass, so if i simply report a FakeConstructor of the IType /Route/, PDT's code assist inserts the constructor of the class - which is not what i want. Is there a way to report a FakeConstructor in a CompletionStrategy where i can also define the parameters? My second question is about adding virtual elements to the structured model - so they can be displayed in the PHP Explorer. The framework i'd like to support has various structures defined in multiple sourcemodules: * Services ( a.k.a JavaBeans ) which are declared in XML/Yaml/PHP files * Routings - also declared in XML/Yaml/PHP files * etc ... To provide a better overview of all those structures in a project, i'm thinking about adding them to the project explorer - similar to the Deployment Descriptor of a Java EE project in eclipse: - IScriptProject -- sources -- PHP Language Library -- PHP Include Path -- Project Descriptor -- Services -- Service A -- Service B -- Routings -- Routing A Can this be done with an existing PDT/DLTK extension point? I guess the biggest problem is that the underlying sources are not SourceModules (XML/Yaml) of the PHP Language? regards -robert ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] Implement support for annotations
hi, thanks for the tip with the modelContentProvider extension, i'll take a look at this. Probably this will also solve my first question ;) regards -robert On 08.06.11 10:46, 赵忠伟 wrote: hi, I do not understand your 1st question for 2nd question,have a look at the following extension(but I am not sure if it is what you want): extension point=org.eclipse.dltk.ui.modelContentProvider modelContentProvider id=org.eclipse.php.ui.modelContentProvider language=org.eclipse.php.core.PHPNature class=org.eclipse.php.internal.ui.provider.PHPModelContentProvider/ /extension 2011/6/8 Robert Gründler r.gruend...@gmail.com mailto:r.gruend...@gmail.com Hi, i'm working on a PDT extension for a php framework which uses annotations in PHPDocBlocks. An annotation basically has a similar syntax of a PHP class constructor: use Symfony\Component\Config\Annotations\Route; -- UseStatement /** * @Route(/, name=foo) // */ However, the parameters of the annotation do not match the parameters of the annotationclass, so if i simply report a FakeConstructor of the IType /Route/, PDT's code assist inserts the constructor of the class - which is not what i want. Is there a way to report a FakeConstructor in a CompletionStrategy where i can also define the parameters? My second question is about adding virtual elements to the structured model - so they can be displayed in the PHP Explorer. The framework i'd like to support has various structures defined in multiple sourcemodules: * Services ( a.k.a JavaBeans ) which are declared in XML/Yaml/PHP files * Routings - also declared in XML/Yaml/PHP files * etc ... To provide a better overview of all those structures in a project, i'm thinking about adding them to the project explorer - similar to the Deployment Descriptor of a Java EE project in eclipse: - IScriptProject -- sources -- PHP Language Library -- PHP Include Path -- Project Descriptor -- Services -- Service A -- Service B -- Routings -- Routing A Can this be done with an existing PDT/DLTK extension point? I guess the biggest problem is that the underlying sources are not SourceModules (XML/Yaml) of the PHP Language? regards -robert ___ pdt-dev mailing list pdt-dev@eclipse.org mailto:pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev -- Thanks! Best Regards! Zhao ___ 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] No code assistance for PHP Language Library
thanks a lot! Installing the h2 stuff solved the problem.
regards
-robert
On Mar 4, 2010, at 1:22 AM, 赵忠伟 wrote:
I have the same problem long ago!
Do you checkout the following two plugins?
org.eclipse.dltk.core.index.sql,org.eclipse.dltk.core.index.sql.h2
And you have to download h2 database in you eclipse plugins directory:)
On Thu, Mar 4, 2010 at 5:32 AM, Robert Gruendler rob...@dubture.com wrote:
some more info:
the root for that exception seems to be in
org.eclipse.dltk.internal.core.index2.IndexerManager, line 47:
IConfigurationElement[] elements =
Platform.getExtensionRegistry()
.getConfigurationElementsFor(INDEXER_POINT);
The elements Array is empty, so the indexer field is null.
regards
-robert
On Mar 3, 2010, at 10:10 PM, Robert Gruendler wrote:
i was looking at the .log file of the workspace which doesn't have code
assistance,
and i'm getting this exception everytime i trigger code assistance:
!MESSAGE PHPCore plugin internal error
!STACK 0
java.lang.NullPointerException
at java.util.Arrays$ArrayList.init(Arrays.java:3357)
at java.util.Arrays.asList(Arrays.java:3343)
at
org.eclipse.php.internal.core.codeassist.strategies.GlobalTypesStrategy.getTypes(GlobalTypesStrategy.java:120)
at
org.eclipse.php.internal.core.codeassist.strategies.GlobalTypesStrategy.apply(GlobalTypesStrategy.java:74)
at
org.eclipse.php.internal.core.codeassist.strategies.GlobalElementsCompositeStrategy.apply(GlobalElementsCompositeStrategy.java:43)
at
org.eclipse.php.internal.core.codeassist.PHPCompletionEngine.complete(PHPCompletionEngine.java:89)
at org.eclipse.dltk.internal.core.Openable$1.run(Openable.java:494)
Seems like the code assistance is activated, and the reason for no code
assistance is an internal exception.
Another thing that points into that direction is that code assistance isn't
working at a project scope, ie:
public class Foo {
protected $bar;
public function test() {
$this- --- triggers the exception too.
}
}
regards
-robert
On Mar 3, 2010, at 4:56 PM, Robert Gruendler wrote:
is there any temporary workaround to re-activate the code assistance for
the language library ?
regards
-robert
On Mar 3, 2010, at 3:47 PM, Roy Ganor wrote:
Hi Alex, I see that Mylyn-DLTK bridge plugin is the only one that plays
with these preferences. Probably for wrapping things with its own
proposals list.
Anyway, the unpleasant situation where empty proposals list is shown
should be fixes somehow.
Thanks!
Roy
From: pdt-dev-boun...@eclipse.org [mailto:pdt-dev-boun...@eclipse.org] On
Behalf Of Alex Panchenko
Sent: Wednesday, March 03, 2010 4:30 PM
To: PDT Developers
Subject: Re: [pdt-dev] No code assistance for PHP Language Library
JDT has preference page to manage them, DLTK uses preferences but without
preference page.
Actually I couldn't find the code changing it, but I remember once it was
somehow disabled in my development workspace.
Regards,
Alex
- Original Message -
From: Roy Ganor r...@zend.com
To: PDT Developers pdt-dev@eclipse.org
Sent: Wednesday, March 3, 2010 8:19:00 PM GMT +06:00 Almaty, Novosibirsk
Subject: RE: [pdt-dev] No code assistance for PHP Language Library
BTW, any reason why a user would select to disable the script category?
You mentioned on exception but it seems odd to me that it is common.
Are there other situations where this category can be disabled?
Thanks!
Roy
From: pdt-dev-boun...@eclipse.org [mailto:pdt-dev-boun...@eclipse.org] On
Behalf Of Alex Panchenko
Sent: Wednesday, March 03, 2010 3:54 PM
To: PDT Developers
Subject: Re: [pdt-dev] No code assistance for PHP Language Library
Hi,
It's possible that PDT proposal computer was disabled in preferences (e.g.
if exception was thrown), so it makes sense to test in a *new* workspace.
Regards,
Alex
- Original Message -
From: Roy Ganor r...@zend.com
To: PDT Developers pdt-dev@eclipse.org
Sent: Wednesday, March 3, 2010 7:56:24 PM GMT +06:00 Almaty, Novosibirsk
Subject: RE: [pdt-dev] No code assistance for PHP Language Library
Hi Robert,
Can you share your .settings folder, .buildpath and .project files?
Best regards,
Roy
From: pdt-dev-boun...@eclipse.org [mailto:pdt-dev-boun...@eclipse.org] On
Behalf Of Robert Gruendler
Sent: Wednesday, March 03, 2010 2:08 PM
To: PDT Developers
Subject: [pdt-dev] No code assistance for PHP Language Library
Hi all,
i don't get any code assistance for the php language library in php
projects.
The only assistance that shows up,are the template proposals, like
try/catch, fn etc.
My PDT extension is completely disabled in the run environment, and i've
tested this
bug also on a standalone eclipse installation with the latest pdt 2.2.
Version Info:
Eclipse: 3.5.2 Build id:
Re: [pdt-dev] Unable to open editor
this is what's listed under Installed software: PHP Development Tools (PDT) Runtime Feature 2.2.0.v200912030932-7L7J-F8NcJKhTcJmKhmcorg.eclipse.php.feature.group How can i determine the build number? On Feb 15, 2010, at 9:19 AM, Roy Ganor wrote: Did you use build #129? https://build.eclipse.org/hudson/view/Athena%20CBI/job/cbi-pdt-2.2-helios/129/ Roy From: pdt-dev-boun...@eclipse.org [mailto:pdt-dev-boun...@eclipse.org] On Behalf Of Alex Panchenko Sent: Sunday, February 14, 2010 7:31 PM To: PDT Developers Subject: Re: [pdt-dev] Unable to open editor Hi Robert, There were API changes in DLTK last week, that's why previous PDT builds don't work. I think next PDT build should be OK. Regards, Alex - Original Message - From: Robert Gruendler rob...@dubture.com To: PDT Developers pdt-dev@eclipse.org Sent: Sunday, February 14, 2010 11:12:31 PM GMT +06:00 Almaty, Novosibirsk Subject: [pdt-dev] Unable to open editor Hi all, i'm using pdt 2.2 and dltk 2.0 in eclipse 3.5. After updating dltk to the latest version, i cannot open php editors anymore. I've filed a bug report with the full stack trace here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=302801 Should the current pdt version from http://download.eclipse.org/tools/pdt/updates/2.2/interim/ work with latest dlkt version? Thanks -robert ___ 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] Eclipse Symfony
we're a group of 3-4 people who started with an eclipse symfony plugin about half a year ago, unfortunately it seems most of us are too busy with other projects to continue the development. If you're interested in jumping in, here's the sourceforge project site: http://sourceforge.net/projects/sfdt/ best -robert Am 12/6/09 6:08 PM, schrieb roberto german puentes diaz: Is possible, a integration between, Eclipse and Symfony like, netbeans 6.8 or PHPEdit have ? Other topic is, PHP and some tool for reports... do you say BIRT ? :D Any suggestions? -- Cr. Puentes Diaz MP 10.12726.9 Córdoba - Argentina www.puentesdiaz.com.ar/blog/ http://www.puentesdiaz.com.ar/blog/ www.puentesdiaz.com.ar/blog/novedades http://www.puentesdiaz.com.ar/blog/novedades www.twitter.com/puentesdiaz http://www.twitter.com/puentesdiaz Linux User n° 441474 Ubuntu/Symfony/Eclipse Rocks! Sign for Free License for Project Zero http://www.petitiononline.com/zerogpl/ ___ 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] Ctrl + Click on String Scalars
Hi all,
i was looking at the CTRL + click example using the phpIndexingVisitors
extension point, and i'm
wondering if it's possible to add CTRL + click support for String
Scalars, ie Arguments to methods:
ClassRegistry::init('MyClass');
In this case, i would like to open the SourceModule containing the type
'MyClass' when CTRL-clicking
on it.
Anyone knows if this should be possible ?
thanks !
-robert
___
pdt-dev mailing list
pdt-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] extending PDT 2.2
thanks a lot for this very useful wiki entry! -robert Am 12/1/09 2:47 PM, schrieb Michael Spector: I've added links to this documentation to the schema. On Tue, Dec 1, 2009 at 3:27 PM, Roy Ganor r...@zend.com mailto:r...@zend.com wrote: Hi, It will be great if this (or parts of this) information will be inserted into the schema files as well? Thanks! Roy *From:* pdt-dev-boun...@eclipse.org mailto:pdt-dev-boun...@eclipse.org [mailto:pdt-dev-boun...@eclipse.org mailto:pdt-dev-boun...@eclipse.org] *On Behalf Of *Michael Spector *Sent:* Tuesday, December 01, 2009 3:00 PM *To:* PDT Developers *Subject:* [pdt-dev] extending PDT 2.2 Hi All, I've added some documentation on how to extend PDT 2.2: http://wiki.eclipse.org/Extending_PDT_2.2 Please report any suggestions or questions you have. Best regards, Michael ___ 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 ___ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
Re: [pdt-dev] Getting cursor position in current editor
thanks, got it working using the ITextSelection. -robert Am 11/19/09 2:04 AM, schrieb 赵忠伟: it seems that you can get the cursor position from current ISelection.if you does not select anything and the ISelection is instanceof ITextSelection,you can see ITextSelection.getLength() return 0,and ITextSelection.getOffset() is the cursor position. ___ 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] add method to class
Thanks a lot! Am 06.07.2009 um 07:27 schrieb Roy Ganor r...@zend.com: Hi Robert, You can find full documentation for AST manipulation here: http://www.eclipse.org/pdt/articles/ast/PHP_AST.html take a look at our unit tests to see what is the right way for doing this for the different types of elements - http://bit.ly/Bnl9q. Regards, Roy From: pdt-dev-boun...@eclipse.org [mailto:pdt-dev- boun...@eclipse.org] On Behalf Of Robert Gruendler Sent: Sunday, July 05, 2009 11:25 PM To: PDT Developers Subject: [pdt-dev] add method to class Hi all, could someone give me a hint how i can add a method to a class and make it visible in the editor ? So far, i've tried the following: sourceModule.becomeWorkingCopy(null, null); classDeclaration.getBody.addStatement(myNewMethod); // classDeclaration is child of the sourcemodule sourceModule.reconcile(true, null, null); sourceModule.commitWorkingCopy(true, null); Do i need to alter the IBuffer of the sourcemodule manually for this to work ? thanks ! -robert ___ 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
