said by rusdi:said by leibold: Starfish 's program already keeps the data for 3 days (if I remember correctly) and it would be easy enough to extend that to a longer period if needed.
Not sure about that. You see, I delete, (clean out) the site where the posts, and folding records are kept. I usually clean 'em out every two weeks or so, but I always leave the last three days of both posts, and folding, otherwise there would be an enormous number of files, on NZs site.
I think when you first viewed that, you may not have realized that what was there, was what I left from recently deleting.
I don't think I told you that, when we spoke before.
Anyway, if it becomes necessary to leave those files, for whatever method of point milestone is chosen, I suppose they could stay. They are only txt. and not very large, there would just be MANY of them.
EDIT: I guess to be clearer, I upload those data files to that site daily from my computer. I don't think, (I could be wrong) the script "keeps" anything. It merely generates the reports, then I upload 'em to nozero
s site, and post them here in the Daily Milestone post.
Hi, reading somewhat from the sideline and pondering.
My program downloads the team data of a particular day and stores it in a parsed and somewhat compressed format in the 'folding' directory.
It never deletes any of this automatically.
Posts are generated based on the files in this 'folding' directory.
These are never deleted automatically either.
So regarding the keeping of data for 3 days: yes and no
And Den, nice post regarding the way of keeping member daily output data and keep a flat file approach. Today (under the shower :P), I had thoughts along a similar line: Using a separate file with users names as index of an array with the last e.g. 20 days of outputs. Something like a stack, push a new item on top of the list, pop one from the bottom, divide by number of days and one has indeed a moving average..
I had not though it out to the point of your 'word of warning' yet, so many thanks for those remarks!
Now I move a bit back to 'lurking' mode again, to see this discussion about the thoughts about the 'wishes and desires' surrounding the milestone levels / application carry on specifically regarding this topic and not as much connected to what my code can or cannot do.
Not sure how to express this at the moment, but I mean, agreeing with Rusdi: these thoughts should be voiced, no matter if they match or do not match what it currently used, who's going to do what etc..
First get the wishes lined up, then we can move to the ideas about the actual realization.