Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries. Thanks for all your past and future contributions.
Talk:Tombstoning helper for Windows Phone 7
Hamishwillee - Very useful information indeed!
Thanks for this article. I have subedited it - please check that I have not "undone" any of the information you wanted to convey.
A few points on the changes I made (FYI):
- Icode template used for inline code markeup - makes it a bit more readable
- Code blocks can have syntax highlighting - see how I've added "code csharp" and "code xml" to make the code display better
- I've renamed since we support multiple frameworks on the wiki so specifying the platform can help make it easier to determine article relevance during search.
- I've added more to the introduction to provide better links to information about tombstoning. As a rule it is good to provide as much context about what you're trying to do as possible, so that beginners don't get lost
In general we also try not to just "replicate" information held elsewhere - because normally there isn't much point doing so (aside from the worry of copyright and plagiarism issues). So in a case like this we'd normally just have the minimum to allow users to find the right information. However in this case I've slightly amended the article so it is the "using in a base class" that "value adds" this over the original. An even better "value add" for this would be to show a worked example of adding support for your own type of UI component - since that isn't well covered in the original documentation. Hope that makes sense - its more "for your future thinking)
This is really useful!
PSWhat devices did you try this on? I like to keep the ArticleMetaData up to date.
05:33, 13 August 2012 (EEST)
Chintandave er - Thanks !
Hi, First Thanks for this useful article.
Still I suggest you to add some images/screenshot of the demo output. So User can easily understand what you are trying to say without reading the each line. If it is not generating any output that can capture then you can draw a sketch which shows the main functionality of this code if possible.
Thanks again,Chintan Dave.
Chintandave er 08:53, 13 August 2012 (EEST)
Jristola - Hi HamishNo edits are fine. I though that categorizing the article was enough but I can put the platform in the title from now on. This article was just a sideproduct of coding on a hobby project so didn't spend too much time on it yet.
10:09, 13 August 2012 (EEST)
Riussi - Tested onLumia 800
10:19, 13 August 2012 (EEST)
Hamishwillee - Hi Jristola/Riussi
Thanks for getting back to me. I've added the device up in the ArticleMetaData.
I think the article is very useful as it is easy to miss useful third party libraries, and in many cases using a base class is a useful idea. If you have time to add more later, then great.
I was wondering if it is worth creating a wiki article "Useful 3rd Party libraries for Windows Phone" to catch all these. Reason being another one was recently brought to my attention as a comment here: Facebook_authentication_in_Windows_Phone_application. What do you think - better to just use Google or is asking users about what they like a good idea?
Putting the dev framework or platform in the title is highly recommended to remove any ambiguity about the platform for readers. Its not such a big problem in this case because Tombstoning is only associated with WP (although a beginner might not know that and would have had to open it to find out if browsing the Files/Data category (for example) ). However we've had masses of cases in the past where people have used minor variations on topic names like "Getting battery strength" for Symbian C++, Python, Qt, Java ME etc. IMO it is better just to include in the name to make it very clear up front.
07:34, 15 August 2012 (EEST)
Hamishwillee - @Chintandave er - disagree
While what you have said would be useful and good advice in 95% of articles we see, I disagree in this case. There isn't any demo output or anything you can usefully show in an image. The use is straightforward and anything more than the code fragments shown would complicate the article, not simplify it.
07:42, 15 August 2012 (EEST)