Fix Incomplete Information Given by S2 Layer Browser

[fallen_x_ashes]

Title
Fix Incomplete Information Given by S2 Layer Browser

Short, concise description of the ideaCurrently the S2 Layer Browser only displays information about classes, methods, global functions, and properties if they are explcitly defined within the layer. However each layer underneath the Core Layer inherits behavior from above its heirarchy.

Comments

[hakeber]

I'm all for completeness.

[camomiletea]

No, please.

The listing of all the Core properties, all the Core methods takes up 58 screens (at my screen resolution). If all layouts, themes, and user layers also listed these along with the stuff defined only in them, there'd be an information overload.

This change will hopefully make the learning curve of S2 a little less steep,

Hahaha, sorry but that is hilarious. Most people find advanced S2 scary and if there's this huge list of stuff -- who is going to want to dig through it? They can always look at the Core stuff separately.

As the Advanced S2 Customization center is used by only a small percentage of viewers in comparison to the entirety of Livejournal, these changes should not cause any wide disruption of service despite their need for greater resources.It will disrupt it for those users who do currently use it, because there would be just too much information. It will become even more daunting to teach those who want to have more control over the look of their journals. I regularly refer users to advanced S2

[camomiletea]

I might have misunderstood what you meant. If so, please do clarify.

[fallen_x_ashes]

This change will hopefully make the learning curve of S2 a little less steep,

Hahaha, sorry but that is hilarious. Most people find advanced S2 scary and if there's this huge list of stuff -- who is going to want to dig through it? They can always look at the Core stuff separately.

No It's not hilarious. With properly defined docstrings, evrey class, method, and property used in a style will be exposed, and the reason why and how it is used in the style can be stated. S2 is complex and needs 58 screenfulls to be explained properly.

Additionally, there is still the fact that overriden methods or completley new methods in a layer do not show up AT ALL. That at the very least should be fixed, and won't result in the informaton overload you're worried about.

[av8rmike]

I'm with you on the browser showing classes and methods that are defined in a given layout/theme layer.
However, I don't think the layer browser can know whether a given theme/user layer is part of a user's style or is floating free, so to speak. I doubt it could do the kind of recursive object inheritance browsing you're describing. The whole thing seems like a solution in need of a problem to me. It's also a lot of work to implement, for limited user benefit, as camomiletea mentioned.