haxe3 and timescales.
68 views
Skip to first unread message
JLM
May 31, 2012, 8:05:18 PM5/31/12
to haxe...@googlegroups.com
I am thinking on working on a haxe 3 focused site for new users with some help. Partially it's a way to get to grips with the haxe wiki/forum code base, but wondered what the considered timescales are for haxe3 release.
My initial thoughts are to have a separation between frontend and backend, with where possible only one example covering several languages with --next in the hxml, but lots of these examples. Targets ( platforms and languages ) would be treated more as a secondary concern, and in some ways treated as inconsequential, an annoying practicality. The site would be semi book structured in format, so that there is a clear flow for users and also could possibly be provided in pdf or even printed form, it is not aimed to be the only approach to haxe but more my ( and my collaborators ) approach.
I was not intending to seek any foundation permissions or specific recommendations, but happy to receive content etc.., but rather go with the theory that the site will lives or dies by users and contribute or not in the same way, initially I need to get something structurally up there, and get into the habit of adding every day.
Anyway as usual lots of ideas but not yet content. My main question again is - what are the haxe3 realistic timescales, bearing in mind that before a release many haxelib's may need to be update so they can work with the new structures; rather than haxe provide a 'broken' experience - a concern I have heard voiced recently.
Hopefully this is positive and will contribute positively to haxenext perspective..... unless like many of us paid work takes too much of my time... only time will tell.
Justin
My initial thoughts are to have a separation between frontend and backend, with where possible only one example covering several languages with --next in the hxml, but lots of these examples. Targets ( platforms and languages ) would be treated more as a secondary concern, and in some ways treated as inconsequential, an annoying practicality. The site would be semi book structured in format, so that there is a clear flow for users and also could possibly be provided in pdf or even printed form, it is not aimed to be the only approach to haxe but more my ( and my collaborators ) approach.
I was not intending to seek any foundation permissions or specific recommendations, but happy to receive content etc.., but rather go with the theory that the site will lives or dies by users and contribute or not in the same way, initially I need to get something structurally up there, and get into the habit of adding every day.
Anyway as usual lots of ideas but not yet content. My main question again is - what are the haxe3 realistic timescales, bearing in mind that before a release many haxelib's may need to be update so they can work with the new structures; rather than haxe provide a 'broken' experience - a concern I have heard voiced recently.
Hopefully this is positive and will contribute positively to haxenext perspective..... unless like many of us paid work takes too much of my time... only time will tell.
Justin
Nicolas Cannasse
Jun 1, 2012, 3:17:28 AM6/1/12
to haxe...@googlegroups.com
We have been moving quite fast recently thanks to Simon which have been
contributing a lot of patches. I have not yet started working on
implementing all the Haxe3 stuff but we got a nice list of the things we
need to do already, which is a big part of the job done.
I expect this summer will be a good time to advance on some of these
features, hopefully we will be able to release Haxe 3 in September/October
Best,
Nicolas
Reply all
Reply to author
Forward
0 new messages