Windows Forms Markup Language (WFML) provides an extensible mechanism to add a markup model on top of an existing .NET Framework object model. WFMLs parsing rules can be summarized as “XML elements map to .NET Framework types and XML attributes map to Type properties (or events)”. This sample includes a WFML parser that dynamically generates an object instance tree from an XML file in WFML format.
Using Windows Forms Markup (WFML)
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
Is there a good intro anywhere explaining just what .NET is and where this is all going–even for the user? It looks like it’s going to be a huge part of Longhorn and I feel like I’m being left behind.
http://www.microsoft.com/net/basics/
How come when Microsoft come up with a copied implementation of something old, it’s news worthy and innovative. Mozilla has been using this ever since the redesign. It’s called XUL. Check it here http://xulmaker.mozdev.org/ and here: http://www.xulplanet.com/
It’s because its going to have a big impact on the it world and how window’s development is done (well thats my take on it). I agree with you though. There’s too much crap being posted nowadays (Anyone want to learn how to install Mandrake 10.0? *grin*).
OT: How different is XUL and the M$ way of doing it?
Gareth
How different is XUL and the M$ way of doing it?
The MS way of doing it uses the .NET object model. XAML/WFML are just another .NET language. They’re declarative equivalents of VB.NET/C# or other .NET languages.
Calling XAML/WFML a copy is XUL would be like calling C# a copy of javascript.
It’d also be like calling C# or another .NET language a copy of XUL
In fact, I would call C#/CLR a copy of Java/JVM + some improvements and some mistakes… but nevermind
There’s a few xml described gui implementations for java including http://www.swixml.org/“>swixml thinlet” rel=”nofollow”>http://www.thinlet.com/”>thinlet. Look here for a more complete listing of http://xul.sourceforge.net/“>”XUL
What’s the difference between glade and WFML?
A Pre XAML XML. XAML is for the Avalon API, this is for the existing Windows Forms. Made possible by the Partial Types supported in Whidbey.
The MS way of doing it uses the .NET object model. XAML/WFML are just another .NET language. They’re declarative equivalents of VB.NET/C# or other .NET languages.
Calling XAML/WFML a copy is XUL would be like calling C# a copy of javascript.
No, these languages in .NET simply bind to the markup. Take your pick. The only reason that they are specific to .NET is because MS wanted it that way. Like one poster suggested this is much like glade. Same goes with XUL. Define your interface with xml and bind whatever language (JavaScript, Java, C, C++). Prolly in the near future, C# will bind to XUL using Mono on the Linux platform. This is old news.
I don’t get the impression that this is an official technology. I can’t find any more references on MS’s sites and the article includes source for the parser. Sounds to me like its just a sample implimentation of the “XML markup for GUI” idea.
If you take a look at the source, its rather nice that this much functionality was done with so little code.
Are there any good links on the net concerning the use of WFML with vb.net instead of c#?
This is not an “official technology” and this is not something we’re including in the next version of Windows Forms. This is a sample that demonstrates a technique for dynamically generating Forms from XML (a common request from customers).
The sample is language agnostic and works equally well with VB and C#.