Timeline for more styling info on stackauth
Current License: CC BY-SA 2.5
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 16, 2017 at 16:33 | history | edited | CommunityBot |
replaced http://meta.gaming.stackexchange.com/ with https://gaming.meta.stackexchange.com/
|
|
| Dec 24, 2010 at 15:15 | vote | accept | Jonathan. | ||
| Sep 23, 2010 at 16:49 | comment | added | Jonathan. | No I really don't think that site_color will prompt requests for other colors, and you can just not implement them. If I want I can just go and get what I call the site's colour using a HTML Parser and just waste more bandwidth. I did say this in an edit of my last comment but it didn't get posted: The colour is not to say exactly which site, but to help. It is very easy to tell the difference between a SO and cooking question, but not so easy between a SO and SU question. The colours don't have to be completely unique but it would be better if each site has their own unique color. | |
| Sep 23, 2010 at 16:18 | comment | added | Kevin Montrose | @Jonathan - I suspect "site_color" would prompt requests for _primary, _secondary, etc. colors. A single site color is of marginal usefulness, especially as the number of sites (and thus of similarly colored sites) goes up. | |
| Sep 22, 2010 at 15:36 | comment | added | Jonathan. | Well if you don't call it "button_color" and just call it "site_color" then people won't ask for other buttons (you can also say no). | |
| Sep 22, 2010 at 9:48 | comment | added | Kevin Montrose | There's also the risk of providing style information on UI elements that are subsequently modified on the sites themselves. In general, its best that the API never constrain the SE engine (in terms of changes), so we can only realistically provide styling information for "set in stone" things. Like tag and question link colors. I'm not saying we'll never expand styling information, just that its a much trickier endeavor than it appears at first glance. | |
| Sep 22, 2010 at 9:44 | comment | added | Kevin Montrose | @Jonathan - obviously we can manually ban anyone who infringes our L&F, but its very difficult to promulgate guidelines in addition to data; much more reliable to restrict the data. There's also a slippery slope problem with additional styling: add one of the button colors, and we'll be asked for the rest (and why refuse, exactly?), and then some more site-identifying colors. Things get trickier still when you consider the # of sites in question here: for instance "orange" might be SO's color, but [Cooking ](meta.cooking.stackexchange.com/q/783) will be very orange too. | |
| Sep 22, 2010 at 6:30 | comment | added | Jonathan. | If I wanted to copy the look and feel of the site I'd need a lot more than the colour of a selected button | |
| Sep 22, 2010 at 6:23 | comment | added | Jonathan. | It's just that a favicon would really not fit in that well, I guess I could just get the colour manually as it's only a 50x25px ish rectangle that I want to colour in, If my app looks to official you could just remove the API key, blocking the app till I change it, if I was a difficult person. | |
| Sep 21, 2010 at 21:43 | history | answered | Kevin Montrose | CC BY-SA 2.5 |