Haxe Studio - the Eclipse based Haxe IDE

Feedback and high-quality pull requests are highly welcome!

1. About
2. Download
3. Usage
4. Building from Sources
5. Acknowledgement
6. License

About

Haxe Studio is an Eclipse based IDE for development using the Haxe general purpose programming language.

It has the following plugins pre-installed:

• haxe4e - Haxe programming language support
• Batch Editor - Windows Batch File Editor
• EGit - Git support
• Easy Shell - opens shell windows or file managers from the popup menu in the navigation tree
• Eclipse Copy Shortcut Lines - cut/copy a complete line or the selected text depending on the selection
• Eclipse TM4E Language Pack - syntax highlighting for popular languages
• Extra Syntax Highlighting - syntax highlighting for additional languages
• Find/Replace View - Convenient view to find/replace within the active editor
• Indent Guide - Adds 'Indent Guide' (vertical line on indentation columns) to text editor
• Open with Eclipse - Windows File explorer context menu integration
• ShellWax - Bash File Editor
• Wild Web Developer - Web Development Tools (CSS, HTML, JavaScript, TypeScript, XML support)

Download

You can download the latest platform-specific releases from here:

• Linux: https://github.com/haxe4e/haxe-studio/releases/download/latest/org.haxe4e.studio-linux.gtk.x86_64.tar.gz
• MacOS: https://github.com/haxe4e/haxe-studio/releases/download/latest/org.haxe4e.studio-macosx.cocoa.x86_64.tar.gz
• Windows: https://github.com/haxe4e/haxe-studio/releases/download/latest/org.haxe4e.studio-win.x86_64.zip
• Windows Portable App: https://github.com/haxe4e/haxe-studio/releases/download/latest/HaxeStudioPortable.paf.exe

Usage

Please check the Wiki

Common Key Bindings

Action	Eclipse	Haxe Studio	vscode
Open Find Actions (Command Palette)	CTRL+3	CTRL+3	F1 / CTRL+SHIFT+P
Open Quick Outline	CTRL+O	CTRL+O	n/a
Full Screen Toggle	ALT+F11	F11	F11
Format Source Code	CTRL+SHIFT+F	CTRL+SHIFT+F	ALT+SHIFT+F
Go to Method/Type Declaration	F3	F3	F12
Zoom In/Out	CTRL++/-	CTRL++/-	CTRL++/-

Building from Sources

To ensure reproducible builds this Maven project inherits from the vegardit-maven-parent project which declares fixed versions and sensible default settings for all official Maven plug-ins.

The project also uses the maven-toolchains-plugin which decouples the JDK that is used to execute Maven and it's plug-ins from the target JDK that is used for compilation and/or unit testing. This ensures full binary compatibility of the compiled artifacts with the runtime library of the required target JDK.

To build the project follow these steps:

1. Download and install a Java 17 SDK, e.g. from:

   • https://github.com/ojdkbuild/ojdkbuild
   • https://adoptium.net/releases.html?variant=openjdk17
   • https://www.azul.com/downloads/?version=java-17-lts&architecture=x86-64-bit&package=jdk#download-openjdk

2. Download and install the latest Maven distribution.

3. In your user home directory create the file .m2/toolchains.xml with the following content:

   <?xml version="1.0" encoding="UTF8"?>
   <toolchains>
      <toolchain>
         <type>jdk</type>
         <provides>
            <version>17</version>
            <vendor>default</vendor>
         </provides>
         <configuration>
            <jdkHome>[PATH_TO_YOUR_JDK_17]</jdkHome>
         </configuration>
      </toolchain>
   </toolchains>

   Set the [PATH_TO_YOUR_JDK_17] parameter accordingly.

4. Checkout the code using one of the following methods:

   • git clone https://github.com/haxe4e/haxe-studio
   • svn co https://github.com/haxe4e/haxe-studio haxe-studio

5. Run mvn clean verify in the project root directory. This will execute compilation, unit-testing, integration-testing and packaging of all artifacts.

Acknowledgement

See https://github.com/haxe4e/haxe4e/blob/main/README.md#acknowledgement

License

If not otherwise specified (see below), files in this repository fall under the Eclipse Public License 2.0.

Individual files contain the following tag instead of the full license text:

SPDX-License-Identifier: EPL-2.0

This enables machine processing of license information based on the SPDX License Identifiers that are available here: https://spdx.org/licenses/.

An exception is made for:

1. files in readable text which contain their own license information, or
2. files in a directory containing a separate LICENSE.txt file, or
3. files where an accompanying file exists in the same directory with a .LICENSE.txt suffix added to the base-name of the original file. For example foobar.js is may be accompanied by a foobar.LICENSE.txt license file.