This is a king of no-no - etiquette wise -:)
> From: Scott Raney <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> Date: Sun, 28 Jan 2001 11:50:27 -0700 (MST)
> To: [EMAIL PROTECTED]
> Subject: Re: Free movable images and players
>
As it's a kind of feature request. I'm posting it here to gauge the lists
reaction/support for this idea... it comes from some experiments with using
the existing htmlText, and recent explorations of XML and the use of style
sheets with database driven dynamic web sites...
Basically:
1) Can we keep the full HTML in the htmlText property?
2) Can we have some basic support for some limited form of style sheet?
I'm thinking of perhaps <H1>, <H2> .... etc and a styleSheet property which
would format these tagged lines/chunks. Even better would be able to use XML
type logical tags and style sheets, which brings me on to 1)...
I have often had to save two versions of text in a stack - the complete html
and then the htmltext imported into a field. In these cases it would e nice
to set the htmlText to the importedHTML and leav it at that - exporting it
later if required.
I have also used data structures with <tag> markup </tag>, which I have
found useful as they can re-use general purpose data functions for
extracting XML data, and will also display fine without any work.
To give an example:
This is some loose text, which contains an important date:
<mybirthday>12/3/63</mybirthday>. Now setting the htmlText of a field
will display this nicely without the ugly tags.
Also, I can use simple functions to extract information from the text:
put extractTaggedtext("mybirthday", htmlText) into someBirthday
This would be tremendously useful if:
1) A style sheet could format the tagged text
2) the htmlText returned all the tagged text and not as now the text
with all tags not supported stripped from it.
This way outweighs the ability to strip unwanted tags by setting the
htmlText and retrieving it from a field (however handy on occasions)! It
would also empower Metacards ability to be compatible with a key/strategc
subset of web standards - in this case XML, CSS etc.
If anyone on the list can see the value of doing this, speak up now or
forever hold your peace. I think this would be very easy to implement
compared with what Scott et al have planned?
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
