Editors

Modelworks Software's IDE engine is designed to be easily configured. File types, menus, toolbars, workspace tabs, output tabs, and info panels can be created and controlled from scripts.

File types supported in JPad Pro and SitePad Pro include:

• Active Server Pages (*.asp, *.aspx)
• Apache Cocoon Sitemap
• Apache Cocoon Template (*.jx)
• Command (*.bat, *.cmd)
• C/C++ (*.h, *.hh, *.hhp, *.cpp, *.cc, *.c)
• Cobol (*.cbl, *.cob)
• Corba Idl (*idl)
• DTD (*.dtd)
• EJB (*.ejb)
• HTML (*.htm, *.html, *.html.en, *.shtml)
• HTML component (*.htc)
• HTML include (*inc)
• Jad Java decompiler (*.jad)
• Java (*.java)
• Java Server Pages (*.jsp)
• Java Server Page Fragment (*.jspf)
• Javascript (*.js)
• Java Dynamo Server Pages (*.jhtml)
• Lisp (*.lsp)
• Make (*.mak)
• Manifest (*.mf)
• Perl (*.cgi, *.pl, *.pm, *.vep)
• PHP (*.php, *.php3, *.php4, *.phtml)
• Python (*.py)
• SQL/PSQL (*.sql, *.psql, *.xsql)
• TLD (*.tld)
• VBScript (*.vb, *.vbs, *.bas)
• Jakarta Velocity (*.vm, *.vtl, *.vsl)
• XML (*.xml, *.xhtml, *.vxml, *.xsd, *.xsl, *.xsld)

Additional file types supported in SitePad Pro include:

• Asm (*.asm, *.asmx)
• ActionScript (*.asr)
• C# (*.cs)
• ColdFusion (*.cfm)
• Dream Weaver Template (*.dwt)
• Freemarker (*.ftl)
• HTML pre-processor (*.htp)
• J# (*.jsl)
• MIT Curl (*.curl, *.mcurl, *.scurl)
• VRML (*.wrl)
• YACC (*.y)

File Formats and Encodings

Files can be read and written with Windows (\r\n), UNIX (\n) or Mac (\r) line endings.

Standard editions use the default code page for encoding characters. For SitePad Pro version 6 and in the international editions of JPad Pro and SitePad Pro version 5 you can choose the code page or one of the following encodings:

• 65000 UTF-7
• 65001 UTF-8
• 65002 UTF-8 with Byte Order Mark (BOM)
• 1200 Unicode UCS-2 Little-Endian with BOM
• 1201 Unicode UCS-2 Big-Endian with BOM

For Java you should use the default code page (e.g., ANSI) or the UTF-8 encoding without signature. The Java compiler will generate a syntax error if you use UTF-8 encoding with a BOM. If you change the encoding you will also need to set the correct encoding for the compiler in JDK/Edit Options...

You should use the default code page or UTF-8 encoding without signature along with UNIX line endings if you are going to deploy the file to a UNIX system.

The signature (also called a byte order mark) for Unicode files is contained in the first two, three or four bytes of a file. For UTF-8 files the bytes are 0xEF, 0xBB and 0xBF. For Unicode UCS-2 the bytes are 0xFE and 0xFF (Big-Endian) or 0xFF and 0xFE (Little-Endian). If you open a Unicode file without a signature then you should set the encoding for the file to be correctly decoded.

For more information on Unicode and file encodings see UTF-8 and Unicode FAQ, Joel On Software and UTF and BOM FAQ.