Thank you so much for all your replies. I will look at the information provided and surly come back for more. Thank you. This is really much appreciated.
I don't think it is in the book unfortunately.
Your reply is most possibly the most concise way of explaining how this is done, however my level of experience will need to increase to understand what you explained. I am doing research on this now.
What I wonder though is that with a normal anchor/link inside the same document, for example, "Go to top" (from the bottom of the page) the distance does not need to be calculated, so why does it need to be calculated now?
Does this not hinder cross-browser and cross-resolution compatibility with a fluid layout? I can understand mathematically how calculating the distance to a destination from point a to b and then taking a percentage of that distance until the position is reach kind of makes the scrolling slower and slower towards approaching its destination. For example always taking a third of the distance between a and b until destination is reached. However calculating the initial distance is what I have not wrapped my mind round just yet. What happens when the screen resolution is higher? Will the distance be defined in px or em? I take it with your method jQuery is not being used but purely JS, am I correct?
No worries about the time frame of replies. I am indeed very happy to have gotten this many replies so fast. Thank you all again for helping me out here. This is really truly appreciated. I will now look at the site and link provided to see if I can manage to understand how this is done.