Class Autoloading suggestion and some other suggestions as wll

We have been trying VS.php for some days now and it is really one of the best PHP IDE's out there (we tried several): we are considering getting a couple of licenses.

However, there are some points we think could be improved .Since the developers seem to actively read these forums and seem to really do something with the feedback, we are posting them here.

Class AutoLoading / Intellisense resolving

In our projects we are using the de-facto standard Pear/PHP auto-loading scheme: the class Just_Some_Class is found in the file Just\Some\Class.php (underscores are replaced by directory seperators).
The current method only allows %s to be replaced with the classname: replacing underscores with directory seperators would be a welcome addition.

An option to auto-parse all project files on start would be a welcome addition also.

Remote Project

When using a remote project, the file dialogs only allows to select one file at a time, as opposed to the default VS dialog which we'll get in a local project. It would be great to be able to select multiple files over SFTP. Selecting directories to 'add as a reference' / 'add to project' would be great also.

Remote debugging

The mapping of remote files with breakpoints to files inside a project is not really working well always. For example, we are using a chroot'ed apache on our development machines which seems to conflict with the directory/filenames in the project somehow.

Suggestion: allow a remote-debugging-path to be set for a project; The files in a project can than be fully translated into pathnames on the remote machine. The relative filenames in the project can then be prepended with the remote-debugging-path and thus breakpoint-notifications from xdebug can be much easier resolved.

Another great feature would be to allow debugging to be done without launching the browser. The reason for this is that we do most debugging thru commandline scripts on the development machine, but we would still like to use breakpoints and step the code from within vs.php.

From all these suggestions, we would think that the Pear/Zend style class autoloading (My_Class -> My/Class.php) and the remote-debugging-path for projects are the two most beneficial for all users and would solve most problems people have with auto-class loading and remote-debugging.

Comments

    Very good ideas

    Very good ideas indeed!

    Thanks