Fluxtheme v1, Please give me your opinion.

[Jason]

So all the themes I see in the VB section are just custom controls? Sounds like a weird hack, you'd think there's an easier way, even with plain old Windows Forms. For XAML in WPF, is there an equivalent to style sheets? That would be absolutely tits. Excuse my ignorance, haven't looked into GUI stuff much because it never really mattered to me, but now when I show my friends my programs and they see the console they're just like "... wuts dat." so I think I need to build some design skills. :/

What do you mean "weird hack"? Microsoft have already done the heavy lifting with 99% of the existing controls (events, behaviours etc), all you need to do is derive from the existing classes and alter the appearance. Inheritance isn't a "weird hack" and method overriding isn't either. It's a lot less effort than re-inventing every single control from the ground up.

This is the kind of thing that inheritance is good for; retain 99% of the code from the parent class, alter 1% to better suit your needs.

XAML doesn't use "style sheets", but you can create named styles in your resources, and even extend on existing styles using the "BasedOn" attribute. Once you have these styles, you can apply them to your XAML elements.

A basic example of a custom border:

<Style x:Key="InteractionPanelBorder" TargetType="Border">
    <Setter Property="BorderThickness" Value="1,1,1,1" />
    <Setter Property="BorderBrush" Value="Black" />
    <Setter Property="Margin" Value="0" />
</Style>

Then you can apply it to any element which derives from "Border"

<Border Style="{StaticResource InteractionPanelBorder}">
    <!-- blah -->
</Border>

[t7ancients]

What do you mean "weird hack"? Microsoft have already done the heavy lifting with 99% of the existing controls (events, behaviours etc), all you need to do is derive from the existing classes and alter the appearance. Inheritance isn't a "weird hack" and method overriding isn't either. It's a lot less effort than re-inventing every single control from the ground up.

This is the kind of thing that inheritance is good for; retain 99% of the code from the parent class, alter 1% to better suit your needs.

XAML doesn't use "style sheets", but you can create named styles in your resources, and even extend on existing styles using the "BasedOn" attribute. Once you have these styles, you can apply them to your XAML elements.

A basic example of a custom border:

<Style x:Key="InteractionPanelBorder" TargetType="Border">
    <Setter Property="BorderThickness" Value="1,1,1,1" />
    <Setter Property="BorderBrush" Value="Black" />
    <Setter Property="Margin" Value="0" />
</Style>

Then you can apply it to any element which derives from "Border"

<Border Style="{StaticResource InteractionPanelBorder}">
    <!-- blah -->
</Border>

It just seems like a weird way to have to do things just to change the appearance of a control, that's all(I thought that their appearance could be controlled via members of their respective classes). XAML looks better to me all the time, though. It's as I said, I know next to nothing when it comes to GUI stuff, I never mess with it because it seemed the least important to me.

[AxiomFlux]

It just seems like a weird way to have to do things just to change the appearance of a control, that's all(I thought that their appearance could be controlled via members of their respective classes). XAML looks better to me all the time, though. It's as I said, I know next to nothing when it comes to GUI stuff, I never mess with it because it seemed the least important to me.

GUI is just the way you want to present your project. console is just plain and not exciting.