to support client-editor, resource path usage of client-ui macros needs to be refactored

[Schipy]

ImageAssetMacros needs resource path, which it reads form hx.properties generated by old plugin

• in haxe 3 this can be solved by custom compile argument, for haxe 2.10, probably best is just generate a hx.properties in NG plugin with new path (can't pass custom compiler args)

[lptr]

Why not report it for client-ui/client-editor then? Is there something to do in the plugin for this?

[Schipy]

Yes, the generated haxe compile statement has to solve to pass in the path of the resources to macros somehow. Current plugin generates a properties file, in Haxe 3 this can be swapped by adding a -D resources=<wherever .har is extracted> to the compile statements. If the plugin supports custom compile flags for any compile tasks, and we switch to haxe 3, then this can be solved without touching the plugin (though it still may be a convenience feature). Just wanted to make a note about all this.

[lptr]

Macros can load resources from the classpath instead of the file system. Resource folders are on the classpath during build already.

[lptr]

Sorry, they aren't right now. I will put them on the classpath then.

[Schipy]

I think they're also needed atm to generate flash embed statements, which uses the actual path string.

[lptr]

Maybe we need another task to extract resources from a HAR to a local folder before the build?

[lptr]

Is this fixed yet? @Schipy ?

[lptr]

I'm gonna close this because nobody cares anymore