Talk:Custom splash screen page for Windows Phone applications
Influencer - Interesting, but...
this is an interesting issue, but in my opinion some things are missing yet:
- some feedback the user gets while the splash page is active
- runnable sample code.
I tried your steps but the splash.jpg file you refer to was missing.Thomas
21:10, 3 November 2012 (EET)
Mehul raje - Need steps,
u tried with sample code i provided?, it already have splash.jpg bundled in it ,and about first point you raised could you please give me some more steps or elaboration as its working fine with me it seems some n/w related issue.Mehul
07:55, 4 November 2012 (EET)
Influencer - Used your steps
Hi Mehul, I used the steps you described in the article. I overlooked the link to the sample code in the metadata. Sorry. I'll try the sample. Thanks,Thomas
10:29, 4 November 2012 (EET)
Croozeus - Other similar articles; Sub-edited &formatted
Thanks for writing this article. As a first article on the wiki it's a good contribution.
However, I also found two other existing articles related to splash screen in the WP category,
In such cases, it would be good to exactly show what your article adds over already existing content.
Improving_the_default_Splash_Screen_on_Windows_Phone article does what your article does too. Please check, what is the difference?
I sub-edited and formatted your article. You can see what I changed here: http://www.developer.nokia.com/Community/Wiki/index.php?title=Splash_screen_for_Windows_Phone_application&action=historysubmit&diff=176837&oldid=176785
- I improved the readability of the article - use articles (a, an, the) and capitalization wherever required.
- If you use any function / variable names outside the code blocks it's a good practice to wrap them into Icode template, as I have done. This give a code like font to the text and makes it easier for the reader to differentiate.
- It's good to have the articles split up into sections - introduction,...., summary, sample code, etc. so the readers get a good idea of what the article covers. I formatted your articles into sections.
09:12, 7 November 2012 (EET)
Hamishwillee - Agree with Pankaj
There is no point creating a "duplicate" of existing content, so searching first before creating is a very good idea. If you know something about a topic then you can always review and improve one that is already there, and add your name to the update.I have added SeeAlso links to the other articles too. Looking forward to hearing your thoughts Mehul.
06:20, 8 November 2012 (EET)
Thanks Pankaj and Hamish for suggestion it really helped me , i already looked article which you mentioned in comment,
i considered following points while giving this example
1. The major one is this example considers splash screen as separate page rather than considering splash screen as popup and handling it in code behind file of application start up page or app.xaml.cs,the advantage of this is all stuff which we wants to do on application start up in background can be put in separate page(splash page in this case) rather than mixing it in start up page.
2. If application start up page is to be decided on some conditions then this approach is best way, where user can do background processing in splash page and depending on result the start up page can be decided at runtime.Thanks.
08:31, 8 November 2012 (EET)
Croozeus - Renamed and added summary
Thanks for your comments Mehul.
I've renamed the article to Custom splash screen page for Windows Phone applications which justifies the content. Also, I added a summary to suggest that there can be other ways (or similar) to create splash screens for WP apps.
Please check if you are happy with it.--Pankaj
11:15, 14 November 2012 (EET)
Hamishwillee - This is a better name + a suggestion
Hi Mehul, Pankaj
First, yes, really good to rename to differentiate from the other article.
Mehul, I don't really agree with your #1 point since you can put the popup behaviour more or less in its own page too if you want. However I do see that by making the splash screen as a page that is displayed first you have the benefits that there is no delay or flicker due to display of the popup. More important you're quite right that in the other approach the first "page" is already drawn underneath the popup while in your approach the splashscreen is the first page and you can decide the next page dynamically.
At the moment the introduction only explains why you might want a splash screen. You might want to cover some other use cases - for example perhaps you just want the splashscreen to display for a bit longer than it takes to load your app. I also suggest you add a line explaining the approach used and its benefits. So perhaps replace "This article helps you to create this splash screen." with "The article shows how to create a splash screen as a page of XAML and display it as soon as the application is launched. A benefit of this approach over others (like using a popup<make that a link to other approach>) is that the next page can be determined dynamically because it has not already been constructed under the splashscreen"
It would also perhaps be a good idea to explain the interaction with the default splash screen, provide a link to documentation on that, and explain possible issues. As I understand it the default splash screen is just an image, so presumably one implication is that your custom screen might start with the same appearance of this image and then change it.
Thanks for this
05:16, 15 November 2012 (EET)