insert text dynamically into textarea

[cyprian]

how do i use javascript function to dynamically insert text into
textarea from the result of an array comparison expression. read the
dom but found no way out.
thanks

[Michael White]

cyprian wrote:

how do i use javascript function to dynamically insert text into
textarea from the result of an array comparison expression. read the
dom but found no way out.
thanks

What is a "array comparison expression" ?
More details needed.
Mick

[David Mark]

"cyprian" <cy***********@gmail.comwrote in message
news:11**********************@o11g2000prd.googlegr oups.com...

how do i use javascript function to dynamically insert text into
textarea from the result of an array comparison expression. read the

Regardless of what it is a result of, you can set the value property of the
textarea element.

dom but found no way out.

Try looking up "createTextNode" and "appendChild."

[Randy Webb]

David Mark said the following on 7/22/2007 7:09 PM:

On Jul 22, 6:45 pm, Randy Webb <[e-mail]:

>David Mark said the following on 7/22/2007 2:00 PM:

>>On Jul 21, 9:48 pm, Randy Webb <[e-mail]:
David Mark said the following on 7/21/2007 3:41 PM:
On Jul 21, 2:22 am, Randy Webb <[e-mail]:
>David Mark said the following on 7/20/2007 2:54 PM:
>>One Dumm Hikk wrote:
>>>On Jul 18, 2:05 pm, "David Mark" <[e-mail]:
>>>>"cyprian" <[e-mail] in message
>>>>news:11**********************@o11g2000prd. googlegroups.com...
<snip>

<snip that probably isn't proper>

>>>>I am sure you understand the value of having content in XML as most
of the Web understands RSS (for example.)
And you have not seen me say differently. We are not discussing XML, we
are discussing XHTML and - directly - it's use as a language on the Web.
As I am sure you know, XHTML is XML. That's the whole point. Just
like RSS and XHTML Basic are XML. You can easily transform one flavor
into another, but you can't efficiently transform HTML into anything
useful.

That is why I don't store static HTML. To do that is idiotic if you want
to transform it.

So what do you store then? I assume XML, which would mean your server
has to transform it to HTML with each request.

Actually, there are very very few HTML files on the Intranet server that
I use. Most of the data is stored in a database and creates .js files on
the fly. Everything in the system was designed with two things in mind -
speed and server load. The more I can make the client machine do then
the less my server has to do. Switching to the current back end system
(the front end looks almost identical to the old version) took almost 3
years and more hours of work than I care to remember. It has sped up my
Intranet almost 10-fold by moving the processing load from the server to
the client machine.

The public website is slowly being migrated to the same system of using
..js files loaded on the fly. I have found it to be simpler, more
reliable, and quicker than trying to make XHR requests and deal with the
response. The major issue with the website being migrated is the lack of
support and problems with loading .js files on mac platforms and some of
the older legacy PC browsers. If, and when, the support becomes more
available on mac browsers and the legacy PC browsers are finally dead
and gone, the website will be switched to the same system as well.

As for transforming XML to HTML, you might try looking at the
process.wsf file and the index.xml file that is used to create this very
groups FAQ. Edit the xml file, run the process.wsf file, and it creates
the HTML file on the fly for you. So no, I don't buy into the "Its
easier to transform XML to XHTML than HTML" argument.

<snip>

>>It seems to me that the real concern of the "XHTML is harmful on the
Web" crowd is that 90% of the authors don't know what it is. But that
is not my concern.

<URL:http://www.spartanicus.utvinternet.ie/no-xhtml.htm>
Try it and the links in it......

I've seen many sites just like it. That particular one seems outdated
as it warns about Opera 7, which prefers HTML (not a problem if you
negotiate properly.) The latest Opera browsers prefer XHTML.

While it is slightly outdated, the only information on that page that is
still outdated is indeed the warning about Opera 7. The other issues
that it brings up are still valid issues for not serving XHTML on the
web though. If you want to serve XHTML on the web, by all means do so.
Just don't expect to push it here in comp.lang.javascript without being
challenged on it as the benefits of XHTML simply are not worth the
effort when it comes to trying to serve it to IE and causing IE to bog
down to try to parse it as tag soup HTML.

--
Randy
Chance Favors The Prepared Mind
comp.lang.javascript FAQ - http://jibbering.com/faq/index.html
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/

[David Mark]

On Jul 23, 1:23 am, Randy Webb <[e-mail]:

David Mark said the following on 7/22/2007 7:09 PM:

On Jul 22, 6:45 pm, Randy Webb <[e-mail]:

David Mark said the following on 7/22/2007 2:00 PM:

>On Jul 21, 9:48 pm, Randy Webb <[e-mail]:
David Mark said the following on 7/21/2007 3:41 PM:
On Jul 21, 2:22 am, Randy Webb <[e-mail]:
David Mark said the following on 7/20/2007 2:54 PM:
>One Dumm Hikk wrote:
>>On Jul 18, 2:05 pm, "David Mark" <[e-mail]:
>>>"cyprian" <[e-mail] in message
>>>>news:11**********************@o11g2000prd. googlegroups.com...
<snip>

<snip that probably isn't proper>

>>>I am sure you understand the value of having content in XML as most
of the Web understands RSS (for example.)
And you have not seen me say differently. We are not discussing XML, we
are discussing XHTML and - directly - it's use as a language on the Web.
As I am sure you know, XHTML is XML. That's the whole point. Just
like RSS and XHTML Basic are XML. You can easily transform one flavor
into another, but you can't efficiently transform HTML into anything
useful.
That is why I don't store static HTML. To do that is idiotic if you want
to transform it.

