Page 1 of 1
XAML, Avalon and WinFX
Posted: Thu Jan 27, 2005 1:58 pm
I was read some information on XAML, Avalon and WinFX. I was wondering if any interresting things like this with web and desktop 3d content in mind are goals of Blender development? I'm not aware of any Linux 3d user interface markup language developments so I didn't mention any of those. As a web designer and 3d artist I look forward to a time of adding 3d content directly into my web code as content.
Posted: Thu Jan 27, 2005 6:23 pm
vrml was meant to be the thing you're describing.
for gui, there is xul
and of course svg
which is particularly cool using the mozilla/firefox svg enabled build
(it allows you to mix various namespaces in xml and it knows svg, that is you can embed svg into a page like any other element and manipulate it through dom
Posted: Thu Jan 27, 2005 6:27 pm
Posted: Thu Jan 27, 2005 9:10 pm
X3D - it's funny how this is often overlooked and people end up think microsoft have invented something "new" instead of just bastardising other peoples work.
Posted: Fri Jan 28, 2005 12:53 am
dmoc wrote:X3D - it's funny how this is often overlooked and people end up think microsoft have invented something "new" instead of just bastardising other peoples work.
I used to work with vrml quite a bit, then heard of X3D "the new vrml",
and then a year later I was still using vrml.
What exactly was X3D? how did MS bastardise others work? (serious question, I hate MS more than most)
Posted: Fri Jan 28, 2005 3:25 am
Yeah I know about vrml although I have never used it in web development. Thanks for the link.
Posted: Sat Jan 29, 2005 3:07 pm
The website tells you all you need to know but briefly X3D supercedes but encapsulates VRML (I think there is now a translator). I have not kept up with it lately but I believe the X3D spec has now gone through several iterations including the addition of a binary spec for compression and/or encryption, so I think it's fair to call it mature.
MS, of course, ignore everything but their own "specs" and from the little I have seen (and based on the usual suspicions) XAML is their own "spec" and any similarities with X3D will be accidental (prob also a sacking offence
What's the big deal? Well apart from the all important "interoperability" MS have no design utility for XAML, ie, for Avalon, leaving hand-coding as the only option (so far). But then from the recent XAML\Avalon video it isn't that far advanced (crude in fact, as you would expect from an exercise in re-creating the wheel). Which if people are wise leaves plenty of time for them to adopt X3D as *the* standard.
Edit: By "bastardising" I mean to rip-off instead of adopting "for the greater good" and crediting the X3D standard. If I'm wrong please say so.