As far as I am concerned JavaScript should never have a control we don't have. This one seems like it might be easy to implement. Getting a lot of requests for it @ application accelerator labs, // Jerry

If you run the sample application with a dark theme, the back button in the settings fly out no longer has a hover color. You do get one in the light theme. I'm not clear why this isn't working, as it should be pulling the BackButtonHoverBackgroundBrush from the current theme, as far as I can tell. Pressed color works though.

....Stefan

UX guidelines talk about error/warning bars but provide no guidance on what controls to use, only the position. This would be a simple control to add a Popup positioned at the UX guideline area for the error/warning

Right now the Flyout bases are really designed to be instantiated from code. This is not ideal for MVVM in all cases as well as doesn't help in designer scenarios.

When you use the flyout control and only add ToggleMenuItems. The result will be a flyout with it's right border trimmed to the text instead of having the same left margin behind the text.

Example screenshot: http://yfrog.com/esrpddp

Code to reproduce:

    private void ShowFlyoutMenu(object sender, RoutedEventArgs e)
    {
        Flyout f = new Flyout();
        f.PlacementTarget = sender as UIElement;
        f.Placement = PlacementMode.Top;
        f.Closed += (x, y) =>
        {
            LogEvent("Event: Closed");
        };

        Menu menu = new Menu();

        ToggleMenuItem tmi1 = new ToggleMenuItem();
        tmi1.Text = "Visug";
        tmi1.IsChecked = _toggleMenuChecked["visug"];
        tmi1.Tapped += (a, b) =>
        {
            _toggleMenuChecked["visug"] = !_toggleMenuChecked["visug"];
        };

        ToggleMenuItem tmi2 = new ToggleMenuItem();
        tmi2.Text = "WiPhug";
        tmi2.IsChecked = _toggleMenuChecked["wiphug"];
        tmi2.Tapped += (a, b) =>
        {
            _toggleMenuChecked["wiphug"] = !_toggleMenuChecked["wiphug"];
        };

        menu.Items.Add(tmi1);
        menu.Items.Add(tmi2);

        f.Content = menu;
        f.IsOpen = true;

        UpdateLayout();
    }

I am unable to get WebViewExtension binding to work and am getting two exceptions thrown when the binding occurs at runtime. The first thrown exception (chronologically) is:
"A System.InvalidCastException was thrown: "Unable to cast object of type 'Windows.UI.Xaml.Data.Binding' to type 'System.String'"
and then the XamlParseException.

The InvalidCastException, which seems to be causing the issue is at this line in \obj\Debug\XamlTypeInfo.g.cs:
Callisto.WebViewExtension.SetStringSource((Windows.UI.Xaml.Controls.WebView)instance, (System.String)Value);

I have a simple repro app to show this with the following code (full solution available on request). Any ideas how to get this working?

Page:

<Page
    x:Class="WebViewExTestApp.MainPage"
    IsTabStop="false"
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    xmlns:local="using:WebViewExTestApp"
    xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
    xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
    xmlns:callisto="using:Callisto"
    mc:Ignorable="d">

    <Grid Background="{StaticResource ApplicationPageBackgroundThemeBrush}">
        <WebView callisto:WebViewExtension.StringSource="{Binding Content}" HorizontalAlignment="Stretch" VerticalAlignment="Stretch"/>
    </Grid>
</Page>

Code:

using Windows.UI.Xaml.Controls;
using Windows.UI.Xaml.Navigation;

// The Blank Page item template is documented at http://go.microsoft.com/fwlink/?LinkId=234238

namespace WebViewExTestApp
{
    /// <summary>
    /// An empty page that can be used on its own or navigated to within a Frame.
    /// </summary>
    public sealed partial class MainPage : Page
    {
        public MainPage()
        {
            this.InitializeComponent();
            DataContext = post;
        }

        Post post = new Post() { Content = "This is test content." };

        /// <summary>
        /// Invoked when this page is about to be displayed in a Frame.
        /// </summary>
        /// <param name="e">Event data that describes how this page was reached.  The Parameter
        /// property is typically used to configure the page.</param>
        protected override void OnNavigatedTo(NavigationEventArgs e)
        {
        }

        public class Post
        {
            public string Content { get; set; }
        }
    }
}

There can definitely be a need/consideration for having a stronger typed AppBarButton rather than just a styled button. This would allow it to automatically respond to snapped state which is supposed to remove showing the label for the button.

Please implement a Closed handler on SettingsFlyout, so that I can be notified when it shuts. There are a number of settings that the user might set that will cause me to refresh the page. I don't want to do that until the user has completed the settings, otherwise it could waste a lot of data, so I need to know when the fly out is shut, and refresh then. Would be fine if it worked the same way as Flyout does, I think.

enough said.

We test the same code in 2 machines and found out that one of the machine doesn't have any background for the setting flyout panel? Any idea?

Seems to be because it presses on the flyout/popup as it is appearing

If you are using Callisto but not using SQLite, the app will fail store certification. This is because the app would need to declare the C++ runtime as a dependency. If an app isn't using SQLite though this is not clear and seems unnecessary.

This might be a reason to remove the SQLLite.cs file with Metro mods from this project and just point to the original source.

Implement a pivot control like the Windows Phone has. Use open source history from phone.codeplex.com as base starting point?

If a ToggleMenuItem is used with other menu items, then the entire aligment of the menu items is off and against the UX design for the ToggleMenu per design.windows.com. This needs to be fixed so that if a ToggleMenuItem is used with others, then the overall Menu margin on the left is wider.

In OAuthTools.cs, line 310 (inside the final GetSignature overload) throws a NotImplementedException because it passes “HMAC_SHA1” into the OpenAlgorithm method. According to the documentation on MSDN "HMAC_SHA1" isn’t a valid value.

Since the algorithm provider class instantiated inside the method is only used to specify which provider implementation should be used in your HashWith extension method (Extensions.cs, line 414), perhaps a better implementation would be to just translate the OAuthSignatureMethod enum value into a string and pass that into the HashWith method. As long as the “HMAC_SHA1” string gets passed into the MacAlgorithmProvider.OpenAlgorithm method, things work fine.

WinRT XAML lacks basic charting components. Port Silverlight Toolkit components for use

If Flyout contains a textbox, it will not update position when the touch keyboard slides out

Here is a sample I found that has some basic repositioning logic
http://snatz.ioix.net/data/news/view/14315138866459610847-12-03

I may be doing something wrong. However, it seems that the binding to Rating.Value does not work when the underlying value is changed. If I set the Value property without binding the stars show properly. If the user selects a star the binding fires into the view model.

Would you have a sample that demonstrates binding to the Rating control. Specifically binding the underlying value to the rating control on load of the screen to show what a user had rated in the past.

Thanks much,
Tom

When setting IsEnabled=False (for a read-only) implementation, the styles are not functioning properly

Implement date/time pickers using Globalization calendar information.

Need to review UX guidelines to see what missing gaps exist in functionality.
http://msdn.microsoft.com/en-us/library/windows/apps/hh465471.aspx

The settings pane root popup should actually transition in as well (not just the content). The Popup doesn't allow the panel animation right now in the consumer preview so this can't easily be implemented that won't be throw away code.

PopupMenu can be used for Menu scenarios in XAML apps, so why would we need Menu? One argument is that Menu in Callisto can better align with MVVM models as PopupMenu doesn't implement ICommand but rather IUICommand.

Additionally Menu can be styled/templated.

Because the SettingsFlyout design is a light theme, the default is dark text, which is fine. The problem arises when a user chooses dark theme app (in App.xaml) and then the text on the SettingsFlyout will be all light, making it miserable.

