Re: Frames -- Disable/Enable Menus
dorayme <doraymeRidThis @optusnet.com.a uwrote in news:doraymeRid This-
6933A0.12085625 042008@web.aioe .org:
[frames]
You don't get it, do you?
If a page can not be indexed correctly by the search engines then that page
is IMHO terribly broken. And google itself state quite up front that they
have trouble indexing framed pages.
If a page can not be referred to by name (instead of, say, "go to
example.com and press the [this is the page I mean] menu button) then that
page is terribly broken.
If an existing page is broken then it should be fixed. That way somebody
may be actaully able to find it some day.
If it is a new page (as I suspect) then it should not be using frames for
all the reasons discussed at length all over usenet[1]. I doubt this is a
legacy site, given the actual question and the source. However as the OP
appears to be a drive by google groper I guess we'll never know :-)
Lets de-cloud the issue by considering the OP's question.
OP has dug himself into a trench by using frames and suddenly wanting to do
what everybody else does and that is, I presume, disable or otherwise
change the menu item for the current page. Well, everybody else does this
server side with modern technology, and it is a blindingly simple task,
just an if statement around each echo that builds the menu, elapsed time to
write: 10 minutes (PHP assumed).
What the OP wants is very difficult to do with a standard framed page.
One could throw a truckload of client side javascript at it but to what
end? Simpler to write those if statements, which work for 100% of the
viewers.
It would be quite difficult to do server side. At the time the server is
asked to provide the menu "page" it has no idea at all which other "pages"
are being pulled to make up the framed page. One could perform all sorts of
skullduggery with sessions and what not to determine this, or perhaps build
a seperate frameset for each and every "page" on the site, pulling in a
different menu "page" for each (posibly via get variables), but to what
end. The energy expended in all of this would be far greater than that
required to simply serve up a suitable non-framed page using the odd if
statement. Probably greater than re-writing the site without frames.
Given the OP's requirements, as stated in his post, and all else aside,
frames are *not* the correct tool for this job.
[1] For any benifit you can possibly come up with *for* using frames it can
be quite easily demonstrated that said benifit can be easily achieved
*without* using frames. Including the dreaded use-up-canvas "fixed" menu.
--
Richard
Killing all google groups posts
The Usenet Improvement Project: http://improve-usenet.org
dorayme <doraymeRidThis @optusnet.com.a uwrote in news:doraymeRid This-
6933A0.12085625 042008@web.aioe .org:
[frames]
You don't get it do you? An existing framed site has a right to life.
You should all top denigrating them to the point of framicide.
You should all top denigrating them to the point of framicide.
If a page can not be indexed correctly by the search engines then that page
is IMHO terribly broken. And google itself state quite up front that they
have trouble indexing framed pages.
If a page can not be referred to by name (instead of, say, "go to
example.com and press the [this is the page I mean] menu button) then that
page is terribly broken.
If an existing page is broken then it should be fixed. That way somebody
may be actaully able to find it some day.
If it is a new page (as I suspect) then it should not be using frames for
all the reasons discussed at length all over usenet[1]. I doubt this is a
legacy site, given the actual question and the source. However as the OP
appears to be a drive by google groper I guess we'll never know :-)
Lets de-cloud the issue by considering the OP's question.
OP has dug himself into a trench by using frames and suddenly wanting to do
what everybody else does and that is, I presume, disable or otherwise
change the menu item for the current page. Well, everybody else does this
server side with modern technology, and it is a blindingly simple task,
just an if statement around each echo that builds the menu, elapsed time to
write: 10 minutes (PHP assumed).
What the OP wants is very difficult to do with a standard framed page.
One could throw a truckload of client side javascript at it but to what
end? Simpler to write those if statements, which work for 100% of the
viewers.
It would be quite difficult to do server side. At the time the server is
asked to provide the menu "page" it has no idea at all which other "pages"
are being pulled to make up the framed page. One could perform all sorts of
skullduggery with sessions and what not to determine this, or perhaps build
a seperate frameset for each and every "page" on the site, pulling in a
different menu "page" for each (posibly via get variables), but to what
end. The energy expended in all of this would be far greater than that
required to simply serve up a suitable non-framed page using the odd if
statement. Probably greater than re-writing the site without frames.
Given the OP's requirements, as stated in his post, and all else aside,
frames are *not* the correct tool for this job.
[1] For any benifit you can possibly come up with *for* using frames it can
be quite easily demonstrated that said benifit can be easily achieved
*without* using frames. Including the dreaded use-up-canvas "fixed" menu.
--
Richard
Killing all google groups posts
The Usenet Improvement Project: http://improve-usenet.org
Comment