Search for the last "/", split the last part off, you have home.html.  Now
look for the "." and split the first part off.  There you have it.

If you want it in practice, I'm pretty sure I can come up with it, but that
would mean skipping the good part for you, huh?... :-))

- Kayjey -



-----Oorspronkelijk bericht-----
Van: David.Artiss(at)boots.co.uk [mailto:David.Artiss(at)boots.co.uk]
Verzonden: woensdag 30 mei 2001 14:25
Aan: tim booker
CC: Klaas De Waele; Hwg-Techniques
Onderwerp: Re: Frames


Actually, Tims point has given me an idea (I'll share it if it works !!!)

Can anybody think of an easy way, in JS, to extract the page name from
window.location (i.e. from http://www.website.com/home.html, I'd want to
extract
"home") ?

David.





"tim booker" <timbooker(at)btinternet.com> on 30/05/2001 09:12:04

To:   "Klaas De Waele" <klaas(at)gracegraphics.be>
cc:   "Hwg-Techniques" <hwg-techniques(at)hwg.org> (bcc: David
      Artiss/IS/GB/BTC/TBC)
Subject:  Re: Frames



1.  The address bar displays the URL of the frameset page, not the content
page.  This means that you can't easily:

    - Link to the page directly.
    - Pass the URL on to someone.
    - Bookmark the page.

2.  Related to the first point is the fact that your pages will, more than
likely, be indexed individually by search engines.  This means that your
page will open up with none of the main navigation.

3.  On the plus side, you can make the navigation stay on the screen at all
times.  On the down side, however, you can make the navigation stay on the
screen at all times.  This can cause big problems with small screens,
because the navigation cannot be moved out of the way, giving the whole
window to the main content.

Just a few thoughts,

Tim



----- Original Message -----
From: "Klaas De Waele" <klaas(at)gracegraphics.be>
To: <hwg-techniques(at)hwg.org>
Sent: Wednesday, May 30, 2001 8:20 AM
Subject: Frames


> Hi there,
>
>
> I'm getting a bit down of all those people around here that hate frames.
If
> for once and for all you can express your thoughts WHY frames are bad (on
> itself, not just because some codewriter doesn't think about the features
> and demands and writes code that will eventually result in 'unexpected'
> frame behaviour) please do so now.  I've used frames in virtually every
site
> I ever made, never ran into problems.
>
> As far as I'm concerned:
>
> GOOD...
> - Easy (very) to have navigation
> - No problem having to scroll up to the navigation again after reading all
> the content
> - Nice to have multi-level navigation
> - Navigation changes?  Only one thing to change and upload.
>
> NOT SO GOOD...
> - You have to think before doing (oh no, that really puts me off ;) )
> - Some browsers don't support it*
> - Hard to make pixel-precise layouts that work across browsers
> - Reveal some specific problems with the respective browsers (Mozilla
e.g.)
>
> *I have my site put up with an intro page with frames and noframes
content.
> The noframes content even has some navigation and subpages without frames
as
> an introduction.  Guess what... last month in total had 3399 visits on
that
> first page... 0,29% had non-frames capable browsers.  Visitors came back
> generally 3 times a month.  If these non-frames capable boys only came
over
> once, it means of 1130 visits I miss 10 of them, 1,13%.  I won't be
changing
> a thing for them unhappy few, to be honest.
>
>
> - Kayjey -
> http://www.fiatcoupe.net
>





 

• Web Designer Courses
• Off the Shelf Training Courses

HWG hwg-techniques mailing list archives, maintained by Webmasters @ IWA