PHPEd is wonderful product. This features may make it even better

1) PHPdoc should look like this



but when I type /**, I get this (without spaces):



(and what about code completion for PHPdoc, popup with @desc, @param, @author,... and help)

2) Run to cursor (F4) command is available only in debug mode. If I want to start debuging from current line, I must press F9, than focus moves to the first line, so I must find the "current" line (or file) and press F4. Sure, it is possible to mark the line as breakpoint (F5) and press F9 & F9, but single F4 is better, isn't it?

3) Possibility to change hidden characters color (or/and style, see Aptana). Gray or silver may be better.

Seconded. Actually, what you get now iswith no spaces whatsoever.

Please change this to a properly aligned comment.

Since peoples expectations for how the completion should work varies a lot, I think it is best to let them implement it themselves with templates and macros. I am using a PHP program to auto generate a suitable Doc comment from the selected class or function definition. Given thisfor instance, it would generate this commentwhere you then fill in the blanks. The code for this is available in a previous thread somewhere.

right, but what if you need to start debugging in file b.php and main file is a.php which includes b.php?
If F4 was enabled, you would be confused by the IDE which would certainly run b.php as a main file


they are colored as White Space/foreground color, actually. So you can change it.

Why run b.php? Run main file and goto to current line in b.php. PHPed is written in Borland IDE, right? Try this behaviour there - put cursor on any line in any file and press F4.



Thank you!

add one more line where you want to stop:
debugbreak();
this solves your problem. this is the most powerful function for me, always works.

regards.

If it was C, we would look for main() function and run it , but it's php and it's unknown what to run.


Right, but F4 has one little advantage - you don't need to modify code. By modifying code you add just two problems
a) you may forget and push a file with this call into production server b) if you debug on a production or development server (it happens sometimes), such calls may interfere with clients or other developers respectively.

Probably you don't understand me. The requested feature is: to act [F4] exactly like sequence [F9] + [F4], when debugging is off. Pressing [F9] & [F4] is unconfortable due one problem: after pressing [F9] I lost focus so I must scroll window (very annoying) or select previous tab by Ctrl-TAB (when default file is defined). That's all.

Sorry if I didn't make it clear enough before.

With F9 + F4 sequence you normally do the following:
Run file A.php (say it's the main file) then open file B.php, scroll to the line of interest and press F4.
How would IDE do everything for you at once?

Say, I've enabled F4 when debugger is not started. You open B.php, scroll to the line, press F4 and
for sure IDE will start B.php instead of A.php.

Is it a bit clearer example?

Yes, it's exactly what I except. When I press F4 on B.php and default file of project is not defined, IDE should start debuging file B.php. That's right. If I'd like to start with A.php, I must use F9 or define defalt project's file.

But there is big advantage. When I am debuggin only one file (1) or project with defined default file (2), I don't have to find losted "current" line (1) or current tab (2) every time I press F9.

okay. I agreed

It will be nice to fix this

Thanks.