Cross platform Haxe/OpenFL set of styleable application centric, rich UI components, to be used "out the box". Supports css type styling/skinning.
Haxe CSS Batchfile
Latest commit 15c1431 Dec 3, 2016 @ianharrigan committed on GitHub Merge pull request #344 from loudoweb/master
fix #221 stageX and stageY correct computations

README.md

Stories in Ready

Important note about OpenFl/Lime

OpenFL has dropped legacy support in versions after 3.6.1. Since HaxeUI (version 1) is tied to legacy versions of OpenFL/Lime the following are the maximum versions that can be used with it:

  • OpenFL: 3.6.1
  • Lime: 2.9.1

Haxe UI

Join the chat at https://gitter.im/ianharrigan/haxeui Cross platform Haxe/OpenFL set of styleable application centric rich UI components to be used "out the box". Supports css type styling/skinning.

Demos (May be out of date): SWF | Windows | Neko | Android | AIR | HTML

Adobe AIR note: Installer will not install from mounted/network drives.

Documentation

Wiki (Incomplete)

API (Incomplete)

Projects

Instructions

First install haxeui via haxelib:

haxelib install haxeui

Once installed add

<haxelib name="haxeui" />

to your openfl application.xml. Finally, create a basic application with:

import haxe.ui.toolkit.core.Macros;
import haxe.ui.toolkit.core.Toolkit;
import haxe.ui.toolkit.core.Root;
import haxe.ui.toolkit.controls.Button;

class Main {
    public static function main() {
        Macros.addStyleSheet("styles/gradient/gradient.css");
        Toolkit.init();
        Toolkit.openFullscreen(function(root:Root) {
            var button:Button = new Button();
            button.text = "HaxeUI!";
            root.addChild(button);
        });
    }
}

Note: haxeui comes with some styles ready for use, if no styles are added a default one is used.

If you created your own style/theme from scratch and don't want to include the built-in styles in your build result, specify the flag <haxdef name="haxeui-exclude-resources" /> before the <haxelib name="haxeui" /> directive in your project configuration file.

Components

General components

  • Button
  • Check box
  • Image
  • Option box
  • Progress bars (horizontal & vertical)
  • Scroll bars (horizontal & vertical)
  • Sliders (horizontal & vertical)
  • Tab bars
  • Text (static, input, multiline)
  • List selection (drop downs, popup lists)
  • Date selection (drop downs, popup calendar)
  • Calendar
  • Menus

Extended components

  • Code editor (supports basic syntax highlighting)
  • RTF edtior (preliminary, only fully functional in flash due to neko/cpp limitations)

Layout, position and containment components

  • Accordion
  • Grid
  • HBox
  • ListView
  • MenuBar
  • ScrollView
  • Stack
  • TabView
  • VBox

Popups

  • Busy
  • Simple
  • List
  • Custom
  • Calendar

Data Sources

  • Array
  • JSON
  • XML
  • MySQL (Neko/Read-Only)
  • Files (Neko/Read-Only)

Notes

html5 target functions but is not particularly performant. This will, hopefully, be improved in future releases.

An experimental html5 demo is available here

Licence

Unless indicated otherwise, this code was created by Ian Harrigan and
provided under a MIT-style license.
Copyright (c) Ian Harrigan. All rights reserved.

Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the "Software"),
to deal in the Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish, distribute, sublicense,
and/or sell copies of the Software, and to permit persons to whom the
Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED ?AS IS?, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

Bitdeli Badge

Bitdeli Badge