The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
Okay, I've got five pages:
home.html
transition.html
index1.html
index2.html
message.html
What I want is this:
When a user clicks on a link on the home.html page, they are taken to transition.html
Then, using a JavaScript, probably somewhere in there, there will be an IF/ELSE statement, the transition page will take you to a certain page depending on the page you were at last.
How do I do it?
home.html
transition.html
index1.html
index2.html
message.html
What I want is this:
When a user clicks on a link on the home.html page, they are taken to transition.html
Then, using a JavaScript, probably somewhere in there, there will be an IF/ELSE statement, the transition page will take you to a certain page depending on the page you were at last.
How do I do it?
Page:
Nimco wrote:
> I was under the impression that Twain wasn't constructing an intranet
> site...
I'm not.
> I was under the impression that Twain wasn't constructing an intranet
> site...
I'm not.
>Garin wrote:
Better still, go work for their tech support and see all the idiots complaining that the intranet applications don't work after they messed around with their browser settings. :)
You can get rid of those functions, they did at my college so we couldn't bypass the Proxy settings on their server.
Also you wouldn't be employed if there wern't idiots working around the company. :)
Better still, go work for their tech support and see all the idiots complaining that the intranet applications don't work after they messed around with their browser settings. :)
You can get rid of those functions, they did at my college so we couldn't bypass the Proxy settings on their server.
Also you wouldn't be employed if there wern't idiots working around the company. :)
Nimco wrote:
> I was under the impression that Twain wasn't constructing an intranet
> site...
Oh, going around in circles now...
We already both agreed that the technique was probably inappropriate for what Twain was doing. The issue was whether its ever valid to use that, I gave some examples of where it could and has been used, which is why intranets came up.
Oh well, guess the topic has been exhausted by now. :)
> I was under the impression that Twain wasn't constructing an intranet
> site...
Oh, going around in circles now...
We already both agreed that the technique was probably inappropriate for what Twain was doing. The issue was whether its ever valid to use that, I gave some examples of where it could and has been used, which is why intranets came up.
Oh well, guess the topic has been exhausted by now. :)
Garin wrote:
> Nimco wrote:
> But on an intranet you wouldn't have to worry about large pages at
> 100Mb+ network speeds! It isn't designing if you can specify every
> criteria about a machine - even on an intranet larger than 200
> machines you cannot control them that perfectly. People mess around
> with their machines, change settings etc. Some employees may turn
> off JavaScript - then what happens?
Firstly, any company worth it's weight in gold wouldn't build a "business critical system" using javascript for anything other than rollovers. Secondly, when designing "business critical systems" you can specify, to an extent, the criteria and operational parameters. (Trust me on this, as well as websites, I design intranets and production systems too!). Any IT/MIS department in any major company will have control on what the user can do with their machine, even down to being able to change the colour or resolution of your desktop.
>Garin wrote:
> Can I just say, welcome to real world. Go and do work for a big
> corporation and this is the stuff you face. Better still, go work for
> their tech support and see all the idiots complaining that the
> intranet applications don't work after they messed around with their
> browser settings. :)
Nice on Garin... sounds somewhat familiar... "Hello there Mr MIS Support... it was working fine yesterday until I went tools>internet options>some random radio button...
>Garin wrote:
> As for your comment about intranet speeds. Just because you have a
> high capacity network doesn't mean you should be using it. The idea
> that everything should be server side is long gone I'm afraid, .NET
> and java are proof of that I think.
Even if you have 100MB+, that's not a guranteed constant. intranets are still affected by bandwidth along with any other network. "business critical sytems" will always take the majority of this, then company email, the rest for general traffic and internet access. Chuck in a VPN and a couple of FTP's and your 100+MB is reduces to 50+ksec. Your right in what you say about Server Side becoming a thing of the past, .NET is becoming the future of MS and as for Java...
>Nimco wrote:
> No, only a fool would try to argue that something is a realistic
> possibility if it requires the kind of computer specification you
> get only in a controlled environment!
A corporate environment is a controlled environment, could you imagine what would happen if it wasn't? So with in an environment which is controlled from appz to hardware, you can be specific in the creation of internal systems.
> Nimco wrote:
> But on an intranet you wouldn't have to worry about large pages at
> 100Mb+ network speeds! It isn't designing if you can specify every
> criteria about a machine - even on an intranet larger than 200
> machines you cannot control them that perfectly. People mess around
> with their machines, change settings etc. Some employees may turn
> off JavaScript - then what happens?
Firstly, any company worth it's weight in gold wouldn't build a "business critical system" using javascript for anything other than rollovers. Secondly, when designing "business critical systems" you can specify, to an extent, the criteria and operational parameters. (Trust me on this, as well as websites, I design intranets and production systems too!). Any IT/MIS department in any major company will have control on what the user can do with their machine, even down to being able to change the colour or resolution of your desktop.
>Garin wrote:
> Can I just say, welcome to real world. Go and do work for a big
> corporation and this is the stuff you face. Better still, go work for
> their tech support and see all the idiots complaining that the
> intranet applications don't work after they messed around with their
> browser settings. :)
Nice on Garin... sounds somewhat familiar... "Hello there Mr MIS Support... it was working fine yesterday until I went tools>internet options>some random radio button...
>Garin wrote:
> As for your comment about intranet speeds. Just because you have a
> high capacity network doesn't mean you should be using it. The idea
> that everything should be server side is long gone I'm afraid, .NET
> and java are proof of that I think.
Even if you have 100MB+, that's not a guranteed constant. intranets are still affected by bandwidth along with any other network. "business critical sytems" will always take the majority of this, then company email, the rest for general traffic and internet access. Chuck in a VPN and a couple of FTP's and your 100+MB is reduces to 50+ksec. Your right in what you say about Server Side becoming a thing of the past, .NET is becoming the future of MS and as for Java...
>Nimco wrote:
> No, only a fool would try to argue that something is a realistic
> possibility if it requires the kind of computer specification you
> get only in a controlled environment!
A corporate environment is a controlled environment, could you imagine what would happen if it wasn't? So with in an environment which is controlled from appz to hardware, you can be specific in the creation of internal systems.
Nimco wrote:
> Tell me this then: when you get to the transition page, it will start
> auto-loading the new page (perhaps after a certain number of seconds),
> yes? If you are relying on the fact that the transition page will be
> displayed until the new page starts loading, then fine. But, if the
> server is going to timeout, the transition page won't help!
>
The transition page will help. The page will only sit there for so long waiting, if it doesn't receive anything back then it just redirects to a created timeout page specifying the operation timed out, but still leaving them within the structure of the application. Of course you can rightly say, well maybe it'll timeout when forwarding to that page too so it won't help you, but at least in the scenario I'm referring to. The timeouts were a problem of the DB server not the webserver itself. But even so, you could make the client side script generate the error page itself without any help from the server if you wanted. But thats straying quite a long way from the original point.
> But on an intranet you wouldn't have to worry about large pages at
> 100Mb+ network speeds! It isn't designing if you can specify every
> criteria about a machine - even on an intranet larger than 200
> machines you cannot control them that perfectly. People mess around
> with their machines, change settings etc. Some employees may turn off
> JavaScript - then what happens?
>
Can I just say, welcome to real world. Go and do work for a big corporation and this is the stuff you face. Better still, go work for their tech support and see all the idiots complaining that the intranet applications don't work after they messed around with their browser settings. :)
I mean its not so bad now, because browsers have converged alot in terms of compatibility. But still its standard procedure when you develop applications for an intranet to specify exactly what the platform client side is going to be (ie what browser and software installed) and what its settings are going to be.
As for your comment about intranet speeds. Just because you have a high capacity network doesn't mean you should be using it. The idea that everything should be server side is long gone I'm afraid, .NET and java are proof of that I think.
> No, only a fool would try to argue that something is a realistic
> possibility if it requires the kind of computer specification you get
> only in a controlled environment!
I should mention that I haven't been talking hypothetically, I'm giving you real world examples that do exist. So erm...I can only conclude, I'm fool, and everybody I've ever worked with is a fool. As you wish... :)
You can take what I've written as you like. I have some experience of doing this kind of stuff. Doesn't mean I'm better than you or that I know more. Enough people around here worrying about that without me starting. :)
> Tell me this then: when you get to the transition page, it will start
> auto-loading the new page (perhaps after a certain number of seconds),
> yes? If you are relying on the fact that the transition page will be
> displayed until the new page starts loading, then fine. But, if the
> server is going to timeout, the transition page won't help!
>
The transition page will help. The page will only sit there for so long waiting, if it doesn't receive anything back then it just redirects to a created timeout page specifying the operation timed out, but still leaving them within the structure of the application. Of course you can rightly say, well maybe it'll timeout when forwarding to that page too so it won't help you, but at least in the scenario I'm referring to. The timeouts were a problem of the DB server not the webserver itself. But even so, you could make the client side script generate the error page itself without any help from the server if you wanted. But thats straying quite a long way from the original point.
> But on an intranet you wouldn't have to worry about large pages at
> 100Mb+ network speeds! It isn't designing if you can specify every
> criteria about a machine - even on an intranet larger than 200
> machines you cannot control them that perfectly. People mess around
> with their machines, change settings etc. Some employees may turn off
> JavaScript - then what happens?
>
Can I just say, welcome to real world. Go and do work for a big corporation and this is the stuff you face. Better still, go work for their tech support and see all the idiots complaining that the intranet applications don't work after they messed around with their browser settings. :)
I mean its not so bad now, because browsers have converged alot in terms of compatibility. But still its standard procedure when you develop applications for an intranet to specify exactly what the platform client side is going to be (ie what browser and software installed) and what its settings are going to be.
As for your comment about intranet speeds. Just because you have a high capacity network doesn't mean you should be using it. The idea that everything should be server side is long gone I'm afraid, .NET and java are proof of that I think.
> No, only a fool would try to argue that something is a realistic
> possibility if it requires the kind of computer specification you get
> only in a controlled environment!
I should mention that I haven't been talking hypothetically, I'm giving you real world examples that do exist. So erm...I can only conclude, I'm fool, and everybody I've ever worked with is a fool. As you wish... :)
You can take what I've written as you like. I have some experience of doing this kind of stuff. Doesn't mean I'm better than you or that I know more. Enough people around here worrying about that without me starting. :)
Garin wrote:
> Twain,
> quite rusty with javascript but if I understand correctly what it is
> you're trying to do you want a function something like...
>
> function redirect() {
>
> if (document.referrer== 'http://www.twaincommunity.tk/home.html')
> {
> top.location= 'http://www.twaincommunity.tk/index1.html';
> } else
> if (document.referrer== 'http://www.twaincommunity.tk/index1.html')
> {
> top.location= 'http://www.twaincommunity.tk/index2.html';
> }
>
> }
>
> And you want to add onLoad="redirect()" to the body tag of
> the transition page
Thank you very much for this, Garin. At least someone answered!
I just tried it, and sadly, there was no effect. It'll go to the transition page okay, but then, nothing happens after that. And I know that "document.referer" will only change the page after the transition page depending on the page that was being viewed before it. this is partly what I wanted, but it still only takes you to one page, regardless of the link that was clicked on before the transition page appeared.
See what I mean?
> Twain,
> quite rusty with javascript but if I understand correctly what it is
> you're trying to do you want a function something like...
>
> function redirect() {
>
> if (document.referrer== 'http://www.twaincommunity.tk/home.html')
> {
> top.location= 'http://www.twaincommunity.tk/index1.html';
> } else
> if (document.referrer== 'http://www.twaincommunity.tk/index1.html')
> {
> top.location= 'http://www.twaincommunity.tk/index2.html';
> }
>
> }
>
> And you want to add onLoad="redirect()" to the body tag of
> the transition page
Thank you very much for this, Garin. At least someone answered!
I just tried it, and sadly, there was no effect. It'll go to the transition page okay, but then, nothing happens after that. And I know that "document.referer" will only change the page after the transition page depending on the page that was being viewed before it. this is partly what I wanted, but it still only takes you to one page, regardless of the link that was clicked on before the transition page appeared.
See what I mean?
Nimco wrote:
> But what is the point of:
>
> Main Page > Transition Page > New Page
>
> which requires them to have JavaScript installed, when you could just
> do:
>
> Main Page New Page
>
> with a simple hyperlink. What do you gain from the first method?
I just wanted to see how it'd work, and if it was worth keeping it with my finished website. I suppose I'd better leave it out . . .
> But what is the point of:
>
> Main Page > Transition Page > New Page
>
> which requires them to have JavaScript installed, when you could just
> do:
>
> Main Page New Page
>
> with a simple hyperlink. What do you gain from the first method?
I just wanted to see how it'd work, and if it was worth keeping it with my finished website. I suppose I'd better leave it out . . .
Garin wrote:
> So by your definition most (since javascript is the most popular
> language for writing them) DHTML sites are very badly designed, ok.
> :P
There's a difference between using DHTML for navigation and relying on it for navigation. Most sites have a backup navigation if they do use JavaScript heavily, but a transition page for an auto-redirect? No.
> Why not indeed? Never said you shouldn't do that or that it wasn't a
> solution. Is that or point number 1 a better solution? Depends on
> what you want. Using javascript can certainly give you more control,
> and can be useful in scenarios where you can get servers that will
> timeout, and you don't want to leave the user left with a standard
> this page couldn't be displayed message.
Tell me this then: when you get to the transition page, it will start auto-loading the new page (perhaps after a certain number of seconds), yes? If you are relying on the fact that the transition page will be displayed until the new page starts loading, then fine. But, if the server is going to timeout, the transition page won't help!
Or perhaps you are going to use JavaScript to preload some of the things on the next page into the cache to speed up the loading of the next page? That could get a very messy script! Trying to use if/else statements to determine which page they came from, then preload images based on which page they're going to, then check to see when it has all preloaded before you redirect them? The script will be huge!
> Anyway, you assume far too much. You aren't thinking beyond a pretty
> web site that sits on the web that everybody can access and caters to
> lowest common demoninator. If I develop for an intranet for example,
> I may have control over all machines, I may have control of their
> browser settings, I might be able to even decide what browser and what
> version they use if necessary. If I decide to use javascript, then
> there certainly won't be any browser that has javascript turned off
> scenarios.
But on an intranet you wouldn't have to worry about large pages at 100Mb+ network speeds! It isn't designing if you can specify every criteria about a machine - even on an intranet larger than 200 machines you cannot control them that perfectly. People mess around with their machines, change settings etc. Some employees may turn off JavaScript - then what happens?
> There is no right or wrong answer to this, no better solutions, just
> some are more appropriate to different situations. And only a fool
> thinks otherwise in my opinion.
No, only a fool would try to argue that something is a realistic possibility if it requires the kind of computer specification you get only in a controlled environment!
> So by your definition most (since javascript is the most popular
> language for writing them) DHTML sites are very badly designed, ok.
> :P
There's a difference between using DHTML for navigation and relying on it for navigation. Most sites have a backup navigation if they do use JavaScript heavily, but a transition page for an auto-redirect? No.
> Why not indeed? Never said you shouldn't do that or that it wasn't a
> solution. Is that or point number 1 a better solution? Depends on
> what you want. Using javascript can certainly give you more control,
> and can be useful in scenarios where you can get servers that will
> timeout, and you don't want to leave the user left with a standard
> this page couldn't be displayed message.
Tell me this then: when you get to the transition page, it will start auto-loading the new page (perhaps after a certain number of seconds), yes? If you are relying on the fact that the transition page will be displayed until the new page starts loading, then fine. But, if the server is going to timeout, the transition page won't help!
Or perhaps you are going to use JavaScript to preload some of the things on the next page into the cache to speed up the loading of the next page? That could get a very messy script! Trying to use if/else statements to determine which page they came from, then preload images based on which page they're going to, then check to see when it has all preloaded before you redirect them? The script will be huge!
> Anyway, you assume far too much. You aren't thinking beyond a pretty
> web site that sits on the web that everybody can access and caters to
> lowest common demoninator. If I develop for an intranet for example,
> I may have control over all machines, I may have control of their
> browser settings, I might be able to even decide what browser and what
> version they use if necessary. If I decide to use javascript, then
> there certainly won't be any browser that has javascript turned off
> scenarios.
But on an intranet you wouldn't have to worry about large pages at 100Mb+ network speeds! It isn't designing if you can specify every criteria about a machine - even on an intranet larger than 200 machines you cannot control them that perfectly. People mess around with their machines, change settings etc. Some employees may turn off JavaScript - then what happens?
> There is no right or wrong answer to this, no better solutions, just
> some are more appropriate to different situations. And only a fool
> thinks otherwise in my opinion.
No, only a fool would try to argue that something is a realistic possibility if it requires the kind of computer specification you get only in a controlled environment!
Page: