This folder contains a sample PHP project in the "MyProject" folder, and several ionCube PHP Encoder Project

(.iep) files. You can open a project file in several ways: 1) double clicking the .iep file 2) right clicking in Explorer and selecting 'Encode Project' 3) starting the PHP Encoder GUI and opening the project file from there. The project files demonstrate the use of various features described below. Each project file encodes the "MyProhect" source project folder into the "encoded-projects" target folder in the examples folder. * example1.iep Encode "MyProject" into "Encoded-Projects". All .php and .inc files are encoded except for config/config.inc "LOCAL README.txt" is ignored. * example2.iep As example1, but adding comments to the start of the encoded files, locking files to IP 192.168.1.1, and giving files a time expiry of 2 hours. If you have opened the project in the main GUI, click project settings (F7) and explore the options to see where these features have been set. After encoding, press F9 to open Explorer on the target folder. Notice that the encoded PHP files have a different icon to non-encoded PHP files (unless the dynamic icons feature was unchecked when installing the Encoder). If you open one of the encoded files with your preferred editor for PHP files, notice too that there are custom comments at the start of the encoded file. * example3.iep (Requires Special Edition GUI) As example2, but this time creating a target zip archive and deleting the target folder. This is a feature of the Special Edition GUI, and is useful if you want to package up your encoded project for distribution. On the target panel of the project settings (F7), note too the FTP options. These are another feature of the Special Edition GUI, and can be set if you wish to ftp either the target folder or target archive to a remote machine. * example4.iep (Requires Special Edition GUI) This example shows some more features of the Special Edition Encoder GUI, with the dynamic customisation feature. When you open the project file, notice how a new panel appears in the window with fields prompting for input. Entering values into the fields before pressing the Encode button will customise the settings for that encoding. Explore the project settings and see the use of "?" in fields that can be customised, and also the use of variable expansion in the text header text field (on the Customisation tab in project settings). This powerful feature allows easy customisation of fields that may change for each encoding, and without the need to edit project settings.

In so doing, user interraction is greatly simplified, sped up, and much less error prone. Also try right clicking on the example4.iep project file and selecting "Encode Project". The simple "auto-encoder" interface is also customised to prompt for the custom fields contained in this project. * example1-ipf.iep (Requires Package Foundry full or evaluation) This project is setup almost the same as example1, but after this project is encoded, the Package Foundry (IPF) will be run to create an installer package from the encoded files. When run, the installer setup.exe program that is create d will install the encoded project onto a local or remote web server. Copyright (c) ionCube Ltd. 2002-2010