Why it took a long time to build the tiny link preview on Wikipedia
11–20 of 255 posts
Re: Why it took a long time to build the tiny link preview on Wikipedia
#12One downside is that when I move the cursor along while reading an article all sorts of links now pop up at me. What I mean is using the mouse or trackpad to keep my place in the article; sometimes I drag the cursor to highlight the text, especially when skimming. Surely I'm not the only one who does this?
Re: Why it took a long time to build the tiny link preview on Wikipedia
#13One downside is that when I move the cursor along while reading an article all sorts of links now pop up at me. What I mean is using the mouse or trackpad to keep my place in the article; sometimes I drag the cursor to highlight the text, especially when skimming. Surely I'm not the only one who does this?
Re: Why it took a long time to build the tiny link preview on Wikipedia
#14In case you want to turn it on (or off), it's under Preferences->Appearance->Page previews. I think I'll probably leave it off personally. I like the previews that have already existed for a while in the mobile app, but on desktop not so sure.
Re: Why it took a long time to build the tiny link preview on Wikipedia
#15I am continually impressed by the markup Wikipedia generates. They've managed to pull in pretty link previews, scientific notation and a grid layout, whilst building a highly nested markup structure? The remarkable part? Wikipedia works great inside a text browser like elinks. It works great in a modern browser. Without sacrificing the interactivity people have grown to expect.
Re: Why it took a long time to build the tiny link preview on Wikipedia
#16I've implemented such an ajax page preview and also a page inliner (for expanding page trees via ajax) about 10 years ago. It was major work, because you essentially send a stripped down page in xml, so it needed some architectural changes to separate the various page templates properly. In the end it needed 2 months work. phpwiki has a proper template design and its plugins cannot ever destroy a page layout or harm security.
mediawiki on the other side is horribly undesigned spaghetti code, with no proper templating and plugin integration, so it needed a few years more. It's like parsing html with regexp.
Re: Why it took a long time to build the tiny link preview on Wikipedia
#17I couldn't care less for the huge image in the popup layer, scrollability and extra content would be much nicer.
Re: Why it took a long time to build the tiny link preview on Wikipedia
#18What a great way of destroying the user experience with a beautifully over-engineered feature that is utterly crap while actually trying to use the underlying page.
Thanks an awful lot for breaking the ability to use the site as I am used to and making it impossible to scan with the curser as anchor for my eyes.
Re: Why it took a long time to build the tiny link preview on Wikipedia
#19I am continually impressed by the markup Wikipedia generates. They've managed to pull in pretty link previews, scientific notation and a grid layout, whilst building a highly nested markup structure? The remarkable part? Wikipedia works great inside a text browser like elinks. It works great in a modern browser. Without sacrificing the interactivity people have grown to expect.
Re: Why it took a long time to build the tiny link preview on Wikipedia
#20Wow. Had just read that and then saw the feature first time while browsing over a list page. Was moving my curser down the list and when ever I wanted to click a link, the above link hat popped up the layer, highjacking my click and leading me to the wrong page. What a great way of destroying the user experience with a beautifully over-engineered feature that is utterly crap while actually trying to use the underlyin…