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:Advanced Techniques for Big UI

From Wiki
Jump to: navigation, search


Hamishwillee - Very impressive.

Hi Toni

I thought it would be a big challenge for the community to come up with something original and useful in this section of the competition, that didn't massively duplicate Nokia/Microsoft resources. You have succeeded very well and I am highly impressed by this useful and complementary article.

The author purist in me feels that I would most likely use the final solution all the time, and that it would be better if the solution was split out into its own document (though what it would be called I don't know). Certainly I would almost always have this over the middle solution by default, because even if I end up creating a big version of every page, I wouldn't start with having a version for every page. I would be tempted then to consider presenting the"final solution" only in full and only mention the half way solution.

No idea where this will end in the judging, but to my mind this is excellent.



hamishwillee (talk) 07:36, 18 December 2013 (EET)

To pe - Thanks!

Hi Hamish,

Thanks for the response, I’m glad you like it. This article is an amalgam of various techniques I used recently, but haven’t had the chance to write down. It is really hard to solve the big UI problem elegantly, but I think that creating separate pages is a nice way for both designers and developers alike.

While I certainly think that the final solution is the most powerful one, I simply had to mention the second one, which is certainly the one from Nokia and MSDN docs, for completeness and to show how to gradually adapt your UI.

If you insist, I will split it into a separate article, but then it might stand out too much. In that case the first two techniques wouldn't be good enough for their own article and I couldn't show how all three techniques can be used in a single solution.



to_pe (talk) 09:52, 18 December 2013 (EET)

Hamishwillee - I will not insist :-)


  1. YOu make a good point on having a separate article meaning it would be hard to have all solutions in there.
  2. I still believe that it would be possible to have this the other way round - your very cool solution first. Also possible to shrink the middle solution and link to more information elsewhere - ie merely as a lever to introduce the point of your approach.
  3. Maybe another approach is to update the introduction slightly to highlight the final framework better.

Or do nothing. It is still awesome.



hamishwillee (talk) 08:06, 19 December 2013 (EET)

To pe - Update imminent

Alright, you convinced me. I'll restructure the introductory part a bit and then you'll tell me if that is better :)



to_pe (talk) 17:47, 19 December 2013 (EET)

Nivesh2 - hats off!

Nice article and cool trick!

nivesh2 (talk) 05:02, 28 December 2013 (EET)