Creating a carousel that uses composition.

When the user clicks on a sample within the sample app the back button should appear.

(like stream or storageFile helpers)

Is there a reason why we are still targeting 10240? It leads to weird VS experiences since most new users will only have 10586. Note that this will only mean we are compiling with 10586, but the code will still work on 10240.

If there is no objection, I would like to move to targeting 10586.

When just entering a plain string I still see that the code is attempting to add a media_id on the end of the URL.

https://api.twitter.com/1.1/statuses/update.json?status=testing%20from%20within%20an%20app&media_ids=

Go to the sample app and onthe hamburger test page select right for PanePlacement

When a sample category is selected from the split view menu the main content page needs a title. This should be pulled from the JSON file.

Only xaml so far

Having a placeholder image gives a good user experience and we should add this to ImageEx control.

• PlaceholderImageSource
• PlaceholderImageStretch
• PlaceholderAnimationDuration
• Need to allow Source Property to get set to null as using the control within ListView Itemtemplate with large number of images will require system to set unset the source.
• For a non zero animation duration, use composition api to fade in.

Create a ticker control with nice animation when changing numbers.

Share to Facebook
Share to Twitter

https://www.microsoft.com/cognitive-services/en-us/computer-vision-api

We need a Staggered Grid control that works like wrap grid but can take different sized images (rendered equal width / different heights. Alternatively we could create a Panel that renders items in staggered manner and this can be consumed from GridView by setting ItemsPanel

1. Implement virtualization
2. Each column maintains the current height and the next item is set in the column that fits it correctly.. that implies that it doesn't need to follow the style of wrap panel

Old school XAML had a WrapPanel, but UWP doesn't. HTML supports this natively (if items don't fit on the current line, they simply wrap to the next line).

UWP XAML has "WrapGrid" and "VariableSizedWrapGrid", but these don't allow truly variable sized items, despite their name. They both take a dependency on the first item's width. The VariableSizedWrapGrid allows different sizes, but the sizes have to be a factor of the original item's size.

Here's a good implementation of WrapPanel that I've used: http://codepaste.net/8gr5go

I believe their implementation is correct except for one issue, I think if you change the Orientation property after it has displayed, the layout won't update? They need to call InvalidateMeasure when the Orientation property is changed? Like the following...

    public static readonly DependencyProperty OrientationProperty =
        DependencyProperty.Register("Orientation",
        typeof(Orientation), typeof(MyWrapPanel), new PropertyMetadata(Orientation.Horizontal, OnMeasureAffectingPropertyChanged));

    private static void OnMeasureAffectingPropertyChanged(DependencyObject sender, DependencyPropertyChangedEventArgs e)
    {
        (sender as MyWrapPanel).OnMeasureAffectingPropertyChanged(e);
    }

    private void OnMeasureAffectingPropertyChanged(DependencyPropertyChangedEventArgs e)
    {
        base.InvalidateMeasure();
    }

Add enums to specify more precisely the kind of search we want to do

These should be set in the control's style. For example, HamburgerMenu.

New project created with 5.1.1 Core runtime. I added the Facebook SDK ( as described here: https://github.com/Microsoft/UWPCommunityToolkit-docs/blob/master/en-us/uwp-community-toolkit/services/facebook.md ).

At project load I still get this exception loading. I am referencing the Microsoft.Toollit.Uwp.Services, and winsdkfb libraries.

{"Requested Windows Runtime type 'winsdkfb.winsdkfb_uwp_XamlTypeInfo.XamlMetaDataProvider' is not registered.":"winsdkfb.winsdkfb_uwp_XamlTypeInfo.XamlMetaDataProvider"}

I can share the sample project if you want to see it yourself.

The current version is based on
http://winrtxamltoolkit.codeplex.com/SourceControl/latest#WinRTXamlToolkit/WinRTXamlToolkit.Shared/Imaging/ColorExtensions.cs

There is an updated version in the new location of the WRTXT
https://github.com/xyzzer/WinRTXamlToolkit/blob/master/WinRTXamlToolkit/Imaging/ColorExtensions.cs

Create a new project and ONLY reference the Microsoft.Windows.Toolkit.Services assembly.

Attempting to reference: Microsoft.Windows.Toolkit.Services.Facebook.FacebookService.Instance.WindowsStoreId results in a typeload exception.

Additional information: Could not find Windows Runtime type 'winsdkfb.FBSession'.

Are we going to add an additional dependency on the services assembly or require users to add another dependency?