{"id":2922,"date":"2010-09-24T14:30:13","date_gmt":"2010-09-24T14:30:13","guid":{"rendered":"http:\/\/fdt.powerflasher.com\/blog\/?p=2922"},"modified":"2011-09-30T08:38:58","modified_gmt":"2011-09-30T15:38:58","slug":"fdt-haxe-plugin-public-alpha-2-released","status":"publish","type":"post","link":"https:\/\/fdt.powerflasher.com\/blog\/2010\/09\/fdt-haxe-plugin-public-alpha-2-released\/","title":{"rendered":"FDT haXe Plugin Public Alpha 2 Released"},"content":{"rendered":"<p>Powerflasher, in collaboration with <a href=\"http:\/\/influxis.com\">Influxis<\/a>, is proud to release the second public alpha of the <strong>haXe<\/strong> plugin for FDT!<\/p>\n<p>This new version builds on the first alpha by providing a greatly enhanced auto-completion system, complete with automatic imports and class lookup, as well as a much needed improvement in compiler configuration by supporting the use of HXML project files. We at Powerflasher now feel that the haXe plugin for FDT provides the ultimate coding experience for the haXe language.<\/p>\n<p>Here\u2019s an up-to-date roundup of the features supported in the alpha 2 release:<\/p>\n<p>\u00b7 Live error checking<\/p>\n<p>\u00b7 Greatly enhanced auto-completion capability<\/p>\n<p>\u00b7 Syntax coloring<\/p>\n<p>\u00b7 Class \/ Enum \/ Interface file creation wizards<\/p>\n<p>\u00b7 Full HXML file inclusion<\/p>\n<p><strong>Installing the haXe Plugin Alpha 2 Release<\/strong><br \/>\nIf you are new to the haXe plugin alpha for FDT, you can install quite simply by following the steps below.<\/p>\n<p>&nbsp;<\/p>\n<p><span style=\"font-size: 12.96px;\">1. First, download the latest version of FDT4 Beta release by visiting this link and install it.<\/span><br \/>\n<span style=\"font-size: 12.96px;\">2. Download the haXe installer for your operating system from http:\/\/haxe.org\/download.<\/span><br \/>\n<span style=\"font-size: 12.96px;\">3. Run the haXe installer, selecting Yes when asked if you wish to install the Neko runtime.<\/span><br \/>\n<span style=\"font-size: 12.96px;\"><span style=\"font-size: 12.96px;\">4. Select the \u201cFDT Plugins Site\u201d update site. (If it is not included in your drop down menu, enter: http:\/\/fdt.powerflasher.com\/plugins in the \u201cWork with\u201d text input and hit return)<\/span><\/span><\/p>\n<p><img loading=\"lazy\" title=\"dhspwgc_108djw2z74p_b\" src=\"http:\/\/fdt.powerflasher.com\/blog\/wp-content\/uploads\/2010\/09\/dhspwgc_108djw2z74p_b.png\" alt=\"dhspwgc_108djw2z74p_b\" width=\"602\" height=\"270\" \/>5. Select the option \u201cFDT haXe plugin\u201d from the items presented and click Finish. Allow the installation to complete.<\/p>\n<p><br \/>\n<strong> Configuring the haXe Plugin<\/strong><br \/>\nBefore the newly installed haXe plugin can be used, it will need to be configured so it knows where to find the haXe compiler on your machine. To do this, select Window-&gt;Preferences from the menu and navigate to the HaXe-&gt;SDK option. You should be presented with a textfield control with the label HaXe SDK Location. Click the browse button next to this field and navigate to where your installation of the haXe compiler exists, then click OK on both dialogs to close them. On windows machines, the haXe installation will usually exist at the location:<\/p>\n<p>C:\\Motion-Twin\\haXe<\/p>\n<p>Mac OSX users may want to try:<\/p>\n<p>\/usr\/lib\/haXe<br \/>\n<\/p>\n<p><strong>Using the haXe Plugin<\/strong><br \/>\nNow for the fun stuff. Create a new AS3 project by selecting File-&gt;New from the menu and choosing \u201cEmpty AS3 Project\u201d from the presented list of options. In the field titled Project name, enter \u201cHello haXe\u201d. Now click OK.<br \/>\n<\/p>\n<p>Now, right click on the src directory in the project file tree and select New-&gt; Haxe Class. If this option does not appear in the context menu, FDT will need to be refreshed. You can do this by selecting the menu option Window-&gt;Reset Perspective.<br \/>\n<\/p>\n<p>When the new class dialog is displayed, give the class the name \u201cMain\u201d and click OK. A new file should now exist in the src directory.<\/p>\n<p>We now have a haXe project and class file, which is great, but we haven\u2019t yet told the haXe compiler what type of project we\u2019re building. To do this, right click on the project node in the file tree pane and select Add HaXe Project Nature. This will raise a new wizard. You can immediately click the next button, as we are not interested in modifying the haXe SDK location for this project.<\/p>\n<p>The second screen in the new wizard provides the option to specify the target platform for our project. Currently, this includes:<\/p>\n<p>\u00b7 Flash9 SWF (AVM2 target)<\/p>\n<p>\u00b7 Flash SWF (AVM1 target)<\/p>\n<p>\u00b7 Javascript<\/p>\n<p>\u00b7 AS3 Code<\/p>\n<p>\u00b7 Neko Binary<\/p>\n<p>\u00b7 PHP Code<\/p>\n<p>\u00b7 C++ Code<\/p>\n<p>Each of these target platforms are fully supported by the FDT plugin and we recommend that you play with this option at your leisure. However, for this example, choose the Flash9 SWF option.<\/p>\n<p>If you look in your project file list, you should notice a new file with the extension \u201c.hxml\u201d. This is your project compiler settings. You can alter this file by right-clicking it and selecting Open With-&gt;Text Editor. Simply double clicking the file will launch the haXe compiler if using the Windows installation of FDT.<\/p>\n<p>The haXe plugin supports a wealth of compiler switches and options, and we advise that you read about them on the haXe website at <a href=\"http:\/\/haxe.org\/doc\/compiler\">http:\/\/haxe.org\/doc\/compiler<\/a>.<\/p>\n<p>Open the Main class and enter the following code:<\/p>\n<p>package;<\/p>\n<p>class Main {<br \/>\npublic static function main() {<br \/>\ntrace( &#8220;Hello, World&#8221; );<br \/>\n}<br \/>\n}<\/p>\n<p>Save this file and run it. A new SWF file will be compiled into your project directory.<\/p>\n<p>We at Powerflasher, along with Influxis, are very excited about the new possibilities provided by this plugin and, as always, we would welcome any feedback, bug notifications and feature requests you may provide. We encourage all such information to be posted on <a href=\"http:\/\/bugs.powerflasher.com\/jira\/browse\/FDT\/component\/10532\">our issue tracking website<\/a>. With your help, we aim to make FDT a truly unique experience for applications development.<\/p>\n<p><strong>What\u2019s Next?<\/strong><br \/>\nWe are currently busying away on the haXe plugin for a major Beta release. This will include the ability to create haXe projects using FDT\u2019s fully integrated project wizard as well as being able to compile and launch directly within the FDT workflow. We aim to make FDT the best haXe development environment available just as it is for Flash!<\/p>\n<div><span style=\"font-size: 12.96px;\"><br \/>\n<\/span><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Powerflasher, in collaboration with Influxis, is proud to release the second public alpha of the haXe plugin for FDT! This new version builds on the first alpha by providing a greatly enhanced auto-completion system, complete with automatic imports and class lookup, as well as a much needed improvement in compiler configuration by supporting the use [&hellip;]<\/p>\n","protected":false},"author":12,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[4],"tags":[455,149,156],"_links":{"self":[{"href":"https:\/\/fdt.powerflasher.com\/blog\/wp-json\/wp\/v2\/posts\/2922"}],"collection":[{"href":"https:\/\/fdt.powerflasher.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fdt.powerflasher.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fdt.powerflasher.com\/blog\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/fdt.powerflasher.com\/blog\/wp-json\/wp\/v2\/comments?post=2922"}],"version-history":[{"count":6,"href":"https:\/\/fdt.powerflasher.com\/blog\/wp-json\/wp\/v2\/posts\/2922\/revisions"}],"predecessor-version":[{"id":2948,"href":"https:\/\/fdt.powerflasher.com\/blog\/wp-json\/wp\/v2\/posts\/2922\/revisions\/2948"}],"wp:attachment":[{"href":"https:\/\/fdt.powerflasher.com\/blog\/wp-json\/wp\/v2\/media?parent=2922"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fdt.powerflasher.com\/blog\/wp-json\/wp\/v2\/categories?post=2922"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fdt.powerflasher.com\/blog\/wp-json\/wp\/v2\/tags?post=2922"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}