[news.eclipse.tools.pdt] Re: No autocompletion - even with simple code

[roy@xxxxxxxx (Roy Ganor)]

Great stuff! I am sure we will be able to direct people to this method 
when they meet code assist issue.

The next wiki page summarizes the pdtt method, including how to create and 
submit a pdtt test - 
http://wiki.eclipse.org/PDTT_-_PHP_5.3_Code_Assist_Tests

BTW - can we change the "type" element to "namespace" when the type is 
really a namespace? I think that most users will not understand it.

Thanks!
- Roy


Michael Spector wrote:


> Hi Ingo,

> This is a message not just for you but also for all who is willing to help 
> PDT project.
> I'll appreciate if you attach a unit test for code assit bug to the bug 
> report. Here are the instructions:

> 1. The unit test file must end with ".pdtt" extension

> 2. Unit test format is the following:

> --TEST--
> Test description
> --FILE--
> <?php
> File contents. Put '|' character where you suppose to call the code assist.
> ?>
> --EXPECT--
> Expected output

> 3. Expected output is a list of: type(A), method(A), field(A) or keyword(A) 
> entries, where A is an element name and 'type', 'method', 'field' or 
> 'keyword' are element types:

>     a) 'type' refers to class, interface or namespace
>     b) 'method' refers to method or function
>     c) 'field' refers to variable or constant
>     d) 'keyword' refers to a PHP keyword or PHPDoc tag.

> 4. Example:

> --TEST--
> Test whether code assist of class instantiation works (bug #12345)
> --FILE--
> <?php
> class MyClass1 {}
> class MyClass2 {}
> $a = new MyCl|
> ?>
> --EXPECT--
> type(MyClass1)
> type(MyClass2)

> More examples can be found here: 
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.pdt/tests/org.eclipse.php.test/workspace/codeassist/?root=Tools_Project

> Thanks for your help!

> Best regards,
> Michael


> "Ingo Renner" <ingo@xxxxxxxxx> wrote in message 
> news:gnef7s$dsn$1@xxxxxxxxxxxxxxxxxxxx
> > Michael Spector wrote:
> >
> > Hi Michael,
> >
> > > Can you report a bug?
> >
> > sure, will do. Is there anything I could attach that could help you find 
> > out what's going on / that could be of help to reproduce the issue? Any 
> > logs or so?
> >
> >
> > best
> > Ingo