Full Article Attached Mail/News Performance Effort Underway

Friday November 2nd, 2001

Seth Spitzer today sent an update out about what the Mail/News team is doing to meet their goals for Mozilla 1.0. They'll be focusing almost 100% of their effort for at least the next two milestones (0.9.7, 0.9.8) on Footprint and Performance of the various parts of Mail, News, and Addressbook. Not only will they be focusing on it, they'll also be locking down their part of the tree and only accepting performance or footprint fixes. Very few exceptions will be made. Click the Full Article link to see Seth's full post.

#177 Re: Re: Re: Re: Re: Re: please

by strauss

Thursday November 8th, 2001 4:31 PM

You are replying to this message

> Fully implement the DOM event model (e.g., allow capturing mouse clicks in widgets). <

I've written plenty of event handling code in Windows and Mac and don't know what problem you're referring to here. The system hands the event to the application first.

> support background images in edit controls <

Background images _in_ widgets is not a CSS feature. The background of a widget is what it's drawn above, not what's drawn inside it.

> clip and z-order widgets properly <

Widgets are drawn in a z-ordered fashion on both Mac and Windows. Please note, however, that overlapping widgets is almost always a design mistake.

Clipping is fully controllable through the GrafPort or drawing context. However, please note that clipping to only part of a widget is also a design mistake -- even more so on a theme-switching system where you can't anticipate what will be shown and what removed. Clipping out the whole thing is fine, and trivial to do.

> render widgets covered by overlapping translucent images <

What problem do you anticipate there? If you have translucency, you have to draw to an offscreen pixmap in layer order, but that's the same with or without widgets, and has long ben a standard drawing mode on both platforms.

> create 500 comboboxes instantly <

Instantly? You sure you're a Mozilla user? Anyhoo, I don't see what's faster about creating 500(!) XUL widgets as opposed to native widgets.

> make sure you can put arbitrary amounts of Unicode text into a text widget <

Text editing is a special case and most applications do roll their own when they have to do this kind of thing.

There aren't any CSS requirements that are broken by native widgets. In fact CSS3 rerquires using the platform standard appearance.

> I think the ultimate proof that native widgets are not the way to go is that Microsoft themselves don't use native widgets in IE! ... They only have to support one platform... <

Microsoft does use native widgets in IE, and they support more than one platform.