Good news everyone (anyone ?) !
Turns out it was easier than I thought to switch cocktail to haxe 3, so it works now, in an haxe3 branch on github, and I’ve also submitted it to haxelib.
So if you have haxe […]
Thanks. I’ll be back after I’ve given the module enough testing.
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
Thanks a lot for the detailed explanation. As per your suggestion I changed the layers with only 2 levels and now my navigation to all pages are working fine. I am using ‘show’ and ‘hide’ in the […]
the next release for cocktail is ready, that will be the last one for Haxe 2. I’ll release it on haxelib in a couple days then I’ll start updating cocktail for Haxe 3.
I’ve to test that all samples […]
If it’s intended as a replacement, you have to agree to the BSD license, and I will review it for integration. The typical method for a contribution is a pull request on github, but as it’s a plugin if you just […]
level1: start layer
= which should contain only the menu buttons to access to the different pages.
= to access to each sub-layer, use the “icon” parameter of each menu button, with “page name” corresponding […]
should all be only on your start layer
the components specific to each sub-layer should be only on the corresponding sub-layer
It is intended as a replacement, although you can keep it separate if you prefer.