Well Richard , I want to believe the people here understood from the beginning  
what "Alpha" means . Otherwise you should watch your back walking on the 
streets ;) 
Good work ! 

Sent from my iPhone

On May 5, 2011, at 9:30 PM, Choons <[email protected]> wrote:

> Thanks, Richard. Glad to see you guys are willing to bite the bullet
> and rework areas to make Away3D better. And thanks for the
> documentation as well. Last year I was trying to develop an app on the
> YouTube API and they would push out changes without informing the
> community. My code would break and I had no idea why. Looks like
> developers can count on the Away3D team to keep us in the loop.
> 
> On May 5, 1:01 pm, Richard Olsson <[email protected]> wrote:
>> Hello Away3D community!
>> 
>> This is a heads up that in a moment, I will be pushing changes to the GitHub 
>> repository (SVN will follow in the next couple of days) that will likely 
>> break any code that you have that uses Broomstick (Away3D 4.0 alpha). This 
>> is because of some major incompatible changes that we're making to the way 
>> that assets are loaded and managed in Away3D 4.0. (In the unlikely event 
>> that your code doesn't load assets at all, it might be unaffected.)
>> 
>> We wanted to make these changes right now, while Away3D is still in alpha, 
>> and we believe strongly that this is the best loading framework that we have 
>> ever had in Away3D (and probably better than most if not all competing 
>> engines out there.)
>> 
>> The short version is that we have removed the ResourceManager (which you are 
>> probably currently using to load assets) and replaced it with three 
>> different classes that can be used for loading: The AssetLibrary (with asset 
>> management features), the AssetLoader (for simple loading of files including 
>> dependencies) and the Loader3D (for easily loading assets into a scene.)
>> 
>> For those interested in a slightly longer description of the new loading 
>> framework, I have attached a five page PDF outlining the design principles, 
>> features and basic usage of the new loading classes. We hope this will ease 
>> your transition while waiting for proper documentation.
>> 
>> Remember that Away3D 4 is still alpha, and things might still change, but we 
>> feel a lot more comfortable with the new solution, and I think that we will 
>> be able to keep it more or less stable through to the final release of 
>> Away3D 4.0.
>> 
>> The examples have been updated as well (all apart from the ones that use 
>> MD5, so those are still broken. Please bear with us while we fix them.) 
>> Example code for the AssetLibrary, AssetLoader and Loader3D will be coming 
>> shortly as well.
>> 
>> Thanks for your understanding, and if you have any questions, comments, 
>> feature requests or bug reports: Fire away! ;)
>> 
>> /Richard, Away3D
>> 
>>  LoadingInAway4.pdf
>> 147KViewDownload

Reply via email to