> I would like to consider putting these demos into the repository
Thanks for showing interest.
> but they are packaged oddly.
I tried my best to mimic package structures found on the site - StateMachine ZIP being one of them.
Please let me know what the preferred format is then and I'll update.
While on this topic, please allow me to introduce the haxelib package manager:http://haxe.org/doc/haxelib/using_haxelib
It's source is available - so maybe a custom version could solve some PMVC maintenace problems?
> Particularly, what is 'xinf'? (as in Demo_haXe_Xinf_StopWatch...../puremvc/haxe/demos/xinf/...)
Glad you ask. Xinf can be many things , but in terms of your 'Source Code Packaging' guidelines here , the fact that Xinf can be a runtime ( Xinfinity ) and a framework, makes it fall into a YYY category following:
"YYY (only optional if not applicable) = any related client technology being used (flex, flash, air, etc...)"
While I've currently only produced Flash and JS binaries - I plan to update the example with the neko-based Xinfinity binaries once a new xinf release is made.
All the best,
Xinf (Xinf Is Not Flash) strives to provide a unified SVG-oriented API for graphics programming in haXe. Using Xinf, your application can run on Adobe's Flash Player (Version 9 up), our own 'Xinfinity' runtime, and (with limitations) on standards-compliant web browsers like Mozilla Firefox - from the same source code.
Most of it's cross-runtime magic is owed to the excellent haXe language and compiler and the neko virtual machine. Xinf adds abstracted implementations for rendering and user-interface events, and a cross-platform (Linux/Windows/OSX), OpenGL-based runtime environment (dubbed Xinfinity).
"The Xinf Project"'s first output "product" is a Flash movie to render static SVG content.