Sep 23 2020
Aug 6 2020
As a Cargo user, I agree that it would be a good idea.
Apr 22 2020
Mar 29 2020
Aug 22 2019
Or maybe whenever the MediaWiki categories table gets updated in the job queue, we could use a hook to add to Cargo's _pageData table at the same time.
Aug 21 2019
May 23 2019
I don't want to derail this Phabricator page, but I've asked what I think may be a related question on the Cargo talk page: https://www.mediawiki.org/wiki/Extension_talk:Cargo#Text-file_output_display_format
May 16 2019
@Tombolano Thanks for this and for your other recent contribution (about HOLDS). I had worked round this one using CSS as I wrongly thought it was a Foreground skin problem. I'm "watching" this project now in the hope that you continue your interest :-)
Feb 18 2018
"The drill-down interface provided by Amazon.com offers some interesting options: there, the filters and all their values appear in a sidebar, instead of at the top of the page - perhaps that should be the case for Special:Drilldown too?"
Sep 23 2017
I have just removed mapOptions['fullscreenControl'] = true; from my code and the fullscreen control remains.
Jul 27 2017
in other words, if page A gets added to category B, it's only for purposes of tagging and querying; no one is expected to go to the page Category:B to check out what pages are there, and traverse through the tree. (Let me know if I'm wrong about that.)
Jul 26 2017
... obviating the need to patch the extension at all ...
I would like the same thing, if possible - to present existing categories as options but allow creation of new categories.
Jul 12 2017
I've not perfected it, but here it is, in Template:Add drilldown links.
Yes, and annoyingly in answering your question I worked out how to use it within a Cargo query too, obviating the need to patch the extension at all... however, I do think it's a good feature, and having a parameter to control it would be easier.
Jul 10 2017
Jul 9 2017
I use Chrome on Windows and don't mind it! Though I concede it doesn't look as classy as on most of the other browsers...
Jul 7 2017
Brilliant, thanks. One final change to fix the add drilldown link= thing:
Jul 6 2017
Pleased you like it!
The ⟱ didn't show up on the iPhone (email or Phabricator website) so there must be something funny about it.
Yesterday I said...
Jul 5 2017
I like the Unicode character :-) I think it maybe looks better on Chrome so it must be a matter of taste.
Jul 3 2017
From Wikipedia: "The magnifying glass (i.e. Magnifying glass icon.svg, or U+1F50D in Unicode: 🔍) is commonly used as a symbolic representation for the ability to search or zoom, especially in computer software and websites.".
In the code below, if you add |add drilldown links (with no equals sign and no parameters) it displays the magnifying glass for all possible fields.
I've changed "feeds-to-map" to "data-feeds-to-map".
Jul 2 2017
Sorry for the delay. I'll try to finalise this over the next few days.
Pleased you like it :-)
Jun 26 2017
Here's what I have so far. It's the magnifying glass that is the link. Not tested yet with Integer or Page. Feel free to let me know what you think!
Jun 25 2017
Earlier you said...
Jun 15 2017
Sorry, I forgot to add that the CSS did load from Cargo.css for format=table but not for format=dynamic table. I needed it to work for dynamic tables, which is why I ended up adding Cargo.css to the styles of ext.cargo.datatables. I hope it makes sense now!
Jun 14 2017
That didn't work for the CSS, for me anyway. The CSS isn't needed in Special:Drilldown, but in a normal page's Cargo query.
I'm pleased you like it :-)
Jun 9 2017
Ok, here we go:
Why can't this be done if "feeds to map" gets the standard "TemplateName[FieldName]" format, though?
Cheers. In relation to your two points:
Sorry, I should add that currently I just have the CSS in Common.css:
I don't understand - how is that different from the current patch?
Jun 8 2017
Here is a way of automatically detecting map feeding with jQuery. The relevant lines in the big diff below are:
P.S. I wonder whether it would be possible to add a hook to Cargo to allow someone to create their own mini extension to modify the output of Special:Drilldown without having to amend the code of the extension. This could be a short-term solution for me.
Jun 6 2017
I *am* sure that none of my users will have a need for "set marker" :-)
A table may make sense if there are a lot of display fields... maybe if there are more than, say, three display fields, it should just show up as a table instead of a category?
May 31 2017
It seems to me that the only really customizable thing is which extra fields to display, though.
I'm pleased you like it so far :-)
For a table which has coordinates I'd like to include a query like this:
May 30 2017
Apologies. I have belatedly noticed that the namespace, when needed, is already included in $valuesTable's 'title'. See amended patch below.
May 28 2017
As an afterthought, I made a small change so that if "hidesetmarker" is set (i.e. the user is not expected to type in coordinate values) then the Coordinates input box is set to "readonly". See the first four green lines below.
I wonder whether it would be possible to avoid the need for the "hideaddressinput" parameter.
Sorry for the delay. I've changed it now so as not to use id and class parameters.
Feb 13 2017
Here is a further attempt, based on your suggestion on the extension discussion page:
Feb 11 2017
Feb 10 2017
Dec 17 2016
Thanks. I'd be happy to have a go at this, though if I try to spend time on it before Christmas I might not survive to tell the tale.