On Apr 5, 12:44 pm, "Jukka K. Korpela" <jkorp...@cs.tut.fiwrote:
Scripsit Dudely:
You're welcome. Now please learn to quote on Usenet: quote the relevant
sentence or two _before_ your own message.
I'll try, but I'm afraid we have a difference of taste/style. If in
fact there is a particular thought/idea/sentence that can be isolated
from the rest of the text without losing context, then yes what you've
stated works for me too. When however the entire post is essentially
necessary to maintain the context, I quote the whole thing and respond
at the top. Why?
When I'm reading through a thread, I don't want to have to page down
each message to get to the new text. I find it somewhat irritating,
and unless I'm truly 200% interested in the thread, I won't bother to
read through it to find the new material. I want to see what's new at
the top, so I don't have to spend time constantly paging down to get
to what may or may not be useful material, hidden amongst the old
text. So to me, it's a courtesy for others to do it that way, and
therefore I try to extend the same courtesy to others.
Perhaps you can't. But you can suggest omission of the scrollbars by setting
body { overflow: hidden; }
in a stylesheet for the _embedded_ document. Before doing so, think about
the consequences: such a setting would procrustinate the content if it
doesn't fit, and can you really know whether it fits?
That's an interesting idea. It will work for static text, and/or
other content that has a fixed display height. Headers, footers, and
simple repetitious paragraphs come to mind. Not to mention certain
"windowed" content areas, that are fixed in height; the "headings" and
rows supplied are always the same, but the actual info. changes.
Example: Weather reports (temp./high/low/wind direction/wind speed,
etc.).
P.S. I'm afraid you're using <objectas a method of including an HTML
document in another.
Yes I am.
Though successful to a fairly limited degree, that's
not the right approach; use server-side includes, preprocessing, or just
redesign the site so that you don't need such inclusion.
Actually, I originally designed it to use SSI. Then along came a
third party application which is designed using PHP, that I wanted to
integrate into my site. It turns out, that I have to rewrite all of
my pages to fit into this PHP application. The application won't
parse SSI, I can't get it to recognize .shtml files.
I have in fact redesigned the site so that I don't need the inclusion
- however I'm horribly disatisfied with the results, as it's big &
ugly - the precise reason why I used SSI in the first place. I've
even tried PHP includes as an SSI replacement. Doesn't work. I
probably have to rename all of my .html files to .php and rewrite them
as well, in order to use PHP includes; but that's an experiment I just
can't afford to spend the time on.
The third party application sold me on itself, by advertising simple
integration into existing sites (plus the fact that there isn't
anything else available that offers the equivalent functionality).
There was no mention of having to redo all of my work. I guess the
3rd party app. never considered anything beyond simple .html files
which could be cut & pasted.
When someone mentioned objects to me, I jumped on it based on the
specification of what it was supposed to be able to do. It appeared
to solve ALL of my problems. Sadly, appearances can be deceiving.
Thanks again for the ideas!
