slashrun.org is a framework for a collective exploration of the potential locked up in text at the digital age

FAQ

1. what is a slashrun?

A slashrun is an explorational bit of software that can be fed with markup data or controlled by script.

2. what are the requirements for running slashruns?

A decent Windows, Mac OSX or Linux computer with a decent graphics card and Java installed. A propos, Java version 1.5 will do the job, but version 1.6 will provide a smoother experience when launching slashruns.

If execution is sluggish, it could be for one of the following reasons:

  • • Your graphics card is an on-board accelerator. In this case, any entry-level card by NVIDIA or ATI will do a much better job.
  • • You have too much applications running in parallel.
  • • The slashrun you are running is simply too complex for smooth rendering on your computer.

3. why is it sometimes slow to start-up?

First of all, Java Web Start – one of the key technologies behind slashruns – is notoriously slow to start-up. In addition, the first-time-ever a slashrun is executed will be slower because of the base code that needs to be downloaded.

Finally, you will be asked whether you trust trust Ariel Malka or not each time a slashrun is about to start. A simple way to bypass this step for further executions is to check Always trust content from this publisher (on Mac OSX, you may need to press Show Certificate and then check Always trust "Ariel MALKA".)

4. why is it required to trust Ariel Malka?

Java applications that use OpenGL and read content (e.g. images) from the web need to be signed with a certificate and users need to confirm that they trust the vendor of the application. Since it's not possible to issue a trustable certificate for slashrun.org, the solution was to issue a personal certificate for Ariel Malka, the guy in charge...

5. what is the technology behind?

Slashruns rely on the software toolkit developed at chronotext.org over the years. The programming environment is Java, the main libraries used are jogl (bindings for OpenGL) and TagSoup (keep on truckin' xml parsing.)

6. is the chronotext software toolkit open source?

No, the right model still has to be found...

Version 1.0.4 – November 24, 2008