MozillaZine on Skins
Tuesday April 11th, 2000
I have decided to put my own head on the chopping block and weigh in on the Mozilla skins and native widgets debate. To read more, click "Full Article" below.
> it's a platform from which many Internet-ready applications can be created and deployed
Sounds like an OS to me.
What, if I have a speech recognition facitily, that (only) works with my native widgets?
I don't want to give up functionality just for some nice web-integrated look. If CSS requires that (I didn't check it), the spec is flawed.
Apart from that, I think, using native widgets would have saved Mozilla *a lot* of work and bugs in the past and future.
Disclaimer: I'm *not* speaking about XUL, which could (mostly) be implemented with native widgets.
> [...] suffers from this same issue as would any attempt to bridge the platform gap in standardized way
No, (X)HTML is truely XP, standardized and I can still use native widgets.
(It doesn't provide all widget types, but that could be changed.)
> Unfortunately, where they're headed might not be the direction that many people had hoped Mozilla would go.
In fact, I hoped, that Mozilla would give the power back to the user, away from the content provider. But in some cases, the opposite happened obviously.
Maybe, my choice of platform was not arbitarily, but in part based on the widgets and their functionality...
> They can strike out in their own direction, from the Mozilla code available
I guess, removing XPToolkit and using native widgets *within* the browser window and mailnews (not just wrapping with native code) will be a lot of work.
But I know your argument is valid: I can't force Netscape to code the way I want. And I am happy, that Netscape released the 4.x and new code.