Alright, I’ve run all the tests and updated on haxelib with the version number 1.0.0-beta.5, cocktail now uses the semver notation for versions

Next cocktail release now use this convention (1.0.0-beta.5), and it is now obligatory for haxelib for haxe3 http://haxe.org/doc/haxelib/haxelib2

For the getting started, I think we should use parts of this getting started

http://haxeflixel.com/articles/getting-started

Chris,

Thanks for your support !

For what kind of projects are you using Cocktail ?

If you are interested, we are always looking for contributors to help us.

Thanks for the answer, such a wonderful library, it would be very useful for nme based apps, games if it could be used in such a way.

Hopefully I can watch a recording of your presentation, the live streams […]

Hi,

for now, it would be a bit painful, cocktail currently works standalone.
However we are working on it, in fact we’d like to showcase cocktail integration with NME at the next Haxe conference which will […]

I updated the master branch with the lastests working samples:

https://github.com/silexlabs/Cocktail/tree/master/samples

Hi

All the projects in Cocktail-legacy-master are obsolete.
You can try the samples located here: https://github.com/silexlabs/Cocktail/tree/master/samples

Hi

Yes I know why, it is because of this command which is not cross-platform:
“-cmd cp -R assets binjs”

I think you are using Cocktail’s master branch.
I recommend using develop one.

If you are using […]

Hi Michael !

For the moment, Cocktail supports only Haxe JS written in .hx source files… The “translation” of haxe JS to Cocktail is made by the “–remap js:cocktail” macanism you can see in Cocktail […]