SimianLogic

Does Haxe-UI use sprite sheets?
Can you nest containers? Widgets within widgets? Or is this a FlxUI object?

I've typically leaned towards runtime instantiation (the "Code test" in the RPG UI demo). In this case I'd read in the JSON and instantiate hax-ui elements according to the naming conventions. 
I might make a go at wiring up a demo of this (I've done a bit of Haxe in the past).

Are you thinking you'd modify the photoshop generator to output layout XML files? 
  You'd need some way to mark up the additional attributes (as you wouldn't want to add these after export as re-exporting would blow away your changes) 
  I think it would make sense to export the metadata from Photoshop that makes sense without jumping through too many hoops and extend your
  layout loader to support "metadata" files. Like, I'm thinking you'd have the PS-generated layout file that gets completely blown away/recreated each time

elsassph

package;

#if macro
import haxe.Json;
import haxe.macro.Context;
import haxe.macro.Expr;
import haxe.macro.Type;
import sys.io.File;
import sys.FileSystem;

jcward

Instructions for testing hxScout with hxcpp.

FYI, I've tested this using Haxe 3.1.3, OpenFL 2.1.7 (the legacy version, aka _v2, aka not next) in Windows 7. Your mileage may vary. All this is under heavy development, so it may cease working at some point.

1) Git checkout (or download) jcward's hxcpp (integration branch), hxtelemetry, and hxScout:

https://github.com/jcward/hxScout/archive/master.zip
https://github.com/jcward/hxtelemetry/archive/master.zip
https://github.com/jcward/hxcpp/archive/integration.zip

nadako

class Main {
    static function main() {
        var a = getValue();
    }

    static function getValue():Tuple<Bool,Int> {
        return new Tuple(true, 10);
    }
}