package com.tutego.utils;

import java.io.InputStreamReader;
import javax.script.Invocable;
import javax.script.ScriptEngine;
import javax.script.ScriptEngineManager;
import javax.script.ScriptException;

public class JavaScriptBeauty
{
private static ScriptEngine beautyEngine;

public static String beautify( String s )
{
try
{
if ( beautyEngine == null )
{
beautyEngine = new ScriptEngineManager().getEngineByName( “JavaScript” );
beautyEngine.eval( new InputStreamReader( FoxproParser.class.getResourceAsStream( “jbeauty.js” ) ) );
}
Invocable inv = (Invocable) beautyEngine;

return inv.invokeFunction( “beauty”, s ).toString();
}
catch ( ScriptException e )
{
e.printStackTrace();
}
catch ( NoSuchMethodException e )
{
e.printStackTrace();
}

return “”;
}
}

I changed the script:

function beauty( plaintext )
{
var plength=plaintext.length;
cmp=new Comp();
…
while(++charAt

For example, I have my tabs set to display as equal to 2 spaces (“set tabstop=2″ in .vimrc). A guy I work with (who I respect as a coder) prefers to use three spaces. I don’t understand that, as you can set vim to use a tabstop of three, and immediately save bandwidth even though visually the code is the same.

I’m still listening to the comments. When I have a few hours to spare, I’ll collate the ideas, expand the app to accommodate them, and announce the updates.

white spaces have their place too, and it’s mostly to do with readability. stuff like if statements with lots of conditions. as for the curly braces…. yeah, end of line is better.

one of the things i have most problems with is the number of spaces (or tabs) to indent for each block of code.

On the other ideas expressed, yup – mostly good ideas (although I don’t see the point of coloured syntax in this context…). I’ll probably work up some options for them during the week (yours as well, Ken, even if it’s wrong )