HTMLtext doesn't play well with CSS
jimaultwins at yahoo.com
Sat Jul 17 09:36:03 CDT 2010
I think I get it. The user makes changes in a field, then uploads the
HTMLtext version for web display.
You need to remember that the HTMLtext was created many years ago for
Rev field rendering, and not for web browsers.
So let's take an approach in Rev that I use for other purposes but may
Rev is a very powerful text chunk engine, so use HTMLtext during the
casting of text blocks, then convert to valid HTML, etc before
sending. I don't have any experience using HTMLtext. If the real
issue is that the tags look good before uploading but then the CSS
does not work when inserted in the page, there may be something going
on that I am missing.
There is no wheel that I know of, and I have been listening to this
list for about 6 years.
Since this is a Rev list and not a web geek list, why not contact me
off list so we can work on a solution, then come back to the list with
the answer. There will be many who will be interested in the result,
but not a long thread.
Let me know if this helps.
I will be happy to build and modify web pages on one of my test sites
to see what possible solutions we can find>
Does this sound good for you?
On Jul 17, 2010, at 7:00 AM, Tim Ponn wrote:
> OK...let me explain more fully...
> There are web geeks (myself included) who create and/or maintain web
> sites. www.historicalengine.com and www.grandvalleytractor.com are
> two of mine. The creation is quite easy with all the drag and drop
> tools available out there. I usually tweak (sometimes heavily,
> sometimes not so) the graphics or the resulting page code. When
> it's finished, I turn the "keys" to the site over to whoever owns
> it. Unfortunately, 99.9% of the time they are clueless to web
> geekery. By the time you get to the "t" in "ftp", their eyes have
> glazed over and they're drooling...much the same as I look when an
> accountant utters more than 2 syllables to my engineeringness. ;=)
> So, when it comes time to update the site, they return to my
> doorstep. Not a big deal if it's once or twice a year...but when
> it's a club site...or the site for a bowling league...or the
> like...I can get requests every day! And the changes are, in these
> cases, dirt simple..."Could you put these latest scores on the
> site?" or "Here's this months newsletter!"
> The solution I'm cobbling together:
> In a sentence...Let them do it themselves. When I create the site,
> I insert a comment (or many, if required..maybe one per bowling
> team...whatever) like "<!--whevIn--><!--whevOut-->" someplace on a
> page. My simple rev app contains a field and a button. There's
> significant password protection, blahblah, going on that I don't
> need to get into here. There's additional stuff going on also...win/
> loss percentages...rankings...blahblah. But, the bottom line
> is...ANYBODY who can enter text and click a btn can update a page,
> or a range of pages or a portion of a page. My app gets the
> url...inserts the text field at the "markers" I've left...then ftp's
> it back up to the site. Simple.
> Right now, it's just text, but I may add graphics later..jpegs,
> gifs, whatever.
> Now, to clarify my original question:
> I want the user to be able to change font sizes, make bold, italic,
> whatever. I also want them to have the freedom to turn some of the
> text into links, etc. When I try to use HTMLtext in rev, the
> results are not so good. How do I improve it? I mean, if I have to
> roll up my sleeves and just write it all...fine...but is there a
> wheel that somebody has created already out there?
> I doubt it matters, but...17" MacBook Pro/Snow Leopard 10.6.4/Rev
> Enterprise 4.5.0-dp-3
> On Jul 17, 2010, at 8:30 AM, Jim Ault wrote:
>> On Jul 17, 2010, at 5:05 AM, Tim Ponn wrote:
>>> Hello all!
>>> I'm trying to use the HTMLtext of the contents of a field to
>>> modify a CSS web page, and it butchers font sizes and style. Is
>>> there something other than HTMLtext that I should be using?
>> HTMLtext is a subset of HTML tags that Rev uses to do formatting in
>> fields. It is not meant to be compliant with browsers, especially
>> the modern day versions.
>> When you render the web pages, do you then run compliance checking?
>> Very like you have quite a few conflicts, especially if the DOCTYPE
>> is beyond 1.0
>> other CSS will get applied.
>> Your description of your process is quite vague, so it is difficult
>> to be more helpful.
>> Do go to one of the many compliance checking sites, enter the url,
>> and follow the bouncing error messages, if any.
>> Also visit http://quirksmode.org to study the interpretation
>> variations that each browser.version uses. The most variant is IE
>> in its many versions.
More information about the use-livecode