robchur wrote:

[[User:Lupin]] on En has some interesting and useful popups which do
this..."navigation scripts" I believe he calls them. Might be worth a look.

robchur wrote:

*** Bug 4408 has been marked as a duplicate of this bug. ***

robchur wrote:

*** Bug 11205 has been marked as a duplicate of this bug. ***

This has existed for quite some time as a Gadget called "Popups" which Rob mentioned in comment #1 5 years ago. It's been ported to a lot of Wikimedia wikis by now as well. Resolving FIXED.

• Bug 18486 has been marked as a duplicate of this bug. ***

• Bug 7278 has been marked as a duplicate of this bug. ***

• Bug 26512 has been marked as a duplicate of this bug. ***

happy.melon.wiki wrote:

*** Bug 26587 has been marked as a duplicate of this bug. ***

happy.melon.wiki wrote:

As suggested in bug26587, it might be worthwhile to consider bundling Popups, or at least a subset of it, as core JS or a maintained extension.

• Bug 28445 has been marked as a duplicate of this bug. ***

(In reply to comment #9)

As suggested in bug26587, it might be worthwhile to consider bundling Popups,
or at least a subset of it, as core JS or a maintained extension.

I'd opt for an extension for better integration and optimalization.

For example, the generated resources can include certain pieces of information by default in the output of elements which would otherwise take extra http requests to the api. And ofcourse internationalization and usage of mw.msg (translatewiki!)

Note that the current version of popups was developed a long time ago, by making it into an extension the popup-modules can become seperate files again (like they once were) and combined by ResourceLoader.

Since many people use popups (not just en.wiki), porting to resourceloader and making it more integrated would possible save a noticeable amount of requests and bandwidth as well.

Also, it should probably be rewritten in a more object oriented approach (partially already is though).

I'd like to take this on as a project and hope some people will join.

Basically we need the following (imho):

• Rewrite from scratch in a modular way in multiple files through ResourceLoader

• Use existing modules like jQuery, jUI and mediaWiki. library where appropiate (ie. for selecting elements, dom manipulation, query parameters, ajax requests with JSON callbacks ($.getJSON), getting user preferences (mw.user.options)

• Redesign (or design at all) a nice interface for the popups and the dropdown menus (right now it's mostly adhoc elements with proof-of-concept styling). This will likely make the interface more breathing and less 'tech-savvy'. We should also re-use core/skin styles/classes where possible (for example for errors and difference-views)

• Localization: No need to define all languages in the script and load for everbody. We can do this using the MediaWiki extension i18n system and use the known route via translatewiki.net for translations which will likely improve translations and cause a wider usage as well. In addition this will also make it much easier to track which messages are yet to be translated and which messages need to be reviewed etc. (all part of translatewiki system)

• Independant from language, project or server. Should work in any language on any 'normal' MediaWiki install (English Wikipedia, Hebrew Wiktionary, but also wikis outside Wikimedia environment)

It would be great if some of the original developers of the gadget could join as well. Would probably be a fun project for them, and they probably know the codebase a lot better than me.

kshitizsethia wrote:

Hi, I have no prior experience in developing for wikimedia but would sure like to get involved in this popup gadget if it is being redesigned.

I am a B.Tech. Information Technology student from VIT University, India. I am currently doing my internship at eBay, India Development Center.

Please pardon me if this is the wrong place to post such a request.

Don't wait for me to do this. Please anyone, take this :)

I'm not certain we need an extension. It seems like almost all these points could be addressed by bug 29272 (Gadgets 2.0).

• Bug 61585 has been marked as a duplicate of this bug. ***

It's worth noting that Prateek Saxena and WMF people in general are now working on a reimplementation of Popups (bug 61167 tracks making that particular solution to this bug happen). There's some information and mockups (but not a lot :( ) available at https://www.mediawiki.org/wiki/Extension:Popups and https://www.mediawiki.org/wiki/Beta_Features/Hovercards#Current_beta_experiment_Designs

Can someone involved will sum up the current status, pretty please? :)

I am currently working on the Popups extension with Yuvi's help. I am implementing the designs made by Vibha which can found here - https://www.mediawiki.org/wiki/Beta_Features/Hovercards. The functionality is mostly done and I am working on solving some design related bugs (https://trello.com/c/s9Msjamo/78-article-preview-hover-cards). I have raised issues for its review as well -

• https://bugzilla.wikimedia.org/show_bug.cgi?id=61167
• https://bugzilla.wikimedia.org/show_bug.cgi?id=61742
• https://bugzilla.wikimedia.org/show_bug.cgi?id=61743

The design team is hoping to get it deployed as a Beta Feature by 6th March 2014. The repository for the same can be found here - https://git.wikimedia.org/summary/mediawiki%2Fextensions%2FPopups

Marking FIXED by https://www.mediawiki.org/wiki/Extension:Popups