Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 05:27
    maartenba commented #213
  • 03:10
    grochocki labeled #213
  • Oct 16 02:29
    NicoVermeir commented #213
  • Oct 13 23:04
    danielchalmers edited #147
  • Oct 10 12:37
    renao opened #215
  • Oct 10 10:15
    joaogomes44033 opened #214
  • Oct 04 22:43
    moreirawebmaster opened #213
  • Oct 04 14:35
    jfevia commented #177
  • Oct 02 07:02
    InquisitorJax commented #211
  • Oct 01 17:57
    lsaudon commented #205
  • Oct 01 17:57
    lsaudon commented #205
  • Oct 01 16:10
    grochocki commented #161
  • Oct 01 16:05
    grochocki labeled #211
  • Oct 01 16:05
    grochocki labeled #211
  • Oct 01 16:05
    grochocki commented #211
  • Oct 01 16:03
    grochocki closed #212
  • Oct 01 16:03
    grochocki labeled #212
  • Oct 01 16:03
    grochocki labeled #212
  • Oct 01 16:02
    grochocki commented #212
  • Oct 01 10:59
    JohanLarsson opened #212
NicoVermeir
@NicoVermeir
github integration seems to work :)
Johan Larsson
@JohanLarsson
yeah, sweet
Johan Larsson
@JohanLarsson
Would it make sense for the xamlstyler to support vanilla xml?
I often find myself disappointed after ctrl + k + 2 in xml docs :D
NicoVermeir
@NicoVermeir
anyone interested in joining this discussion? Xavalon/XamlStyler#16
Johan Larsson
@JohanLarsson
Dunhno if it can be integrated, perhaps as a popup
Johan Larsson
@JohanLarsson
Writing an analyzer for WPF
NicoVermeir
@NicoVermeir
anyone want to chime in? Xavalon/XamlStyler#46
Johan Larsson
@JohanLarsson
Awesome if it works! Been meaning to write a PR for that since forever.
Not having identical settings on a team creates noisy diffs.
NicoVermeir
@NicoVermeir
so we can add the setting in the setting file? that sounds like inception :D
Johan Larsson
@JohanLarsson
I can see an argument for both
Having a global setting file is perhaps easier than to export/import settings for the plugin.
Pedro Lamas
@PedroLamas
so I'm now looking at the code for the "config per solution" thingy
am I going mad here if I say that when we change the external config file in VS settings it only loads the new settings after rebooting VS?
oh, never mind
found the code in the set_config
Johan Larsson
@JohanLarsson
Nice work @PedroLamas, gonna be so nice to be able to share settings in a team.
Pedro Lamas
@PedroLamas
from what I've read, VS15 (vNext) will finnaly allow VS settings to be saved and shared across teams, so this will probably fade away then :)
Johan Larsson
@JohanLarsson
oh :)
Pedro Lamas
@PedroLamas
PR updated
Nianios Georgios
@nianios_twitter
Any news regarding a vs2017 version?
João Miguel
@CaptainJRoy
hey guys
i'm new in xamarin and xamarin.forms and what not
do you know if i can use XAML Styler to graphically preview an app?
Dave Grochocki
@grochocki
XAML Styler works with Xamarin, but it does not allow you to preview code, just format it nicely
rspl-nilesh
@rspl-nilesh
I am quite new for xamarin. I want to know this plugin will work in Mac Visual Studio ?
rspl-nilesh
@rspl-nilesh
@all, is anyone can help me out ?
vreniose95
@vreniose95
Hello everyone!
Oooh, fancy seeing you here @JohanLarsson
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!