Difference between revisions of "Wgraph:Installation"

Revision as of 15:35, 22 July 2007

For a full installation of wgraph you must:

• Download the Semeb sources and move the 'Wgraph' directory (note the capital 'W') to 'yourWiki/extensions'.
• verify if the built-in mechanism in Wgraph.php for detection of the operating system ( getenv(PATH) is checked for '/usr/bin') works for your server. If not, set the variable $operatingSystem to 'linux' or 'windows' manually in 'Wgraph.php'.
• create two subdirectories named 'windows' resp. 'linux' below 'Wgraph' and make a 'bin' subdirectory within each.
• download the recode Zip, place recode.exe under yourWiki\extensions\Wgraph\windows\bin and recode (the linux binary) under yourWiki/extensions/Wgraph/linux/bin. Make sure to assign execution permissions to the recode file in bin/ subdirectory.
• download the latest version of aiSee and purchase a license (if needed) and store the installation into a subdirectory named 'aisee' below 'windows' resp. below 'linux'. Make sure to assign execution permissions to the aisee.bin file in the aisee/bin subdirectory.
• check 'makegraph.bat' resp. 'makegraph.sh' in the windows resp. linux directory and adapt the absolute path settings to the local file path of your server
• make 'makegraph.sh' executable on your server and make sure that the first line of the script (#!/bin/bash) points to the right place where the bash can be found.
• create a directory 'Wgraph' below your mywiki/images directory and a subdirectory 'icons' within that directory
• assign permission 777 to both directories
• activate the extension by a 'require_once' statement in your LocalSettings.php

• talk to your webservice provider to make sure that a 'system' call from within the php environment will be permitted. Maybe you have to request your own 'php.ini'. Or maybe you need a '.htaccess' file with 'AddHandler php-fastcgi .php .php4' or something similar. This depends totally on the rules and regulations of your web hoster.

• If you cannot get permission to run your own executable as a subprocess of the wiki engine you can still produce 'GDL' on the server. In these cases you should comment out the system call. It is up to the client to download the gdl file (under mywiki/images/Wgraph) and view it with aisee locally. This is better than you may think at a first glance, as it gives a lot more control like subgraph folding. Users might also want to convert the donwloaded GDL code to svg or png (using the command line version of aisee on their local hardware). They could then upload the graph as a normal image. This way can be automated using a little scripting and tools like wget or curl together with php or perl.