|
Well, we're really talking about two different objects here, both based on the RichEdit control.
Rod mentioned that he wanted a RichEdit object that can be "programmed" with funky (raw) RTF encoding. And the HTMLView object is "derived" from the RichEdit object, but adds value in that it can be programmed with a subset of HTML - the HTML engine would generate RTF codes under the covers but wouldn't expose the raw RTF interface itself.
So I guess what I'm wondering is what would be more usefull. A RichEdit object with an RTF interface or a RichEdit object with an HTML interface.
Haven't heard back from Rod in terms of what he has planned ... raw RTF encoding (imho) seems to be pretty powerfull ... was reading-up on some of the links he provided ... T think you can even encode bitmaps as RTF strings (or as Kixtart $variables) ... and have them display inside the RichEdit window ... pretty powerfull stuff.
From my perspective, the RichEdit with its simple raw interface would be the quickest and (probably) most stable object to implment next. But the HTMLView object has an appeal as well. At the end of the day - both will be there - question is - which one first.
[ 19. September 2002, 18:19: Message edited by: Shawn ]
| 
