See the release notes See the project page

What is a Scripting Page ?

There are two different types of Scripting Pages :

Which Scripting language is used ?

This is the funny part : there is no required scripting language to use SSP. In theory, you may use anything and plug it into SSP if the requirements below are met : In fact, SSP is a set of Java classes build on a core abstract class. When you want to add a new language in SSP, just derive this class and connect the classes from your code.

Which Scripting language are already available ?

In the current version (SSP-0.2), the following scripting languages are connected (select one for a link to more informations) : Of course, the implementation is not always complete, or fully compliant with all available possibilities of the scripting language. This may evolve with the further versions of SSP, depending of the needs of the users. For now, the TCL implementation works fine, as I know how to use this scripting tool, and jpython has been more tested than the others.

How to use it ?

What is missing ?

Of course, a lot !
If I should summarize what shall be done to get a correct implementation, I'll suggest : All those ideas are planned, and should be made available in future releases.

Why this Project ?

Writing pages in HTML is just fine when you only want to build static, stone-shaped pages with information that never change. You may then use any available HTML editor and draw your site. Anyone is able to access your informations, just using a simple web browser. But if you want to change the layout, create new pages, update anything in your site, it will be very painful, and you will have to spend lots of time in validating the new design.

You may use CSS or JavaScript to help you control the look and feel of you site. These tools are very useful and may help you for most your jobs. You will be able to create almost any design you want and get a very friendly GUI. But this will not help you with dynamic informations on the site, as they are used in a client point of vue.

Another way to dynamise you work is to use CGI scripts. They are on the server side of the connection, and are able to look at the files on the server's disk. But this is only a pack of scripts, that the end-user targets when selecting a link. Tying that with JavaScript is fine, but you will have to learn three languages (HTML, JavaScript and Perl) to achieve your goal!

When designing the site, you may create specialized applets and servlets, if you are able to code in Java. This is the heavy way to build a site. Ho yes, you are then able to do whatever you want, from a mastermind game to a database browser, but this remains heavy.

Searching the web, I found a small thing that was very impressive. This was the TCL HTTP server from Scriptics. This is a real HTTP web server written entirely in the TCL scrpting language. It is able to parse pages on the fly, just as JSP, and uses script commands as URLs. I thought this was a very good idea. But the server itself is not as robust, fast and secure as Apache, Tomcat or other compiled web servers.

The only solution was to create myself a way to give site designers an access to their favorite scripting language directly in the server. This has led to SSP.