×
Namespaces

Variants
Actions

Talk:Scrolling horizontal menu bar in Qt and Windows Phone

From Nokia Developer Wiki
Jump to: navigation, search

Contents

Hamishwillee - Interesting approach

Hi Somnath

Some thoughts

  1. A little odd because it doesn't fit with either platforms' UI style. However it is interesting and a perfectly valid UI decision. It is probably worth adding the fact that this isn't "in style" to the top of the article though.
  2. If I were to do this I'd probably use a horizontal list view for the toolbar rather than a flickable. Mostly because I think the logic would be more obvious. Wouldn't change it though - there is always more than one way to do anything. I added a "Tip" about this
  3. Some of the code snippets are not well formed.
  4. Do you need to set anything in the Flickable to tell it to only scroll horizontally?
  5. In the example "BitmapImage bi = new BitmapImage();" there isn't anything to say how this is called - ie where is the handler defined?

Thanks very much

Regards

Hamish

hamishwillee 04:11, 26 October 2011 (EEST)

Somnathbanik - Compatibility

This article is Compatible for both Windows Phone 7 and Windows Phone 8.

We will update the title accordingly.

somnathbanik 14:10, 5 June 2013 (EEST)

Hamishwillee - And content

Title looks good, but would be great if the content also referred to Windows Phone.

hamishwillee 09:18, 10 June 2013 (EEST)

Somnathbanik - And content

You mean to say to change the name of the source file to something like ScrollMenuWindowsPhone.zip ?

somnathbanik 12:08, 10 June 2013 (EEST)

Hamishwillee - No

I mean that you've changed to refer to Windows Phone in the title, but the first line says "This article demonstrates how to create scrollable/flick-able objects in Qt and WP7.".

I would change to be as generic as possible - ie "This article demonstrates how to create scrollable/flick-able objects in Qt and Windows Phone." I would change other instances where THIS MAKES Sense. I don't think it makes sense to change the name in the source code because this is based on WP7 template, so that is useful. Also wouldn't change "WP7 Project" section title - unless the project is "generic" across versions. However I might change "The full source code of WP7 example is available here" because the project is implied by the file name.

Not so important for "Qt comparison" articles, but in general the most important thing is to quickly check that the API hasn't changed for the component in question in WP8. So for example if you were talking about "live tiles" the API has been significantly extended in WP8.

Thanks

H

hamishwillee 04:42, 11 June 2013 (EEST)

 
×