Category talk:Using new Object Documentation

Loading

It would appear the new object documentation loads every page using said documentation. That means the page loads like a slug. A slug that JulienDethurens stepped on. (Yes, it is a bad Analogy). Anyway, I think we need to fix that. - Quenty (talk • March 18)

What are you trying to say?

NXTBoy (talk • contribs)

18:33, 18 March 2012 (UTC)

He told me by PM what he was trying to say.. The problem is that every single /superclass, /methods, /properties and /events page is loaded on EVERY object page.. Try to edit any object page and look at the templates used on that page (there is a list of them)... JulienDethurens

Alternatively, look here. Notice how every single object page on the wiki links to it? It's the same for every single of these pages.. I think we need to rethink about how we use the {{ClassReference}} template.. --JulienDethurens 18:47, 18 March 2012 (EDT)

Loads super slow. I have fast internet too. - Quenty (talk • March 18)

I did notice it takes a lot to time to load any object page, but I thought it was just because they used lots of templates and included all the corresponding methods, properties and events pages. I don't believe we should include them, anyways. If the user wants to know more about them, he'll usually just click on the link.. --JulienDethurens 18:52, 18 March 2012 (EDT)

I don't want to click on 10 links. A page with like 3 lines of text doesn't hurt. About 300 of them do. - Quenty (talk • March 18)

Members don't even need their own pages. They only reason it was done that way was because no one knew about class inheritance at the time. --Anaminus 19:05, 18 March 2012 (EDT)

Not all of them. All the /superclass pages are loaded though, to populate the Derived classes list. Only the required properties/methods/events pages are loaded.

NXTBoy (talk • contribs)

23:06, 18 March 2012 (UTC)