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.
#212 Re: Re: Re: Re: Re: Re: Re: Re: please
Friday November 9th, 2001 2:04 PM
You are replying to this message
Things you're saying are dangerous are in my experience things that are normal. In many cases they're things that have long been encapsulated in COM objects in the Platform SDK, like offscreen drawing. You seem to be talking about an implementation strategy that uses only the base Windows API from 3.x rather than the current state of the API.
I don't use VB, thank you very much, and yeah, that is fairly insulting. All my Windows development from 3.1 to the present has been in C++.
I will, on reflection, modify a couple of points. Partial clipping of widgets could be important to animation effects such as wipes. You woudln't want to leave them in that state but during intermediate states you'd definitely want to show a clean line. I don't see that you've demonstrated a problem doing that, though. Ditto for z-ordering, since during animation widgets might fly over each other. Again, no problem with doing that has been demonstrated.
GDI heap overflow was a serious bug in Windows in past versions, to be sure. Theoretically you can render more complex web pages on those older versions w/o using native widgets because that bypasses the OS bug. However, I don't think that a 500-widget edge case on older OS versions justifies a complete abandonment of platform standards.
The CCS3 user interface proposal is at <http://www.w3.org/TR/css3-userint> . It calls plainly for "system default look and feel." Looks like they got some UI guys involved in this one. (Finally....)
Windows IE uses native widgets. They may very well roll their own text editing -- most serious applications do, on either platform. The base text editing capabilities on either Mac or Windows are suitable mostly for small text fields. Why don't you try looking for buttons, scroll bars, etc. in addition to text fields, though?
Oh, and BTW, there is a code fork between the Windows and Mac IE platforms, but not a "completely separate code base." I know this from working directly with the Mac IE engineers on a project at a previous company. It's more of a fork than Mozilla would like to have, and so it doesn't bear directly on the feasibility of a platform-independent widget layer, but it does show that they were able to use native widgets on both platforms.