Talk:Creating a Timer, independent of System Time in Windows Phone
Hamishwillee - Review/under construction
Firstly, thanks very much for taking the time to create this. I added some comments here about the scope and content.
What I have done is split this up a bit in line with what I am hoping will happen. Since we have a number of options, none of which are perfect I'd quite like an article which covers all the options. Ideally it would explain them, provide code fragment, and overview the advantages and disadvantages of each. Then it would have a code example showing them. At the moment everything is a placeholder.
If we can't do this, then we need to be more precise in the title to identify the specific approach used, and we should have real rather than pseudo code. So "Using network timer for system independent time" or similar.
In terms of the section that is complete, this looks like a combination of monitoring the elapsed time while app is running and comparing to network time to penalise them if they try mess with system time. Is that correct? If so, what is to stop them just disabling network time? What if you can't get network time?
I would also probably pull out the detail of password protection - ultimately we're most interested in the bits about "telling the time elapsed".
What do you think, can we be more precise in the other sections?
I know I've turned your semi complete article into a bit of a dogs breakfast, but I'm half way between where I'd like to be and where you were :-0
Hope it makes sense what I'm trying to do.
10:28, 10 April 2013 (EEST)
I appriciate the changes you made. Article looks neat now. And regarding the implementation, i think there is some confusion. We are not relying completely on network time. We have three things to calculate elapsed time : system time, network time and periodic agents. But we can not rely on any one of these completely. Hence the pseudo code takes advantage of all of them to calculate the elapsed time more precisely. And yes we need to mention the tradeoffs with the approach. I will do that. Currently i can't think of a rock solid solution which will work every time with 100% accuaracy but we can use whatever is available to get best out of it. Let me know if we can improve this approach. And i will try to come up with a sample code in coming few days.
Also if you can think of a nice title you may do so. Even i am not too happy with this title.
11:42, 10 April 2013 (EEST)
Hamishwillee - Suggest we do as above
Still didn't get to this properly, hopefully soon.
>Let me know if we can improve this approach.
I don't know if we can improve the approach for the "overall" method you've got here. However as I suggested previously we can improve the structure of the article. If we break it into bits "ie using Network time" then we can explain the pro's and cons of just that approach, and show just how to check that (in real, not pseudo code). Ditto for other approaches.
When we have done that we can explain our "best" solution which attempts to overcome the tradeoffs - this is what you've jumped to.
Doing it this way means that someone else can come along and see the logic of what you're doing, and decide whether they want to handle the tradeoffs differently.
08:03, 15 April 2013 (EEST)
Vinayppatil - Code for Period task and Timer approach
Found this buried in some corner. :P Maybe we can finish it. I added code for Period task and Timer approach. Have a look and let me know your views.
talk) 12:35, 29 January 2014 (EET)(
BuildNokia - I think this is good to go.
I had a look at this article and I think it's great. If you're comfortable doing so, I'd suggest we remove the "Draft" mode and publish it so others can use it.Jen
talk) 02:02, 13 June 2014 (EEST)(