Make XAML style writing more like CSS

Make XAML style writing more like CSS

1. Less code
2. Be more logical
3. Easier to read

I don’t know if future versions have that design in mind Let’s say I want a button with rounded corners

// version now

<Window.Resources>
      <Style x:Key="Btn" TargetType="Button">
          <Setter Property="Template">
              <Setter.Value>
                  <ControlTemplate TargetType="Button">
                      <Border BorderThickness="1" Width="60" Height="32" CornerRadius="3" Background="#4C5EE9">
                          <ContentPresenter Content="{TemplateBinding Content}" HorizontalAlignment="Center" VerticalAlignment="Center" />
                      </Border>
                  </ControlTemplate>
              </Setter.Value>
          </Setter>
          <Setter Property="Foreground" Value="#fff"></Setter>
      </Style>
  </Window.Resources>

  <Button Style="{StaticResource Btn}" Content="Button"></Button>

// expect version 1

   <Style x:Key="Btn" TargetType="Button">
         Width=60,
         Height=32,
         Background="#4C5EE9",
         Foreground="#FFF",
         BorderRadius=3
   </Style>
   <Button Style="{StaticResource Btn}" Content="Button"></Button>

// expect version 2

   <Style>
       Btn {
         Width:60,
         Height:32,
         Background:"#4C5EE9",
         Color:"#FFF",
         BorderRadius: 3
       }
   </Style>
   <Button Style="{StaticResource Btn}" Content="Button"></Button>
    OR
   <Button Class="{Btn}" Content="Button"></Button>

[mandalorianbob]

You’re kind of comparing apples to oranges here. Based on your “Expect version 1” your first style should look like this:

<Style x:Key="Btn" TargetType="Button">
    <Setter Property="Width" Value="60" />
    <Setter Property="Height" Value="32" />
    <Setter Property="Background" Value="#4C5EE9" />
    <Setter Property="Foreground" Value="#FFF" />
    <Setter Property="BorderRadius" Value="3" />
</Style>
<Button Style="{StaticResource Btn}" Content="Button" />

Now that’s not really that bad.

(For what it’s worth, it would be great if <Setter Property="Width" Value="60" /> could instead be <Width>60</Width> but I understand that XAML doesn’t work that way at all at the moment. However, I think that’s an interesting notion - could an object (like Setter) be instead replaced by a tag that isn’t itself an object but is instead just parameters? That’d be neat.)

Of course, BorderRadius isn’t a property of Button. But what I suspect you’re doing is you’re trying to say “Look at all the stuff you have to do to change a template” but then what you show as “expected” does not look like it could result in a changed template.

So kind of not really comparing fairly. Again, apples to oranges.

But for sure, when you do have to create a new Template, it gets very verbose. If you wanna propose something that would make it less so, I think you would need to show something that looks like it could actually create a template.

Also, I don’t wanna exactly, you know, go all “language wars” or anything, but in my opinion: CSS is verbose. CSS is illogical. CSS is hard to read. But I’m not talking about “Color: Red” - I’m talking about when you have to write multiple nearly identical classes for lack of inheritance with -vendor-specific-tags whose values are like “split-inline-float” and you’ve got “clear: both” and !important randomly sprinkled throughout. I feel like CSS is an absolute nightmare once you move at all past the basics. So … you know, there’s that haha. I mean if you like CSS good on ya, but not everyone necessarily thinks it’s awesome.

[xzbaijj]

css and html are very Bad language！Because they are not rigorous