Hi,
If you think XAML is three years off think again.
Xamlon, Inc. just released Xamlon Beta that you can
use to "script" today's Microsoft .Net 1.1 toolkit
using XML tags.
To quote from the project page:
What is Xamlon?
Xamlon (pronounced "Zamelon," which rhymes with
"avalon"), is a XAML runtime library for the .NET
Framework 1.1. Xamlon is not a 100% XAML compatible
library, it was not designed to be, but rather uses
the same syntax as XAML to provide the same power and
capabilities as XAML but for building
"Windows.Forms"-based applications instead. Simply
put:
"Xamlon is XAML for Windows.Forms"
There are several key benefits of using Xamlon today:
* Application development becomes much more simple and
efficient. Xalmon provides a very clean separation
between presentation and application logic.
* Xamlon application run on all of today's .NET
Framework 1.1 Windows operating systems: Windows 98,
ME, NT, 2000, XP, and Server 2003.
* Xamlon provides a much simpler migration path to
Microsoft's next-generation presentation layer in
Longhorn, XAML.
Xamlon is not a XAML port or 100% compatibility
library, but rather a subset of XAML that allows for
the development of Windows Forms application using the
same XML markup syntax as XAML.
How does Xamlon work?
Unlike Longhorn's XAML, Xamlon does not convert your
XAML markup to C# (or Visual Basic.NET). Instead,
Xamlon interprets your XAML at run-time very
efficiently to dynamically create your application
interface(s).
Your logic and event handling code is specified as
"Class Behind" files, much like ASP.NET's or XAML's
"Code Behind" attribute. The class that handles the
event handling can be written in any .NET language.
By interpreting your XAML documents during runtime,
this affords your great flexibility in how you deploy
your application. You can embed your .xaml files as
resources, leave them intact on disk to load at
runtime, dynamically load them from the internet, and
so on.
Because Xamlon interprets the code at run-time, logic
code (i.e. C# / VB.NET) cannot be inserted into the
XAML markup, but rather needs to live entirely in the
class behind file. This ultimately leads to cleaner,
easier to read XAML.
and so on and so forth
Full story @ http://www.xamlon.com
- Gerald
PS: It's not clear yet who is behind Xamlon, Inc.
However, one thing is for sure. It won't be a freebie
as the "How do I get Xamlon?" page states:
Xamlon is currently in beta. Closer to the release
date, Xamlon pricing will be determined. Xamlon is
licensed per developer and has no runtime licensing fees.
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
xul-announce mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xul-announce
