Talk:Minimal Camera app in Windows Phone
Hamishwillee - Looks like a good start.Thanks for this. As a rule we try to avoid duplication of materials on the wiki or with MSDN - so important to work out what value your article adds over existing tutorials etc and whether it would be better to include in other articles or is worth writing your own. I don't know in this case - but please check other articles in Category:Camera#Windows_Phone
05:50, 20 June 2013 (EEST)
Diegodobelo -Hi, Hamishwillee. Thanks for your comment. In fact there are other articles talking about camera, but my intention here is make it as simple as possible to serve as a base for other camera applications. Indeed, I'm planing to add an article showing how to overlay an image over camera canvas, so I will need this article here.
14:09, 20 June 2013 (EEST)
Hamishwillee - OK - thanks for explanation
I'm not familiar with the others so I don't know if they could serve this purpose. Never the less it is a valid point, provided others could in theory similarly build their articles on yours.
Are you "finished"? Ie is this ready for an editorial review?
09:54, 21 June 2013 (EEST)
Diegodobelo -Yes, it is finished and ready for review. Thanks!
01:51, 26 June 2013 (EEST)
Hamishwillee - Subedit for wiki style
Thanks for this. I've subedited for wiki style and renamed.
In terms of suggestions for improvement I think this could/should be split into smaller chunks - more instructive and less tutorial. That would make it easier to read. So for example headings for "Integrating with XAML", "Testing for camera support", "Required capabilities", "Supporting different screen resolutions", "Capturing image", "Saving image to camera roll"
It would also make it more likely you explain what bits you're using rather than just suggesting others do so. For example explain what the VideoBrush is in XAML and what it is for, explaining that pictures are taken using .CaptureImage(); etc etc.
Lastly good to explain what is needed and what is a design choice. So "In the MainPage.xaml file update the element phone:PhoneApplicationPage to lock the orientation on landscape and to hide the system tray:" - this means that the user is forced to use landscape, while there might be good reasons to use portrait. Its a design choice that limits usefulness of the app, but does make it simpler.
07:53, 26 June 2013 (EEST)
Hamishwillee - Good changesSplitting into more sections has made this a lot more "digestible". Thanks!
talk) 04:41, 4 July 2013 (EEST)(