Talk:Naming Lights
There needs to be at least some page for about naming lights, just because some information exists somewhere does not mean that it is organized. Right now, this information is arbitrarily scattered about, and this page was intended to be a means of collecting those facts in one place. This page should be referenced to or included in the others...--TheFixer333 23:23, 18 July 2009 (UTC)
It's weird to have a whole page for an issue affecting only 3 entities or so... I like the text, though. Maybe this could be pasted to each light entity instead? Reaper47 23:50, 18 July 2009 (UTC)
- Indeed, a part of me agrees on every point...but the problem I keep comming back to is that there are actually a number of Lighting related pages scattered all over which attempt in explaining naming lights, their effects, uses, and in-depth explinations for how it all works. Ideally, this would be the way to clean that up - unfotunately, very little functions in an ideal way, LOL. I just figure...why not try to make something better when you see it. (because I'm the type of person who will forget and come back repeatedly LOL). It's this reasoning that I've always valued templates for short-info, and then descriptive pages for in-depth (even b4 I started editing and didnt understand wikimedia formatting). It just seems like the most efficient/precise method. But back to the point, I've actually made bits to include inside the light entity pages. But even if this were a smaller subject, how else do we organize it? Is common method to just link-link-link? All of this is helping me to learn wiki, so either way, yay!--TheFixer333 02:11, 19 July 2009 (UTC)
- I see what you're doing now. I thought you were simply using this page as a way of singling out the text you wanted. :-) I don't think Template:Light NameInfo is needed though: Template:Light NameWarning should be noticeable enough on its own. --TomEdwards 11:19, 19 July 2009 (UTC)
- Agreed. I look at NameInfo, then NameWarning...there doesn't need to be THAT much quick-info on ANY page. I saw what was done in Light and I just replaced it with a more readable version then added it to the others, but it really IS redundant. I think it should go. The question still remains, though - should stuff go here, or in a subsection of 'Lighting' etc? This page does seem a tad excessive. Should I just pool in the other stuff into ONE subsection, then link it all?
- Any article that tries to pool everything into one place would end up a horrible mess. Much better to start a new category for static lighting... --TomEdwards 18:57, 19 July 2009 (UTC)
- I also realized that Naming Lights is actually a PART of the the issue of 'switchable' lights, since naming, setting pattern, or setting styles ALL HAVE THE SAME EFFECT. They create these 'switchable' lights. LOL, it feels like attacking the situation from the wrong side. I should've noticed that earlier, because the most the subject of naming lights needs, is to understand how name pairs interact together (or apart) in a group of lights - everything else is universal to switchable lights--TheFixer333 19:19, 19 July 2009 (UTC)
- Agreed. I look at NameInfo, then NameWarning...there doesn't need to be THAT much quick-info on ANY page. I saw what was done in Light and I just replaced it with a more readable version then added it to the others, but it really IS redundant. I think it should go. The question still remains, though - should stuff go here, or in a subsection of 'Lighting' etc? This page does seem a tad excessive. Should I just pool in the other stuff into ONE subsection, then link it all?
- I see what you're doing now. I thought you were simply using this page as a way of singling out the text you wanted. :-) I don't think Template:Light NameInfo is needed though: Template:Light NameWarning should be noticeable enough on its own. --TomEdwards 11:19, 19 July 2009 (UTC)
screenshot...?
What exactly is the error being shown in the screenshot? It just looks like a light and dark variation of an albedo. Pinsplash (talk) 23:06, 21 June 2018 (UTC)