Posted By: The Channel 9 Team | Jan 4th, 2005 @ 6:52 PM | 314,748 Views | 71 Comments
Daniel is a software design engineer on the Avalon team and he's responsible for the 3D features of Avalon.

Here he gives us a demo of Avalon 3D. Really cool stuff. Originally designed to only run on the next version of Windows, code-named Longhorn, Avalon is now supported on Windows XP and Windows Server 2003. In fact, the demo here is done on XP.

For more information on Avalon, see the MSDN Longhorn Developer Center.
Tag: WPF
Media Downloads:
Rating:
0
0
jBuelna
jBuelna
Never mistake motion for progress.
Hello stewarts I have to say... I like your icon.  It's the only prescription.
What about texture mapping of wmv9 files on my HD or streamed from a Win2003 server?
Text mapping?
What kind of effects on text will be available? Extrusion, animation, etc?

This looks quite good if MS can provide all that!
nemisys
nemisys
You Know

Bill Gates screwed up again. But this time, he wasn't alone. Such a shame for such a financially wealthy company. You guys need to get more quailty in your products for 7.1 Billion a year in R&D

Bill Gates touts 'digital lifestyle,' despite technical bugs

You have good applications, but you guys new a new Operating System.  You were always an applications company, not an OS company.  Don't like Linux? Contribute to the development and use the new and improved Linux kernel on Longhorn, eh? Mac has freeware Darwin BSD as it's kernel. Your NT-based stuff doesn't work anymore for the new age. Get over it. Sucks less than DOS, but still sucks!
g_braad
g_braad
My 15 kilobytes of fame
Minh wrote:
Just curious why it is necessary to have a <Viewport3D.Camera> element within the <Viewport3D> element. Why not just <Camera> ?


Also, why defining a perspectivecamera within the viewport3d.camera. why not use elements within the camera itself to specify these settings. would this suggest there could be more than one camera?!? or just MS likes to use single tag elements. <flamebait />.

EDIT: just saw the movie. the main idea is clear... single tag to create just using the constructor. and elements, my guess would be, are accessors.
jBuelna
jBuelna
Never mistake motion for progress.
nemisys wrote:

you guys new a new Operating System.


bah.
Nemisys, YOU suck (monkeyballs)!
It's obvious that you're not a developer, otherwise you would never choose the linux development and config hell over the powerful, user-friendly and well-integrated windows development experience!

I sometimes have to administer and configure Linux servers for my job, and NOT FOR 7.1 BILLION US DOLLAR I would want to trade my windows OS for linux!!! (yes, I mean that)  Linux is so unproductive, you can't even install a graphical UI on a server (well you CAN install the nightmare called X, but it's very strongly advised NOT to do so (yeah, they even tell you that in the OS manuals!), as you probably know). Even if you are the nr. 1 linux guru in the world, you can never compete with a Windows Server admin that has a whole scale of graphical admin-, monitoring, and development tools at his disposal.

And btw, Microsoft has very high-quality products! I don't know what planet you are from, but just compare the MS apps with open source alternatives for example... yeah it's just pityful: I looked at so many open source projects in my life, but few, VERY few, meet the quality of Microsoft's commercial applications. Just face it, 99% of open source / linux projects never get completed to a point where you would use the application on a day-to-day basis and can depend on, and their user interfaces (if you can even call them that way) are extremely UGLY and unintuitive! Microsoft applications on the contrary are used by millions of people every second of the day, and they get their work done, and very quickly because of the user-friendly and well-designed GUI's.
jBuelna wrote:
WinFS isn't taking a backseat to Avalon (neither is Indigo.) 


I guess you could say that WinFS isn't taking a backseat to Avalon because WinFS isn't even allowed to get in the car and was sent back to it's room for another couple years.

I'm looking forward to Indigo but WinFS was the "pillar" of Longhorn I was looking forward to most. 

Sad
I really like the new presentation framework of longhorn. After installing it and playing around. I really got the feeling that working with XAML is a lot easier than writing all that code.

Is there an editor on it's way for creating XAML windows? That would be even better, since learning all the tags can be a bit of a hassle.

Shannon wrote:
jBuelna wrote: WinFS isn't taking a backseat to Avalon (neither is Indigo.) 


I guess you could say that WinFS isn't taking a backseat to Avalon because WinFS isn't even allowed to get in the car and was sent back to it's room for another couple years.

I'm looking forward to Indigo but WinFS was the "pillar" of Longhorn I was looking forward to most. 

Sad


I doubt WinFS has taken a backseat at all.

I think the requirements for WinFS were shifted, hence a recalculation of the actual schedule has occured.

Here is a what I take to be a hint as to one of the reasons, but not the only reason why WinFS is being delayed.


I think some of you might find what is mentioned in this article interesting as well (RE: WinOE).
Microsoft Communities