PHP PORTABLE IDE: Introduction: Difference between revisions

* Portable run from UDB memory stick

It transpires this user was learning PHP and wanted an easy way to run code snippets. Reason for running from a USB stick, he/she did not want to install PHP and a full-blown IDE on their PC.

My reply was, use Notepad++ install the NppExec plugin add core binaries from PHP. To run currently displayed script write a small NppExec command script. You can create a shortcut key that runs this command script. For greater flexibility consider adding XDebug which will allow you to debug both CLI and server side scripts.  

Response was not unexpected! "''Can you supply a complete idiots guide''?"  

This guide is split across several pages each page builds on previous pages to construct the final IDE. Pages and topics covered are as follows:

* How to [[PHP PORTABLE IDE: NppExec Configuration#Copy and Paste (console window) | copy and paste]] in console window.

This page shows how to enable PHP extensions in the CLI configuration and ensure correct file is being picked up.

* Running CLI scripts the PHP interpreter needs to know [[PHP PORTABLE IDE: PHP extensions#Update NppExec command script |what configuration file to use]] also true when run via a command script.

* Checking correct configuration file is being picked up you can put a [[PHP PORTABLE IDE: PHP extensions#PHP configuration file - php_cli_ide.ini | dummy line]] in the configuration file to produce an error or use the [[PHP PORTABLE IDE: PHP extensions#PHP INFO | PHP info function]].       

* Generally when a file is double clicked you expect that file to be run with the correct application. Interestingly this can lead to some confusion especially for PHP files see [[PHP PORTABLE IDE: PHP extensions#Double clicking PHP file problem | Double clicking PHP file problem]]

* Want to preserve file associations for example .php is associated with a PHP editor and you want to run that script on a server when double clicked use a [[PHP PORTABLE IDE: PHP extensions#PHP CLI redirect script | redirection file]]!   

This page looks at automating functionality using Notepad++ menu system.

* After editing a PHP script it is advisable to run a [[PHP PORTABLE IDE: Run Menu#PHP Syntax check | syntax check]]. This functionality is assigned to a menu item.

* Similarly running a [[PHP PORTABLE IDE: Run Menu#Run PHP web page on server | page on a local web server]] is assigned to a [[PHP PORTABLE IDE: Run Menu#Edit Notepad++ file shortcuts.xml | menu item]]. This runs a [[PHP PORTABLE IDE: Run Menu#PHP CLI redirect script | PHP script]] that indirectly (via a browser) runs a script on a local server. A server may be configured to pass files with any extension hence the PHP redirection makes no distinction.  

* Our IDE requires both console and debugging windows to be open however there is an issue when these are docked [[PHP PORTABLE IDE: Notepad++ XDebug 1#Docking Problem | solution]] is to undock them.

* Interested in tracking a small number of variables then add them as [[PHP PORTABLE IDE: Notepad++ Debugging 1#Watches | watches]].  

* Notepad++'s integrated console window may be of limited use for your application alternative is to use an [[PHP PORTABLE IDE: Notepad++ Debugging 1#Alternative Console Window  | external cmd window]] for debugging.   

* Again majority of material seems to be Linux orientated hence a quick [[PHP PORTABLE IDE: Notepad++ XDebug 2#Overview | overview]] for Windows users

* At this stage you will have noticed duplication between pages XDebug 1 and XDebug 2 this is intentional see [[PHP PORTABLE IDE: Notepad++ XDebug 2#Important Commonality | Important Commonality]].  

* Recap example. Debuggining initiated useing a browser and from Notepad++

After reading this design tutorial why not download either the finished Portable IDE or Plugin.