>> If you care so much about Mozilla XUL why don't >> finish up what you started?
> Time constraints mainly. Ian, that says it all. If you care about XUL and if XUL is important too you than you make it a priority. Saying you're too busy with other things just shows you don't give a damn. Why not, for example, give up your day job and start your own business? After all XUL is the future, isn't it? >> Can you put some evidence behind your claim? >> Where, for example, can I >> find the Mozilla XUL mailinglist? What changes >> have been made to the spec recently? > > Most of the current XUL work is being done within > standards organisations > with strict NDA policies. If you are a ISO, W3C, > ECMA, or IETF member let > me know and I can show you the relevant links if you > are a member of the > appropriate one. Whom do you try to intimitate? IETF works using mailinglists using a "no kings and queens" policy. Can you point me to some posts that touch on XUL? Or how about ISO? Is ISO cooking up a XUL spec for 2025? Just get real. If you design XUL using a closed door policy you're not getting anywhere. All it breads is such arrogant posers like you are. > Actually I am intimately familiar with the reasons > behind Apple's decision > to use KHTML to develop Safari, and can assure you > XUL was not related to > the decision at all. That they immediately hired one > of XUL's editors, and > that said editor is still working on XUL, should > tell you whether they > consider XUL a threat or not. Ian, you're clueless. Apple, of coure, won't come out and say XUL is a platform threat. The same holds true for IBM, Sun, Microsoft and so on. If Apple supports XUL how come they don't even use it? Also Apple hired David Hayatt not because he is the XUL "editor" but because he has been the core Gecko HTML render engine developer. Why not ask David if Apple allows him to sneak in XUL into Safari for some enlightenment? > I'm still waiting for your "open XUL" effort to > begin, not to mention > still waiting for the answers to the two e-mails I > sent many months ago on > this mailing list. Ian, the XUL Alliancen uses a different approach to standardization. First, you build XUL motors/browsers/runtimes and then you work on interoperability and later on standardization. It's all well underway. - Gerald PS: If you report to the CTO at Opera why not show him the light and add XUL to your browser. ------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ _______________________________________________ xul-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xul-talk
