Hi

I am testing phped at the moment and so far i like this IDE

One question:

In my Projects I use something like
(relative pathnames work local but they wouldnt fit the filestrucure on the server - due to symlinks)

Unfortunately phped (and no other IDE i tested so far) can understand this.

Is there any way to close this gap? For Instance an option in the project settings where you can assign a value for $path_to_class for local function insight. Would be great!

greetings
b

phped 3.3 update pack #2 will come with a good sulution for this situation.

Has this been implimented? What is the work around?

I to work on files like this and code insite for my classes is broken

sure. It is implemented.
You can open project properties and add include path to let code insight engine to look into different directories for the sources.

Thanks!

This is the one hang up that was keeping Zend Studio installed.

What is the good solution you have implemented here?

Using only the filename from the include and search it in the whole project?

This is not enough (se this thread: code-completion-for-project-code-snippet-search-t1096.html#5015#5015)

and besides, what happens if I have the following structure:
/index.php
/core/functions.php
/libraries/functions.php
/custom/functions.php

and in index.php I write:


will it see all functions defined in both files?

You need to add a feature then to automatically "build" the include list recursively for an entire project tree. Then all our woes would be solved

This is already implemented in 3.3 update 3 and the list for whole the project is built automatically , what you need to add into that list is the list of directories OUT of the project tree if you have them of course.

ddmitrie, sweet, thanks so much. will grab update 3.

sure, example code-completion-for-project-code-snippet-search-t1096.html#5030#5030 won't be autocompleted in 3.3.3 w/o a little code modification. A workaround is to add require_once "b.php"; on the first line of b.php.
As of the "g" list I meantioned before, it's working to help code insight in finding files throught the project and directories in include_path.

But it still does not build up whole-the-project list of classes. It would require too many changes in 3.3. Next version's code explorer is better suited for this task. In other words, the improvement will come with the next version.