|
I'd hold off until it's known if G+ is going to survive any longer than any one of the other 300 betas that Google killed off over the last year.
|
|
|
|
|
| +1
Henry Minute
Do not read medical books! You could die of a misprint. - Mark Twain
Girl: (staring) "Why do you need an icy cucumber?"
“I want to report a fraud. The government is lying to us all.”
I wouldn't let CG touch my Abacus!
When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is.
|
|
|
|
|
Henry Minute wrote: +1
Univoter, eh?
"I love deadlines. I like the whooshing sound they make as they fly by." (DNA)
|
|
|
|
|
Just had a thought about reputation wearing off ( with a similar system to tennis ATP ranking, for instance) with time. This would:
- keep the reputation more "up-to-date", e.g. it is not because I have contributed ten articles ten years ago in VB6 that I am still "reputable" enough to answer ASP.NET questions. I take my own case as an example: I have not touched a line of code since 2007 and still profit from the reputation I gained answering questions in the C++ forum more than 8 years ago.
- give newcomers with good competences a hope to reach the "gods circle" of top posters/members, since the top scores would not be so high as today. It is nowadays impossible to outscore them, or even to become slightly visible...
|
|
|
|
|
Rage wrote: "gods circle" of top posters/members, since the top scores would not be so high as today
I doubt that.
The top gods (CG , Nish , Pete , ...) are still active so there reputation would remain pretty much the same.
And who says your not qualified to answer questions.
I'm sure if you wander into the c++ forum you could still answer some of the questions there and you'll probably find questions the same or similar to the one's you answered 3 years ago.
|
|
|
|
|
Tom Deketelaere wrote: would remain pretty much the same.
Exactly my point: keep the same, not climb to the sky. And by keeping the same, other could come in their reach.
Tom Deketelaere wrote: And who says your not qualified to answer questions.
Trust me on this one A lot of APIs have changed since MFC...
|
|
|
|
|
Rage wrote: A lot of APIs have changed since MFC...
Yeah but the questions haven't, that's the problem 
|
|
|
|
|
So you're saying only show reputation based on x number of years, and every day, the points for the day beyond that time period is no longer counted? I think that merely calls for a different graph.
This graph would should the points gained for the last 365 days, or since Jan 01 of the current year, and would merely be an indication of daily accumulations of each category of points. I would certainly bring the less easily obtained points higher up on the graph. I envision trend lines and other features. I think Pete was supposed to be working on a Silverlight module to allow more flexible graphing of data, but I don't now what the status of it is.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
John Simmons / outlaw programmer wrote: I don't now what the status of it is.
Memory leaks in the Silverlight RIA services that I'm still trying to work around. Show too much reputation and *boom* the graph dies in a pathetic heap.
|
|
|
|
|
Pete O'Hanlon wrote: Show too much reputation
...and on my end I need to provide weekly or monthly summary data for the graph. Daily is too much.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
If you could do that with the current ODATA service, this would ease the pain in the RIA.
|
|
|
|
|
I'm working on a desktop app (article) right now that only shows the most recent year's worth of rep data 8 series * 365 days = 2920 data points. Yesterday, I finally got moving on it again, and got the daily scrape/database stuff working. I now have a whopping 1 day (8 data points) worth of data. Of course, it only scrapes once per day and it's gonna take a while - well, a year - to get enough data gathered to see it's true performance characteristics, but I don't anticipate many/any issues.
The user will be able to display the data as daily, weekly, or monthly data, including trend lines, and end of week/month/year projection of points earned.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
Why are you using RIA? We started to and ran into the same problems, and switched over to a WCF web service with a single method in it (accepts stored proc name and parameters in the form of xml data, converts the xml params to sqlparameter objects, calls the stored proc, and the stored proc returns data as xml).
It works great, and is very performant.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
John Simmons / outlaw programmer wrote: It works great, and is very performant.
So you've gotten acceptable performance with WCF?
3x12=36
2x12=24
1x12=12
0x12=18
|
|
|
|
|
Two doozies in one.
My teeth are grinding.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Well, it's just a matter of passing a bunch of strings around for us. It works very well (although getting all our ducks in a row regarding getting the silverlight module to talk to the service was a pain in the ass).
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
The amount of data that was being returned was making this too prohibitive, as we would be firing from SL to web-server, and then from web-server to web-service (returning a lot of data). That's why I was using RIA.
|
|
|
|
|
Not just showing the graph, but also reporting the total rep as based on the last N years.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
I've thought about this a lot. It's tempting. One of the issues, though, is that in places such as QA where we show a member's rep along with their post, this rep may, over time, reduce. Having an answer appear to come from a lower rep member than was the case at the time the answer was posted may do the answer an injustice.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Allright.
I actually find John's idea interesting: in fact, my request is nothing else than another view on the database, so it could be well achieved with a graph or with the information being displayed somewhere in a profile, for instance "recent reputation" as opposed to "all time reputation". let's wait till the graphs are available...
|
|
|
|
|
I'm writing an article/application right now that I think does what you want. I'm working on the graph part right now while the associated web service scrapes data once per day (I have the luxury of not having to actually tally each point value, so that's why it works for me). The app will only show data that's no more than a year old. Anything beyond that is cast off an no longer applicable to the application (but it is kept in the database so someone can write additional code to get to it). Right now, I have three days worth of data for myself. That's anough to do all the chart work.
It's called "Reputationator".
I can post the database table schema I'm using if you want to start manually collecting your own data.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
Good, I look forward to it.
John Simmons / outlaw programmer wrote: It's called "Reputationator"
John Simmons / outlaw programmer wrote: I can post the database table schema I'm using if you want to start manually collecting your own data.
Thanks, but my own reputation is of no interest, I'll wait until this is available for vieweing everybody's.
|
|
|
|
|
It will only scrape for one user 9at first). Eventually, it will show you where you are in comparison to the 2 people ahead of you in points, and the two people behind you. It's not intended to really watch more than one person, but I suppose I could make it do it. The real problem is that it takes a few seconds to scrape the profile page for the specified user. I feel like even if it supported multple users, I would have to limit the number to something reasonable like 10 or so. I was going to remove it from the table, but it's looking like it was a good idea afterall to save the user's ID with each point value.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
I fired up the diff engine to see what the edits made to my alternative[^] were.
Revs 2/3 are showing irrelevant(?) <p> tags. If you diff v1 against v3, the closing tag and my paragraph are missing the last 2 characters. 1 vs 2 or 2 vs 3 are hiding the trailing bracket of the /p tag as well.
The period at the end of the sentence only shows in 1 vs 2, or 1 vs 3 in the new revision. In 1 vs 3 it's marked as added, but not is 1 vs 2. 2 vs 3 doesn't show it at all.
I think your diff code has a few fencepost errors in the string handling code. 
3x12=36
2x12=24
1x12=12
0x12=18
|
|
|
|
|
Both here and in The Lounge (haven't tried elsewhere) if I hover over any part of a post subject line I get a ToolTip of "None".
Of course there is always the possibility that this is intentional, in which case please ignore this message.
Henry Minute
Do not read medical books! You could die of a misprint. - Mark Twain
Girl: (staring) "Why do you need an icy cucumber?"
“I want to report a fraud. The government is lying to us all.”
I wouldn't let CG touch my Abacus!
When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
