
Windows installer version: pliant-100b windows installer.
For linux and newer windows versions please consult http://hc.fullpliant.org/doc/install/index.
If you are installing on Windows just run the provided installer.
Important: You can not pick an arbitrary directory to install pliant. When prompted for install path, the default will be "c:\pliant". You may change the drive letter (for example "d:\pliant") but don't change the path.
The recommended way is to use the windows installer. However, if you choose to install from scratch from a zip file, unzip the file into either "c:\" or "d:\" or any other drive-letter root. Suppose you decided to use "c:\pliant", the default location. After uncompressing, you will have directories "c:\pliant", "c:\pliant_data" and "c:\pliant_security". Create a shortcut on your Desktop to "c:\pliant\fullpliant" and execute it. Nothing will open right away, but don't worry, pliant is compiling its core modules. You can see that its working Task Manager's Process tab. In about a minute or two a Pliant UI window will open.
At this point you are set up to run the integrated development environment, which is the recommended way to develop pliant programs. However, should you choose to run pliant from command line, copy c:\pliant\binary\pliant-debug1.exe to c:\pliant\binary\pliant.exe (already done by windows installer) and add c:\pliant\binary to your PATH.
For Linux, untar the tarball to filesystem root:
$ tar xzvf pliant-latest.tgz -C /
This will create directories /pliant, /pliant_data and /pliant_security on your filesystem root. If you don't like to install into filesystem root, you may also install into your home directory.
$ tar xzvf pliant-latest.tgz -C $HOME
In the following discussion lets assume it was uncompressed into root directory /. If you installed elsewhere, modify instructions accordingly.
In any case, after uncompressing the archive, you must execute the /pliant/fullpliant executable.
$ /pliant/fullpliant
Create a symlink to /pliant/binary/pliant-debug1.exe from /usr/bin/pliant
$ ln -s /pliant/binary/pliant-debug1.exe /usr/bin/pliant
The purpose of this command is twofold:
If you happen to install pliant on a remote server it is highly recommended to setup a vncserver session for the purposes of initial configuration via pliant client ui. If you can't do that read some tips on pliant Wikia page. After you have completed configuration, you should disable the ui client from executing. To do this, create the file (and leading directories) "/pliant/custom/universal/pliant/fullpliant/run.pli" and place into it the following code,
custom auto
constant auto_ui true
constant auto_http true # or false, up to you
constant auto_console false
Pliant is an English word that means: bending readily; flexible; supple; adaptable.
Just like with scripting languages, no Makefiles, Ant build files, or configure.sh scripts are needed. Pliant compiles from source code, and resolves all dependencies automatically.
Not always, but most of the time, theres no need to restart the pliant ui server: with a press of a button you can recompile changes in Pliant UI code.
Meta programming is the most unique and original feature in Pliant. It gives the ability to add new syntax to the language.
Just like Adobe AIR, Pliant UI Client is a program you install locally on your computer in order to use client-server application with advanced features.
Copyright © 2008 Pliant Software Solutions | All Rights Reserved
Website powered by Pliant. Contact:
Connection to the server is suspended.
Please press the Continue button to resume.