object-mapping (something I never ever saw :) ) |
Site Admin
|
why not to just add /** @var dblayer */ before first usage of $dblayer?
For further info, please read TypeHints: http://forum.nusphere.com/tip-type-hints-t1563.html |
||||||||||||
_________________ The PHP IDE team |
|
That's a good hint, thank you. But please note that in this case it cannot solve my problem. My objects are included and construct on the fly, I don't know when I use them. And the biggest problem: I have an index.php that has 1 include() and after that when initializing it dinamically loads any needed files. And because of this method I if I'm editing the mod_guestbook/classes/guestbook.php file, inside that I have no include or require on anything, because it is not needed. So I have to do the typehinting for all my PHP files... Or maybe I must have misunderstood something or blind not to catch up Your idea... Thanks! |
||||||||||||||
|
Site Admin
|
with default settings, PhpED does not care if you have just one include, none or many. What makes sense for Code Insight is list of all classes available in the project. So if you type /** @var classname */, Codeinsight will scan the class list until it finds classname. It does not matter if corrsponding script is included at all.
|
||||||||||||
_________________ The PHP IDE team |
|
Oh, btw, dmitri,
as you mentioned, phpEd scans project tree for all php files, to find apropriate class for object, etc. But, I have situation, where in the same project but diferrent deep levels or dramaticaly different directories, there are some files with the same class name defined, but whole diferrent code inside. "Why?" you'd say, lets take example, that the same project has admin and client sides, so every side needs for my case diferrent class'es, as phpEd goes trought my project filelist only first class is defined, and clientside classes are left out of sign. How could I solve this problem without renaming class names? Bye |
||||||||||||
|
Guru master
|
The dual versions is a problem I have here as well. Both for functions and for classes. Just wanted to mention it
|
||||||||||||
|
Site Admin
|
well, you have "admin" and "user" area. If they contain similar classes that have the same names, why don't you work with them through two different projects in one workspace?
|
||||||||||||
_________________ The PHP IDE team |
|
You see, dmitri, it's possible, of couse, but a bit annoying . Because, logically it's the same project, not two different .
In my opinion this is optional feauture, but the good one . Bye |
||||||||||||
|
Site Admin
|
if it is the same project, why does its class hierarchy have clashes (name conflicts)?
|
||||||||||||
_________________ The PHP IDE team |
|
Imagine situation:
admin site (/admin directory) has libraries (classes) in it, where template, session handler and other classes sits, class names 'template', 'session', 'page' etc. client side (/client directory) has the same class names, but whole diferrent logic inside, why should I rename class names for every x-side... The point in this is - admin and client side +- has almost the same logic, but libraries part for both sides for my situation has to have same method, class names, but different logic inside with several unique methods etc.. So there comes phpEd class name overrides, that are very annoying. Bye |
||||||||||||
|
Site Admin
|
After all, you have two libraries and two areas (admin + user) where those two libraries are used, I see no connection in between the two. Why not to develop them as two projects? Say you have class named SessionHandler in both libraries. How any tool on the Earth would guess what libriry is the source of it until it have your code executed? Please note: executing code is not an option for the Code insight.
|
||||||||||||
_________________ The PHP IDE team |
object-mapping (something I never ever saw :) ) |
|
||
Content © NuSphere Corp., PHP IDE team
Powered by phpBB © phpBB Group, Design by phpBBStyles.com | Styles Database.
Powered by
Powered by phpBB © phpBB Group, Design by phpBBStyles.com | Styles Database.
Powered by