Technical FAQ
PHP Manual
CSS2 Manual
HTML Manual
JS Guide
JS Reference
PhpDock Manual
Nu-Coder Manual
PhpExpress Manual
PHP Joomla
Learn PHP
Last updated: Sat, 01 Jan 2011

User Guide Notation

This section explains certain syntax conventions used in this User Guide.

Command Examples

Command line text in the User Guide is printed in monospace bold font.
Command examples are printed in the form:
nu-coder.exe [options] source-directory target-directory
or to illustrate command usage and output, as
prompt> nu-coder -v
NuSphere PHP Encoder Nu-Coder 3.0.0 Copyright (c) 2005-2011 NuSphere Corp.
Or similar with License Manager
prompt> nu-licgen -v
NuSphere Nu-Coder license generator 3.0.0 Copyright (c) 2005-2011 NuSphere Corp.

Shell input is shown in bold, and program output is plain. prompt> is an example shell prompt for command entry but this may be different on your own system.

Nu-Coder and PhpExpress support for PHP 4 and for PHP 5

Nu-Coder and PhpExpress difference

Nu-Coder supports encoding of the scripts written in PHP versions 4.3, 4.4, 5.0, 5.1, 5.2 and 5.3. PHP scripts written on earlier versions of PHP and encoded with Nu-Coder can also be deployed on any later version of PHP interpreter with the help of PhpExpress. Unlike many other PHP Encoders, Nu-Coder can encoder PHP files with special provisions for intermediate versions with the use of -c parameter. For example using php encoder with option -c 5.1 will result in encoding taking in account special features available in PHP 5.1 and not just PHP 5.0

Examples used in this User Guide

The PHP version of the script being encoded with Nu-Coder can be specified by passing -c parameter followed by version number to Nu-Coder Command Line Interface. For example, the following line will invoke the encoding for PHP 4.3 script file.php, storing the output in the file file_enc.php:
nu-coder.exe -c 4.3 file.php file_enc.php
-c is not a required parameter, if omitted the script will be encoded with PHP 5.1.
For simplicity in this document we will omit -c parameter in the most of the examples. Therefore these examples will illustrate how the program should be used if encoding a PHP 5.1 project to ensure that your encoded scripts will run on PHP 5.1 servers. If the project is on a different version of PHP, the -c parameter should be used explicitly to specify the version to the Encoder.

Typical usage of Nu-Coder encoder and license manager

In a typical scenario your files will be encoded on same machine where you do PHP development, i.e. Windows box. You will be able to encode PHP files using Graphic User Interface on the same machine with Nu-Coder. Encoded files are usually packaged and placed on the server from where they can be downloaded by your customers for either evaluation trial or purchase.

Please note that if you are using NuSphere PhpED - PHP IDE you can also encode PHP files using PhpED interface to Nu-Coder.

However, the License files usually need to be generated on the server at the time when the customer's request to download is received. For this purpose NuSphere supplies License Manager for all major platforms, including *BSD/x86 and x86_64, Linux/x86 and x86_64, Windows, Solaris/x86, x86_64 and Sparc. There are two the most commonly used ways to generate the license:
  • License that expires after certain time interval or on certain date - typically used for trial versions and demos
  • License that doesn't expire in time but only allow execution of PHP scripts on certain identified hardware or on specified IP address or network segment
Please consult this manual for the ways to load, work and do the error handling of the Licenses generated by Nu-Coder's License Manager.

Last updated: Sat, 01 Jan 2011