Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Nov 14 15:35
    zachdean synchronize #217
  • Nov 13 08:33
    lsaudon closed #209
  • Nov 12 16:26
    grochocki commented #217
  • Nov 12 16:23
    grochocki review_requested #217
  • Nov 12 16:16
    zachdean opened #217
  • Oct 25 18:11
    bigworld12 commented #216
  • Oct 25 18:03
    bigworld12 opened #216
  • Oct 24 09:38
    Saratsin commented #211
  • Oct 24 07:14
    renao commented #215
  • Oct 24 00:16
    grochocki labeled #214
  • Oct 24 00:16
    grochocki labeled #214
  • Oct 24 00:16
    grochocki closed #214
  • Oct 24 00:16
    grochocki commented #214
  • Oct 24 00:14
    grochocki unlabeled #177
  • Oct 24 00:14
    grochocki labeled #177
  • Oct 24 00:14
    grochocki closed #177
  • Oct 24 00:14
    grochocki commented #177
  • Oct 24 00:13
    grochocki commented #211
  • Oct 24 00:10
    grochocki labeled #211
  • Oct 24 00:08
    grochocki unassigned #215
Johan Larsson
@JohanLarsson
lurking
vreniose95
@vreniose95
(Oh, this is CCRed95 btw)
This extension is awesome. Id love to contribute to adding more features and conditionals
Not sure if this sort of stuff would be outside the scope of this extension's intended function, but I'd love it if I could set up conditional rules for automatically converting an inline MarkupExtension (like MyProperty="{Binding ... }") based on the complexity of the binding
Johan Larsson
@JohanLarsson
it already formats markupextensions, there is a setting for that
dunno if that is what you mean
vreniose95
@vreniose95
but can you have it keep something like MyProperty="{Binding Path=TheTargetPath, RelativeSource={RelativeSource Self}}" , but with MyProperty="{Binding Path=TheTargetPath.(QualifiedType.SubProperty).AnotherSubProperty, RelativeSource={RelativeSource FindAncestor, AncestorType=ListView, AncestorLevel=2}}", have it auto convert to
<Binding Path="TheTargetPath.(QualifiedType.SubProperty).AnotherSubProperty">
    <Binding.RelativeSource>
        <RelativeSource Mode="FindAncestor" 
                        AncestorType="ListView" 
                        AncestorLevel="2"/>
    </Binding.RelativeSource>
</Binding>
Johan Larsson
@JohanLarsson
R# does a good job at that
vreniose95
@vreniose95
as in, setting the level of complexity of binding expressions to auto-nest
IIRC it doesnt do it automatically though
Also, im not sure if you can do this with the "Attribute ordering rule groups" already, but i'd love to be able to set up common WPF / UWP types, and configure the properties that are most "important" to reorganize to the top of the inline attribute set list (or at the top of the nested attribute set list). Possibly even subgroups of properties that are to be considered "related", and should be kept together during the reorder?
vreniose95
@vreniose95
Heres a very stupid pseudocode / pseudo markup example of a configuration for the property ordering and indenting schema for a single type, ie: Window
element Window
{
    [0] = XClassDeclaration
    [1] = XmlNamespaceDeclarationList, (OrderByAscending => XMLNS_ID) 
    {
    }
    [2] = Title
    [3] = LayoutProperties 
    {
        { Height, Width }
        { d:DesignHeight, d:DesignWidth }
        { Left, Top }
    }
    [4] = VisualAppearanceProperties 
    {
        Background
        Foreground
        BorderBrush
    }    
    [5] = BehavioralLayoutProperties 
    {
        { ResizeMode, WindowState }
        TopMost
    }
    [6] = OtherProperties, (OrderByAscending => Name)
    {
        $ ANY $
      }
    [7] = AttachedDependencyProperties, (OrderByAscending => Name)
      {
        $ ANY $
      }
    [8] = Ignorables
    {
        mc:Ignorable
        d:DesignSource
        d:IsHidden
        d:LayoutOverrides
        d:DataContext
    }
}
vreniose95
@vreniose95
which would produce a fixed layout of this:
<Window x:Class="Alcon.Instruments.FrontEnd.Views.TestWindow"
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
        xmlns:local="clr-namespace:Alcon.Instruments.FrontEnd.Views"
        xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"

        Title="Test"

        Height="450" Width="700"
        d:DesignHeight="500" d:DesignWidth="800"
        Left="0" Top="78"

        Background="Orange"
        BorderBrush="Lime"

        ResizeMode="CanResizeWithGrip"
        Topmost="True"

        AllowsTransparency="True"
        FlowDirection="RightToLeft"

        IconAssist.Scale="2"
        HintAssist.Hint="Hi"

        mc:Ignorable="d"
        d:IsHidden="False"
        d:DataContext="{d:DesignInstance local:MainWindowViewModel, IsDesignTimeCreatable=True}">
    <Grid>

    </Grid>
</Window>
Ray Tang
@raytangRT
Hi all, I am trying to add skin feature in my program, and the skin .xaml contain <Color x:Key="someKey" R="255" G="255" B="255" A ="255" /> and I would like to skip format on those skin directory, is there any config to achieve this? btw, I am using xamlstyle.exe to automate this. Thanks
Andrii Chebukin
@xperiandri
Do you know who in MS can issue a Blend signature key for extension?
Mathieu Fillion
@MatFillion
Hello :) I am curious when is the next publish of the extension planned? There is PR 173 I am eager to use in our team !
Dave Grochocki
@grochocki
We are investigating some installation/configuration issues right now. We would like to resolve those ASAP and put out an update with the lot
Mathieu Fillion
@MatFillion
Great!
Taras Shevchuk
@Saratsin
Hi, everyone, I have a question to the contributors. I have created port of XamlStyler for Visual Studio for Mac (previously Xamarin Studio). It's currently based on the fork of the original Xavalon/XamlStyler repo and this port is now available in official MonoDevelop repository. The question is what will be the best decision: to create a pull request to the Xavalon/XamlStyler repo and after maintain Mac Extension improvements there, or keep it as is, in separate forked repo, or something else?
Dave Grochocki
@grochocki
I think it would be good to merge in. I saw that you already created a PR (and issues with AppVeyor build). We'll need to figure that out, but Nico had been looking at the extension for Mac and is probably best to review
Taras Shevchuk
@Saratsin
Yeah, great, I wrote Nico in twitter about this PR, hope it will be merged and we'll continue support it (I'll try to made improvements to to make it more similar to Visual Studio Windows Extension)
NicoVermeir
@NicoVermeir
@Saratsin thanks for the PR! it's a huge help. I'm doing some final checks on it today and will merge it into the project if everything checks out. I've talked to @grochocki about this and we need to figure out a way to align releases and versioning of the mac / windows versions.
Taras Shevchuk
@Saratsin
@NicoVermeir @grochocki , I've created PR for Mac extension. Now it supports "Settings.XamlStyler" configuration files. Please check it when you'll have time
Mathieu Fillion
@MatFillion
@grochocki we're looking foward the next release of the extension with #173 included, is there anything we can help ? Should we use a locally-built vsix ?
Dave Grochocki
@grochocki
I would like to get a new version published ASAP. Working through some reports of compatibility issues and configuration bugs, which we are having a hard time reproducing, but there are enough reports that there might be something to them. Working to resolve those ASAP and then publish an update.
Mathieu Fillion
@MatFillion
:thumbsup: