On the other hand, consider the RichEdit control. This is an edit control that can display text formatted using RTF in an edit control. Now, it makes perfect sense to have a control that displays HTML formatted text.
As far as toolbars are concerned, the problem with putting the logic for them in the OS is that there isn't much shared logic associated with them to begin with! The intrinsic logic that a toolbar represents is very small - most of its logic is app specific.
You completely give in to my point by suggesting that Netscape's implementation may be "less sophisticated" (and they are even in the HTML rendering business!). First, think of all the other apps that want a quick way to display HTML. Clearly, it doesn't make sense for these folks, who are trying to build a very task specific app, to invest in HTML rendering engines. For them, having this support in the OS is a huge, huge benefit. Second, notice that no-one is forcing you to use this HTML rendering engine that comes with the OS, as you yourself are pointing out - Netscape uses its own, so more power to them.
Finally, if Judge Jacka-- really understood this, why the injunction (that was overturned) last year? |