What needs to happen is overrides within the SettingsFlyout by having theme resources defined in generic.xaml. The problem is that they all have to be defined again (including all variants for Menu and other defined brushes within Theme RDs. Having Issue #1 resolved might help this

Hi,

Using SettingsFlyout control the following throws an exception, I tried adding a Grid with that Name, doesn't work

_contentGrid = GetTemplateChild("SettingsFlyoutContentGrid") as Grid;

Is this a issue or am I missing something?

The binding now works in one direction (from DataContext to control) thanks (very much!) to your fix (76531d3), but not from control to DataContext. I am using a

    <Page.Resources>
        <ResourceDictionary>
            <local:PostContentToViewerHtmlConverter x:Key="posttoviewconverter"></local:PostContentToViewerHtmlConverter>
        </ResourceDictionary>
    </Page.Resources>
...
        <WebView x:Name="blogPostViewer" Margin="0,88" callisto:WebViewExtension.HtmlSource="{Binding Content, Mode=TwoWay, Converter={StaticResource posttoviewconverter}}" />

    public class PostContentToViewerHtmlConverter : IValueConverter
    {
        #region Constants
        const string editorBaseHTMLPrefix = "<html><head></head><body><div id='postContent' contenteditable='true'>";
        const string editorBaseHTMLSuffix = "</div></body></html>"; 
        #endregion

        public object Convert(object value, Type targettype, object parameter, string language)
        {
            return editorBaseHTMLPrefix + value + editorBaseHTMLSuffix;
        }

        public object ConvertBack(object value, Type targettype, object parameter, string language)
        {
            return value.ToString().Replace(editorBaseHTMLPrefix, "").Replace(editorBaseHTMLSuffix, "");
        }
    }

There should be a ToolTip on RatingItem to show the value for the Item (ItemCount index or perhaps a new DP on RatingItem)

When there are multiple levels of flyouts, the backbutton does not seem to work as expected. The backbutton only seems to go back to the settings charm. If I have gone from one flyout to another flyout, the backbutton should move me to the previous flyout, at least this is my expectation.

Add some helper to enable the 'push scrolling' capability you see on the start screen for horizontal panning with mouse.

I wonder if we should rename LiveTile -- this is very much a Start Screen term and we don't want to confuse what the developer creates with something that won't show up on the Start Screen experience?

Need a ToggleMenuItem (to show a checkmark next to the item)

Currently the SQLite methods are synchronous which doesn't totally match with the Metro philosophy. In most cases the operations are likely fast enough not to matter. However we should consider making things like Insert, Create, Drop, etc. async.

Need a CR/better enhancement on PlacementTarget logic on Flyout. This was extracted from Silverlight toolkit and some hacks in place to meet UI guidelines for Win8...would be good to see if this could be tightened up some more.

The animation should reset every time you press on it so it appears responsive. Now it just stays in the same state.

Grid containing the actual settings panel content should have a vertical alignment of Stretch, rather than top.
The template uses a ContentControl rather than a ContentPresenter.

I haven't tested this in all cases, but setting _windowBounds in the constructor of the control and then using it in the loaded event to set Canvas.LeftProperty doesn't allow reaction to changes in the layout. If the view loads in fullscreen mode, and then is changed to filled, the settings flyout will render too far to the right by 320 pixels.

Since the sample app was moved to a frame navigation model, the keydown events aren't being captured in the Menu anymore.

Without question, this is the most commonly requested Metro control.
// Jerry

HighContrast on Rating/Rating item isn't working due to needing to map system resources to Color (not brush)

User is not able to set colors without re-templating

Review SuppressMessage annotations on APIs for more clean CA code. low pri

It seems that I can't make a Flyout bigger than Width=450 or so. Is this by design or is there someway I can make it bigger?
I tried specifying the width of my user control at construction time but it still did no good, the controls were cut off on the right hand edge.

If you keep invoking the flyout really quickly, the flyout still sometimes appear at the non-desired position.

1. Set flyout to open from top
2. Repeatedly click button quickly
3. Flyout will open on right

Implement an API helper to dynamically switch to light/dark theme on a given visual tree starting point. This allows for the app to have one theme (i.e., dark) but other areas (i.e., Settings panel) to have a light theme without having to re-style each control being used.

the flyout experience is supposed to fade out if you look at other system-level flyouts. Popup currently doesn't allow animations to run when IsOpen=False is set. A bug has been filed on the consumer preview and we will have to wait to see if that can be changed

Hi,

I followed your blog entry and example on this project page to use Flyout control for Settings page in my http://metrorssreader.codeplex.com,

It looks like I need to specify PlacementTarget element even for use in Settings, which throws an exception when not specified,

Please help.

After clicking the control which the Flyout control PlacementTarget is set to, the position the flyout appears is shifted down to the right. I was able to repro this issue in the sample code as well by clicking the Show Menu button repeatedly and quickly.

RTL for both FlowDirection as well as OS-based RTL languages needs to be handled correctly for the developer. Right now, for instance, SettingsFlyout will always position on right side of the screen. If the OS is an RTL language, then the charms bar will actually be on the left and the SettingsFlyout should position accordingly to be predictable for the user

I dont know but I can't use in DatePicker. I installed your package, I wrote Using Callisto.Controls but DatePicker is not there.