Hello, I invite you to post your questions for the next XUL Titan interview with Marc Clifton.
In case you haven't heard about Marc Clifton, Marc leads the MyXAML project that let's you build UIs for Mono/DotGNU/.Net using XML markup. Find out more online @ http://www.myxaml.com For more info about the XUL Titan interview series I invite you to browse over the latest episodes online @ http://xul.sourceforge.net/interviews.html For more info about Marc Clifton you might stop by at the MyXAML et al blog online @ http://myxaml.com/marcclifton Finally to give you a flavor of Marc's thinking. Allow me to quote a Marc's comment post to a Longhorn blog MyXAML annoucement: Well, as the author of MyXaml, I'll throw in my 2c on the issue of declarative markup. While things like XUL have been around, what's unique is the combination of using markup with a reflection capable language (Ok, maybe they've been doing this with Java for ages, but I don't know about that). XUL's concept of events is closely related to scripting, and databinding is accomplished with XBL. So, I personally don't find XUL a very unified approach, and it seems too close to Java and scripting. But to each his own. What I do find attractive about using a language like C# is that the parser can instantiate any class in any namespace, set properties and wire up events. In some ways, this is the ultimate "plug-in" architecture. Using reflection, there is no need for an underlying class object model. The combination of reflection and markup is quite powerful, and I'm not sure I've even grasped the power of it. For example (if I may digress), a friend of mine is writing a state machine that can be expressed declaratively. I can now define the state systems using markup. Someone can write a slick designer that serializes to MyXaml, and voila, a useful product! The applications for this reflection/markup alliance are unbounded. I also like the ability to change the form (and even the events!) at runtime. This is a natural extension to the ability to change the code while in the debugging session--if I don't like the way a dialog appears, or the I need to add something to the event handler, I can do so without terminating the program, making the changes, recompiling, re-executing, and re-initializing whatever state the program was in. The feedback I'm getting from MyXaml is that people also like it for generating custom GUI's on the fly, for managing variations of the program, but having one EXE for different user interface requirements, etc. And I like it for the really clean separation you get between the user interface implementation and the presentation layer logic. As for a designer, well, of course a lot of people aren't going to use markup directly without a designer. What's surprised me is that there are quite a few people that don't mind. But not having a designer is being addressed by MyXaml. Personally, I find the markup really easy to work with. Maybe I can get a handicapped permit for being "designer tool challenged". - Gerald ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ xul-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xul-talk
