MysticTaz

My feedback

  1. 619 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    MysticTaz supported this idea  · 
  2. 23 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    MysticTaz supported this idea  · 
  3. 56 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    MysticTaz supported this idea  · 
  4. 161 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    MysticTaz supported this idea  · 
  5. 42 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    MysticTaz commented  · 

    If you aspire to see UWP as a platform-independent interface framework, this would have to be done very carefully. Initially, it would tie UWP to the Edge browser, which only exists on the Windows 10 family of OS's. It could be carefully architected, however, to provide adapters to other web engines.

    Perhaps, there could also be use of the System.Dynamic namespaces to access all of the DOM and JavaScript objects in the DOM, although there should still be strong-typed interfaces for the well-known DOM objects (<div>, <br>, <span>, etc.).

    This would be very welcome. It would be interesting to see what cross-platform support this could lead to. Also it would be interesting to see how long this YAMSDAPI (yet another Microsoft DOM API) would live on. ;-)

  6. 84 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Universal Windows Platform » Framework  ·  Flag idea as inappropriate…  ·  Admin →
    MysticTaz commented  · 

    And I would also suggest that instead of rendering to HTML Canvas, to render to WebGL to get the hardware accelerated goodness.

    I like the idea of making this strategic for Windows, since the apps would run better on Microsoft platforms (as .NET vs JavaScript).

    MysticTaz supported this idea  · 
  7. 806 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    37 comments  ·  Universal Windows Platform » Framework  ·  Flag idea as inappropriate…  ·  Admin →
    MysticTaz supported this idea  · 
  8. 349 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    An always happy Friday as I just got the TFS complete email :) As this hasn’t hit an insider preview SDK, i’m going to mark this still as “working on it” still BUT … this will be coming to an insider build near you!

    This item heart is markup extensions. There is one item that will not be there however that is relevant to markup extensions, IServiceProvider. I created a new item for that but we are working on this item [https://wpdev.uservoice.com/forums/110705-universal-windows-platform/suggestions/19416094-iserviceprovider-for-markup-extensions-for-wpf-par]. We have created a new one and we are working on that (that includes IProvideValueTarget and INameScope) but feel we have enough to ship this and mark this larger work item done and we do point out in reference to more work items need to happen, namely the work around IServiceProvider.

    Also XamlServices.Load / Save isn’t directly related to markup extenstion so we’re viewing that…

    MysticTaz commented  · 

    Additionally, WinRT Xaml REALLY needs x:Type and support for TypeConverter's, which WinRT also doesn't have yet.

    MysticTaz supported this idea  · 

Feedback and Knowledge Base