But we have a cool zoom feature
-
On the Jehovah's witnesses Watching The World page you can learn about what is going on in the world. The page provides you with summaries a la Slashdot and you can even listen to them if you find reading an entire page too tedious - but there are no "Read more" links; there is nothing beyond the summaries. The good news is that if you happen to like one of the stock photos you can click on it and use the sophisticated zoom feature.
Interesting technical fact: while the content is pretty light, that simple page is made of 7500 lines of HTML (270KB).
-
@Ronald said:
The good news is that if you happen to like one of the stock photos you can click on it and use the sophisticated zoom feature.
I love the way the image is positioned by source-image pixel coords, rather than output pixel coords. When you're zoomed in, you can see it jumping in steps the size of the large zoomed pixels.
-
It's a legacy from the printed version: short 1-paragraph stories about random things.
-
@Ronald said:
Interesting technical fact: while the content is pretty light, that simple page is made of 7500 lines of HTML (270KB).
3000+ lines of that is code relating to all the various languages that are available:<option data-priority="1" data-alternative-spellings="Acholi" class="lang-ach" lang="ach" dir="ltr" xml:lang="ach" value="/ach/bukke/">Acholi</option> <option data-priority="2" data-alternative-spellings="Afrikaans" class="lang-af" lang="af" dir="ltr" xml:lang="af" value="/af/publikasies/tydskrifte/g201312/ons-beskou-die-w%C3%AAreld/">Afrikaans</option>
[snip . . . )
<option data-priority="306" data-alternative-spellings="Korean 한국어" class="lang-ko" lang="ko" dir="ltr" xml:lang="ko" value="/ko/publications/magazines/g201312/watching-the-world/">한국어</option>
-
@El_Heffe said:
@Ronald said:
Interesting technical fact: while the content is pretty light, that simple page is made of 7500 lines of HTML (270KB).
3000+ lines of that is code relating to all the various languages that are available:<option
data-priority="1"
data-alternative-spellings="Acholi"
class="lang-ach"
lang="ach"
dir="ltr"
xml:lang="ach"
value="/ach/bukke/">Acholi</option>
<option
data-priority="2"
data-alternative-spellings="Afrikaans"
class="lang-af"
lang="af"
dir="ltr"
xml:lang="af"
value="/af/publikasies/tydskrifte/g201312/ons-beskou-die-w%C3%AAreld/">Afrikaans</option>[snip . . . )
<option
data-priority="306"
data-alternative-spellings="Korean 한국어"
class="lang-ko"
lang="ko"
dir="ltr"
xml:lang="ko"
value="/ko/publications/magazines/g201312/watching-the-world/">한국어</option>It's an innovative approach. Why burden the server with language selection when it's possible to offload this tedious task to the client?
Of course the fact that the multilingual code merely contains the parameters required to request the actual content from the server in each language indicates that there is room for even more innovation.