"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:
> because of the upcoming web server switch to an off-site data center,
> which is going to require a reduction in the number of ElevateDB
> downloads that need to get uploaded with each new build.  

Ouch! sounds to me like you need an intermediate destination! uploading to
in-house box that uploads the final files when a control file appears, so
some such. I'm sure you've thought of that though. Actually, one thing I
was advised to do recently was to use version control for deploying. It
allows you to deploy to a test server, verify, and then know that the live
will be good, and if not you can roll back anyway. I did this with my first
big EWB project, which unfortunately got canned. Unlike the next one, I
hope.

Anyway, enough teaching egg sucking for one day. 8-)

--
Matthew Jones

Can I revisit this please? IE is showing duff info again for me. Neither #13 + #10
nor plain #10 works. The DOM shows that the text has nothing there, but that may be
the copying from the browser.

Anyway, if I build up the string in a variable, and assign it in one go, it works
fine. I think that if the TLabel is unable to reliably read what is in the DOM that
it should cache the value in a variable. Perhaps a special procedure to
"ReadFromDOM" might be handy for those special occasions when it has been
externally updated, but I can't see much downside to having a local copy.

FWIW, the lines have to be built up with both #13 + #10 to work in Chrome and IE
like this.

/Matthew Jones/

Matthew,

<< Can I revisit this please? IE is showing duff info again for me. Neither
#13 + #10 nor plain #10 works. The DOM shows that the text has nothing
there, but that may be the copying from the browser. >>

Example project please (or point me to the previous one, if necessary), and
then I can see what's going on.

<< Anyway, if I build up the string in a variable, and assign it in one go,
it works fine. I think that if the TLabel is unable to reliably read what is
in the DOM that it should cache the value in a variable. Perhaps a special
procedure to "ReadFromDOM" might be handy for those special occasions when
it has been externally updated, but I can't see much downside to having a
local copy. >>

I'll see what I can do.  I cache everything else in the DOM already for
performance reasons, so it's not a big stretch.

You'd think that the browser vendors could come up with a standard regarding
line feed handling, but.....

Tim Young
Elevate Software
www.elevatesoft.com