No one (including me) has access to version 4 of the API, except the core dev team. They are under NDA and cannot discuss anything, relating to Molehill, publicly. If they do they would get chopped up and cooked into a delicious Boeuf Bourguignon by Thibault Imbert. I would assume that switching to Away3D 4 will require minimal re-write. It's a high level API and what will change are the low level renderers used: DirectX, OpenGL and Switfshader.
Simply put we cannot develop for Away3D 4 without the updated API and without the next Flash player. Once the beta is out we will have the chance to port our work over. As announced, Away3D 4 will be available when the beta is out. There's going to be a few months where we can test and update our projects to be ready. All we know is public beta will be in H1. Anything else is speculation and a waste of time. So the best we can do is to make sure our projects stick closely to the current API. Avoid hacking or modifying core classes. Extend existing ones. I have been using Away3D since day one and never had to "redo everything" upon updating to the latest API. The whole idea behind Away3D has been to make the lower level stuff seamless by creating a solid and simple high level API ;) Cheers. J. On Jan 1, 7:45 pm, Michael Iv <[email protected]> wrote: > He He ... :) > > On Sat, Jan 1, 2011 at 9:41 PM, Jarrad <[email protected]> wrote: > > Hey Guys, > > > Im wondering will the next gen version of away3d api be closer to > > away3d lite or the main ? > > > I want to start developing for it now, but not really wishing to redo > > everything again when next version comes out. > > Any hints or tips? > > > Cheers, > > Jarrad > > -- > Michael Ivanov ,Programmer > Neurotech Solutions Ltd. > Flex|Air > |3D|Unity|www.neurotechresearch.comhttp://blog.alladvanced.nethttp://www.meetup.com/GO3D-Games-Opensource-3D/ > Tel:054-4962254 > [email protected] > [email protected]
