Widget talk:Website graphs

I like this very much!

Great! Will there be support for the semantic propvalues? --[[kgh]] (talk) 16:49, January 8, 2013 (CST)

Thanks! This gives me much more control. Extension:Widgets was perfect for this. I need to bring the semantic property graphs back. Probably get that done this evening. I also keep thinking of the graphs in two rows, and some better CSS. Maybe even synchronizing the graphs. Thingles (talk) 16:53, January 8, 2013 (CST)

I am really amazed. You should see my eyes and mouth wide open. :) --[[kgh]] (talk) 16:59, January 8, 2013 (CST)

Ha! Awesome. :-) Thingles (talk) 17:11, January 8, 2013 (CST)

Format adjustments

Nice to have the fill display for the graphs - another goody. The property value count should have it too, while I am not sure if the active users chart should have it. An additional small wish would be to have the y-axis description it the colour corresponding to the line. --[[kgh]] (talk) 23:46, 18 January 2013 (UTC)

Glad you like it. I added the fill on properties. I spent most of tonight getting the graphs in a 2-column setup. I tried to use CSS and make it responsive, but gave up. I'm sure it can be done, but it's beyond me. I ended up settling for a basic table which works pretty well although I haven't tried it on a phone yet. :-\ I also stubbed in links for Daily and Weekly charts to see if passing URL parameters will work the way I want and they do. Soon I will need to start aggregating the raw statistics data captured multiple times a day into daily and weekly records that have ranges and averages. So, those graphs will actually be even cooler looking since they'll use dygraph range bars. :-) My plan right now is that the raw data will stay around for probably 1 year, and the daily data for say 5 years. Weekly data will stay for as long as WikiApiary exists. Thingles (talk) 05:37, 19 January 2013 (UTC)

The current changes are cool anyway. Great work! Perhaps further optimisation should be on the roadmap but with a back burner priority. A big thank you for trying to do it. The 2-column setup it ok for widescreens but it does not work for narrow ones since the columns are sticky. So this is quite a problem. They should rearrange to a 1-column setup as soon as there is no place on the display. Would splitting the different graphs into several widgets be a solution? --[[kgh]] (talk) 10:48, 19 January 2013 (UTC)

You already answered two questions I already had in my mind for you. It appears reasonable to store them as planned by you. Selling the collected raw data to admins/owners for some little fee would be an offer to consider too. Besides, I cannot wait for the range bars. :) --[[kgh]] (talk) 10:48, 19 January 2013 (UTC)

Oh boy, I just came up with an approach for the graphs that I think is going to be pretty freaking awesome! Won't be able to do anything with it today, I'm spending the day with my son looking at firetrucks and trains. But, this approach I'm thinking of is going to work out really well I suspect. :-) Thingles (talk) 14:40, 19 January 2013 (UTC)

I am very curious now. Making me wait seems to be an cruel and unusual punishment. :) Have a good day! --[[kgh]] (talk) 14:45, 19 January 2013 (UTC)

Format adjustments 2

I think there needs to be a hyphen between the name of the wiki and the contend displayed within each graph. --[[kgh]] (talk) 22:47, 26 January 2013 (UTC)

Format adjustments 3

I think "Response Time" should better be called "API Response time" since there may well be a difference between accessing the API on one hand and the wiki on the other hand. --[[kgh]] (talk) 18:07, 27 January 2013 (UTC)

WOW

This is getting better and better. Your changes of today are just amazing. Many kudos for you!!! :) There seems to be an issue with Fx. The charts for aricles and pages as well as users do not get shown. Instead there is just a blanc space until the job queue graph gets shown. It would be great if you could check on this. I cannot rule out entirely that one of my add-ons to Fx might cause this. Cheers --[[kgh]] (talk) 22:45, 9 March 2013 (UTC)

Thanks! :-) Popping the graph into it's own window is a lot of fun, and if a simple refresh is added to that popup window it becomes an instant dashboard. I'm not able to reproduce the behavior you are seeing in Firefox, however, I did have a bug in graph.js that did exactly what you are describing. I fixed it though, so I'm wondering if you might have gotten an old version of graph.js cached. Can you pull it up directly using one of those links and force a refresh. Let me know how it goes. Thingles (talk) 13:14, 10 March 2013 (UTC)

Yeah, it must still have been in the cache. Did not think about this. O_o It was working on Ch and IE since these there freshly opened. Everything is ok now. :) --[[kgh]] (talk) 22:33, 10 March 2013 (UTC)