Talk:Delacorte Theater

Spelling of venue

This entry has the proper spelling: Delacorte Theater. Information from other entry should come here. J. Van Meter 18:03, 7 September 2005 (UTC)

agreed and done Quill 22:16, 7 September 2005 (UTC)

Against proposed merge

• I strongly oppose the proposed merge. The theater is a separate and distinct entity from the Festival. It would be like saying the Knicks article should be merged w/ the Madison Sqaure Garden article. (That being said, there is way to much Shakespeare Festival info in the Delacorte article. It should be moved out.)J. Van Meter 21:52, 5 March 2007 (UTC)

Maybe you're the right one to divide up the information properly, with cross-references. --03:31, 6 March 2007 (UTC)

A Commons file used on this page or its Wikidata item has been nominated for deletion

The following Wikimedia Commons file used on this page or its Wikidata item has been nominated for deletion:

• Duke Ellington Circle jeh.JPG

Participate in the deletion discussion at the nomination page. —Community Tech bot (talk) 22:51, 22 January 2021 (UTC)

Broken map widget

During a recent de-cluttering of the article, I chucked a map widget that I found unhelpful. In my edit summary, I (carelessly) limited my reasoning to the map’s redundancy with the infobox map, and that led to some pushback from Epicgenius. I’m re-removing the map widget because my concerns are actually more extensive. I’m not sure how this widget looks to everyone, but for me, it depends how I am accessing Wikipedia:

• If I access the article from a desktop browser (either Edge or Vivaldi), I get a flurry of location pins for various Central Park features. Most have no connection to the article topic beyond ‘things that are also in Central Park’. Worse, the pin for Belvedere Castle loads in front of the pin for the Delacorte Theater, largely obscuring it.
• If I access the article from a mobile phone (Android using either Chrome or Vivaldi, or iPhone using Safari), the map loads without any location pins.

Either way, the map promises to be a source of confusion to most users. This seems like a half-developed widget that shouldn’t be in use presently. Even if it gets the bugs worked out, I would hope that it would be integrated directly into the infobox because at its core, it is a second map that shows the exact same geography as the first. —jameslucas ^{▄▄▄ ▄ ▄▄▄ ▄▄▄ ▄} 15:34, 23 May 2022 (UTC)

Thanks for explaining your edit. I still disagree with it, but I will explain why I had added the map back:

• I did indeed intend for multiple features to be displayed in the browser version of the map. This map is intended to display related structures in Central Park. I do not think they are unrelated at all, as they provide context to the theater's location in the park. By contrast, the infobox map does not do that. Of course, the default zoom level of the map can be increased so it will only show a few points by default.
• The pins are displayed like that because the template lists the points in north to south order (so points to the north are listed first). Belvedere Castle appears in front of the Delacorte because the castle is south of the theater. This is also intentional, because if the landmarks to the south were placed first, the landmarks to the north would overlap. See the map below for what I'm talking about. Again, if the default zoom level is increased, this is no longer an issue.
• I'm not experiencing the same issues you had on mobile. I tested it using Safari and Chrome on an iPhone 7 running iOS 15.2, and the pins load as intended for me.

• Finally, I think this map can actually be integrated into the infobox, provided we suppress the default interactive map.

– Epicgenius (talk) 16:06, 23 May 2022 (UTC)

I get the reasoning for the north-to-south load thing (and I can’t see anything else making sense), but even if that works for 19 out of every 20 location pins in the park, it’s a problem here unless it looks right for this one pin; to that end, I think your zoom-level adjustment is a good first step. But the pins are still failing to load and/or display in every mobile browser I’ve tested, including on a month-old iPhone 11 borrowed from someone who isn’t an editor and is running the phone pretty much as it came out of the box. —jameslucas ^{▄▄▄ ▄ ▄▄▄ ▄▄▄ ▄} 16:54, 23 May 2022 (UTC)

I can modify the template so this specific pinpoint is on top for this page only. But even then, there is still the issue of the Delacorte being on top of Belvedere Castle. Also, the map issue is strange - it works properly on some devices but I've heard it fails to work at all on others. – Epicgenius (talk) 17:00, 23 May 2022 (UTC)

Troubleshooting mobile-browser compatibility is far out of my skill set, so I’ll leave that quagmire to you and/or suitably knowledgeable editors. Two proposals:

1. Could use the default map in the infobox but make it link to your fancy map?
2. If you get your custom map widget to work and are able to customize the pins, maybe you could nix the Castle’s pin due to its unfortunate placement but restore a few others that feel most relevant? The Great Lawn, the Swedish Cottage, and the Statue of William Shakespeare seem like pins that are reasonably connected to the Delacorte and unlikely to obstruct the Delacorte’s pin.

—jameslucas ^{▄▄▄ ▄ ▄▄▄ ▄▄▄ ▄} 17:18, 23 May 2022 (UTC)

Sure, that sounds like a good plan. I can work on modifying the map later to accommodate both of these proposals. – Epicgenius (talk) 17:36, 23 May 2022 (UTC)