AMT-Cheif
/
Stylet
mirror of https://github.com/AMT-Cheif/Stylet.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
687 Commits 7 Branches 65 Tags 4.1 MiB
C# 97.9%
PowerShell 1.7%
Ruby 0.4%
Go to file
Antony Male ffb218d666 Add default FlowDirection and TextAlignment to MessageBoxViweModel 
This removes the MessageBoxOptions input to MessageBoxViewModel, and
replaces it with explicit FlowDirection and TextAlignment inputs.
I think this is fair enough - we weren't using most of the members
of MessageBoxOptions, so allowing them to be provided was misleading.

Fixes #12
 		2016-11-12 11:35:58 +00:00
Bootstrappers Fix up the Bootstrappers project 2016-07-09 12:21:02 +01:00
NuGet Recreate App.xaml if NuGet removed it 2016-04-05 10:26:00 +01:00
Samples Move to automatic nuget package restore 2016-07-09 12:15:32 +01:00
Stylet Add default FlowDirection and TextAlignment to MessageBoxViweModel 2016-11-12 11:35:58 +00:00
StyletIntegrationTests Freeze BitmapSources before returning them 2015-10-08 14:43:09 +01:00
StyletUnitTests Add default FlowDirection and TextAlignment to MessageBoxViweModel 2016-11-12 11:35:58 +00:00
.gitattributes Use powershell, and powershell only, for Stylet.Start 2016-04-04 14:48:16 +01:00
.gitignore Add rake task to generate code coverage report 2014-05-06 12:21:39 +01:00
CHANGELOG.txt Update CHANGELOG 2016-08-26 11:46:48 +01:00
LICENSE.txt Actually fill in the blanks in the license 2014-05-23 13:08:19 +01:00
README.md Fixed link to caliburn micro project 2016-05-10 22:04:31 +02:00
Rakefile Fix cover report generation 2016-01-19 11:15:35 +00:00
Stylet.sln Move to automatic nuget package restore 2016-07-09 12:15:32 +01:00
Stylet.sln.DotSettings Align style with ReSharper 2015-01-14 15:08:43 +00:00
StyletIcon.png First attempt at an icon 2014-04-19 00:17:08 +01:00
StyletIcon.svg First attempt at an icon 2014-04-19 00:17:08 +01:00

README.md

Project Icon Stylet

NuGet Build status

Introduction

Stylet is a small but powerful ViewModel-first MVVM framework for WPF, which allows you to write maintainable and extensible code in a way which is easy to test. Stylet's aims to:

  • Solve the blockers, niggles, and annoyances which hamper MVVM development without a framework, using simple but powerful concepts.
  • Be obvious to people picking up your project for the first time: there's very little magic
  • Be easy to verify/validate. The LOC count is low, and it comes with a very comprehensive test suite. The code is well-written and well-documented.
  • Be flexible while providing sensible defaults. Almost any part of the framework can be overridden if you wish, but you probably won't want to.

It is inspired by Caliburn.Micro, and shares many of its concepts, but removes most of the magic (replacing it with more powerful alternatives), and simplifies parts considerably by targeting only MVVM, WPF and .NET 4.5.

Getting Started

The quickest way to get started is to create a new WPF Application project, then install the NuGet package Stylet.Start. This will install Stylet, and set up a simple skeleton project.

See Quick Start for more details.

If you want to set up your project manually, install the Stylet package, then follow the instructions in the Quick Start.

Stylet requires .NET 4.5 (Visual Studio 2012 or higher).

Documentation

The Wiki is the documentation source. There's loads of information there - go and have a look, or start with the Quick Start.

Symbols

The source is also available when you are debugging, using GitLink. Go to Debug -> Options and Settings -> General, and make the following changes:

  • Turn off "Enable Just My Code"
  • Turn off "Enable .NET Framework source stepping". Yes, it is misleading, but if you don't, then Visual Studio will ignore your custom server order and only use its own servers.
  • Turn on "Enable source server support". You may have to OK a security warning.

See also GitLink troubleshooting.

Contributing

Contributions are always welcome. If you've got a problem or a question, raise an issue. If you've got code you want to contribute, please read the Contributing guidelines first of all. Create a feature branch off the develop branch, add your changes there, and submit it as a pull request.