So what do you store then? I assume XML, which would mean your server
has to transform it to HTML with each request.

Actually, there are very very few HTML files on the Intranet server that
I use. Most of the data is stored in a database and creates .js files on
the fly. Everything in the system was designed with two things in mind -
speed and server load. The more I can make the client machine do then
the less my server has to do. Switching to the current back end system
(the front end looks almost identical to the old version) took almost 3
years and more hours of work than I care to remember. It has sped up my
Intranet almost 10-fold by moving the processing load from the server to
the client machine.

What do JS files have to do with the XHTML vs. HTML discussion?

>
The public website is slowly being migrated to the same system of using
.js files loaded on the fly. I have found it to be simpler, more
reliable, and quicker than trying to make XHR requests and deal with the
response. The major issue with the website being migrated is the lack of
support and problems with loading .js files on mac platforms and some of
the older legacy PC browsers. If, and when, the support becomes more
available on mac browsers and the legacy PC browsers are finally dead
and gone, the website will be switched to the same system as well.

As for transforming XML to HTML, you might try looking at the
process.wsf file and the index.xml file that is used to create this very
groups FAQ. Edit the xml file, run the process.wsf file, and it creates
the HTML file on the fly for you. So no, I don't buy into the "Its
easier to transform XML to XHTML than HTML" argument.

That wasn't my argument. Of course you transform XML into HTML. What
is silly is transforming XHTML into HTML, when you could just send the
XHTML.

>
<snip>

>It seems to me that the real concern of the "XHTML is harmful on the
Web" crowd is that 90% of the authors don't know what it is. But that
is not my concern.
<URL:http://www.spartanicus.utvinternet.ie/no-xhtml.htm>
Try it and the links in it......

I've seen many sites just like it. That particular one seems outdated
as it warns about Opera 7, which prefers HTML (not a problem if you
negotiate properly.) The latest Opera browsers prefer XHTML.

While it is slightly outdated, the only information on that page that is
still outdated is indeed the warning about Opera 7. The other issues
that it brings up are still valid issues for not serving XHTML on the
web though. If you want to serve XHTML on the web, by all means do so.
Just don't expect to push it here in comp.lang.javascript without being

I don't push anything in here. I think the original discussion arose
from some silly tag line of yours that insulted anyone and everyone
who used XHTML on the Web. So don't expect to do that without being
challenged. Or perhaps you can as I am growing weary of this whole
argument.

[Randy Webb]

David Mark said the following on 7/23/2007 2:25 PM:

On Jul 23, 1:23 am, Randy Webb <[e-mail]:

<snip>

>>So what do you store then? I assume XML, which would mean your server

^^^^^^^^^^^^^^^^^^^^^^^^^^

>>has to transform it to HTML with each request.

Actually, there are very very few HTML files on the Intranet server that
I use. Most of the data is stored in a database and creates .js files on
the fly. Everything in the system was designed with two things in mind -
speed and server load. The more I can make the client machine do then
the less my server has to do. Switching to the current back end system
(the front end looks almost identical to the old version) took almost 3
years and more hours of work than I care to remember. It has sped up my
Intranet almost 10-fold by moving the processing load from the server to
the client machine.

What do JS files have to do with the XHTML vs. HTML discussion?

See the question you asked? The one where you asked "So what do you
store then?". You asked a question, I answered and explained some of why
I chose that path.

>The public website is slowly being migrated to the same system of using
.js files loaded on the fly. I have found it to be simpler, more
reliable, and quicker than trying to make XHR requests and deal with the
response. The major issue with the website being migrated is the lack of
support and problems with loading .js files on mac platforms and some of
the older legacy PC browsers. If, and when, the support becomes more
available on mac browsers and the legacy PC browsers are finally dead
and gone, the website will be switched to the same system as well.

As for transforming XML to HTML, you might try looking at the
process.wsf file and the index.xml file that is used to create this very
groups FAQ. Edit the xml file, run the process.wsf file, and it creates
the HTML file on the fly for you. So no, I don't buy into the "Its
easier to transform XML to XHTML than HTML" argument.

That wasn't my argument. Of course you transform XML into HTML. What
is silly is transforming XHTML into HTML, when you could just send the
XHTML.

We are right back where we started. Sheesh. You have two choices:

1) Send HTML to any browser.
2) Send XHTML to a browser that doesn't understand it and parses it as
tag soup so that 10% of the web can use XHTML.

The latter isn't worth the time and effort.

><snip>

>>>>It seems to me that the real concern of the "XHTML is harmful on the
Web" crowd is that 90% of the authors don't know what it is. But that
is not my concern.
<URL:http://www.spartanicus.utvinternet.ie/no-xhtml.htm>
Try it and the links in it......
I've seen many sites just like it. That particular one seems outdated
as it warns about Opera 7, which prefers HTML (not a problem if you
negotiate properly.) The latest Opera browsers prefer XHTML.

While it is slightly outdated, the only information on that page that is
still outdated is indeed the warning about Opera 7. The other issues
that it brings up are still valid issues for not serving XHTML on the
web though. If you want to serve XHTML on the web, by all means do so.
Just don't expect to push it here in comp.lang.javascript without being

I don't push anything in here. I think the original discussion arose
from some silly tag line of yours that insulted anyone and everyone
who used XHTML on the Web.

It arose from my opinion that I stated in a signature. It was based on
my personal experience and reading. And, anytime anyone suggests using
XHTML on the web, until it is supported by IE, I will state that opinion
again.

--
Randy
Chance Favors The Prepared Mind
comp.lang.javascript FAQ - http://jibbering.com/faq/index.html
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/