Hi Alex, Yeah, was sitting here working away when the email came in, and I thought, wow, cool. My only comment about what you wrote is that I shouldn't have said C#--any language that's CLR compliant would work. Don't like VB? How about Cobol.NET, hehehe.
> Your quick response and plugging of your own project seems to reinforce my > idea of hitting upon something interesting, worth exploring further :) Definitely. There's a lot of activity in this area, obviously. Charles' comment about being late to the party (paraphrased) is probably applicable to MyXaml as well. However, since there isn't any definite leader of the pack (at least not that I'm aware of), there's a lot of opportunity. I wonder though, is attempting to create a code base that produces, as you said, "a language/platform/UI-agnostic" development platform all that helpful? In general, is providing a widget library for a specific XUL implementation the right approach? MyXaml is agnostic in the sense of what it interfaces with, so my customers can use third party components and keep up to date with both the changes coming down the pike from Microsoft and from third party component developers, such as VG.net, DevExpress, Infragistics, DevComponents, Genghis, etc. To me this offers real sustainability in using the MyXaml architecture for your product development. What concerns me with the some of the XUL implementations that I've seen, is that they come bundled with their own widgets. It also lets the customer choose the UI package, not the XUL vendor. For better or worse, I'd prefer to leverage the components that other people develop and maintain. I think that's one thing that separates MyXaml from other implementations. Heck, it even separates MyXaml from MS-XAML, because MS-XAML seems so tightly bound to Avalon and Longhorn. I've yet to see one of the Longhorn bloggers demonstrate using MS-XAML with a third party component. (cliché alert!) They talk the talk, but they don't seem to walk the walk. As to the inevitable "there are a lot of third party XUL widget developers out there", well, I don't totally buy into that. People/companies buy packages from DevExpress and Infragistics because of the tech support, among other things. "Free" often comes with a price, that's more expensive than a commercial product. Thoughts? Marc -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex de Landgraaf Sent: Monday, June 21, 2004 1:12 PM To: [EMAIL PROTECTED] Subject: RE: [xul-talk] Project FopSpeen - Why Not? Hi Xul people, Quoting Marc Clifton <[EMAIL PROTECTED]>: > Actually, I have another comment to make about the FopSpeen project. Why go > through all those hoops illustrated in the diagram? Use .NET/Mono for the > UI, use MyXaml for the scripting interface, and use C# for the client side > scripting. You can eliminate all the different layers in the FopSpeen > design diagram, and get your apps working with a browser and desktop > solution simultaneously, under multiple browsers and desktop OS's. Simple: because not everyone wants to use C# (or VB, heaven forbid) as their scripting language. My little 'thought-experiment' was to see if people would think a language/platform/UI-agnostic way of building rich-client webapplications would be at all possible (or worth striving for, even). The whole .NET/Mono framework, although impressive, won't be able to encompass all other languages, although it would narrow the amount of development necessary (which is why I also mentioned Parrot as a likely candidate). In my design I strived for an architecture that would be as flexible/extendable as possible and would push XUL forward down the road of both KaXul/desktop applications and more useful web applications, free for both closed and opensource applications, buildable using any existing scripting language. If anyone can point me towards such an existing project, I'm all ears :) Your quick response and plugging of your own project seems to reinforce my idea of hitting upon something interesting, worth exploring further :) cheers, Alex PS. please send a CC this way when replying, as I'm not on the list ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ xul-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xul-talk ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ xul-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xul-talk
