Thinking Inside-out of the Browser

[Ben Rubinstein]

on 16/3/03 6:01 am, Jim Lambert wrote

> If Rev's HTML renderer were just a teensy bit more compliant it'd be fine
> for displaying simple webpages that had to do double duty - say, within a
> Rev app and on a site. That'd work on any platform and be somewhat like a
> basic browser within Rev.

Oh, please don't do this.  I really want to campaign for the htmlText
keyword to be deprecated, and an alias (eg "markedUpText") added and pushed.
The htmlText property is an excellent and handy way to get or set text with
all the stylistic attributes at once; but I'd prefer it was documented as
using a set of conventions that just happened to resemble HTML.  It isn't an
HTML renderer, and I don't think it ever will or should be; and of course,
because Rev supports a number of text attributes that aren't in HTML, so the
conventions supported by the 'htmlText' property include some things that
just aren't HTML.

An HTML render object, or a browser object, would be a splendid thing.  But
I wouldn't want it to be built directly in Rev/MC (huge diversion of
critical engineering resources on to a never ending path); and it shouldn't
be confused with the handy property for accessing styled text of a field.

 
  Ben Rubinstein               |  Email: benr_mc at cogapp.com
  Cognitive Applications Ltd   |  Phone: +44 (0)1273-821600
  http://www.cogapp.com        |  Fax  : +44 (0)1273-728866