AMT-Cheif
/
Stylet
mirror of https://github.com/AMT-Cheif/Stylet.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
601 Commits 7 Branches 65 Tags 4.1 MiB
Commit Graph

601 Commits

Author SHA1 Message Date
Antony Male 8a6f010fbb Add support for namespace transformations to ViewManager 2015-09-25 10:57:46 +01:00
Antony Male 3dd1ec2bfe Ensure that ViewManagerConfig properties cannot be null 2015-09-25 10:43:17 +01:00
Antony Male 000a77c4a9 Make looking up a view type slightly cheaper 2015-09-25 10:39:19 +01:00
Antony Male 7bc6a6b863 Update NuGet packages 2015-09-24 17:55:38 +01:00
Antony Male 1731f2388a Change how ViewManager is configured 
Instead of taking a reference to the Bootstrapper, it takes a configuration
object which is populated by the Bootrapper. This will pave the way for
easier views-in-multiple-assemblies handling in the near future...

This also involved some work to remove registering Stylet's assembly with
the IoC container and the ViewManager. It wasn't really necessary
anyway and just slowed things down.
 2015-09-24 17:48:40 +01:00
Antony Male 7fe21eb40b Turn s:ViewModel into a proper binding, making it vaguely useful 2015-09-24 15:43:06 +01:00
Antony Male e8d9f95dfd Remove unnecessary usings 2015-09-24 13:37:29 +01:00
Antony Male 8548df498b Tidy up commented-out code 2015-09-24 13:36:58 +01:00
Antony Male c1c8a38dfb Merge branch 'feature/bindingproxy' into develop 2015-09-24 13:09:22 +01:00
Antony Male 240f013822 Improve documentation 2015-09-24 13:08:45 +01:00
Antony Male b378027018 Introduce proper testing 2015-09-24 13:02:54 +01:00
Antony Male 4d767f0364 Refactor to add {s:ViewModel}, and use that for actions 2015-09-24 12:12:37 +01:00
Antony Male 540482a5f4 YAY IT'S WORKING 2015-09-24 12:12:36 +01:00
Antony Male f4bf876c6b Mucking about with an integration test for BindingProxy 
See also SetResourceReference and
BindingOperations.SetBinding(inputBinding, CommandProperty, new Binding("."))
 2015-09-24 12:12:35 +01:00
Antony Male a703659095 Playing around with BindingProxy 2015-09-24 12:12:34 +01:00
Antony Male fc7f164c53 Remove unnecessary usings in unit tests 2015-09-23 21:46:36 +01:00
Antony Male a321c6f94a Start screens in Deactivated, not Initial 
This means there's no further confusion around screens being deactivated
without first being activated. This is also closer to the Caliburn.Micro
model.

The Initial state used to be useful for determining the first transition
to Activated, but that turned out not to work, see recent commits.
 2015-09-23 21:45:13 +01:00
Kai Eichinger 0089029ea8 Fixed broken tests for Systems that don't use "." as decimal separator 2015-09-22 20:53:56 +02:00
Antony Male 477d30ab4e Remove 'Task.Delay(1)' from unit tests 2015-09-22 09:18:42 +01:00
Antony Male 7f14d29696 Merge branch 'release/1.1.7' into develop 2015-09-09 12:48:49 +01:00
Antony Male 4114e1cf92 Bump version 2015-09-09 12:48:29 +01:00
Antony Male 3df0beaa23 Update changelog 2015-09-09 12:48:21 +01:00
Antony Male 44cff93967 Update NuGet packages 2015-09-09 12:43:31 +01:00
Antony Male 786438dc50 Fix unit test which could crash 
We were trying to close a window on a non-STA thread after the test had
finished executing, which was evil.

Threading is hard.
 2015-09-09 12:43:26 +01:00
Antony Male 0bf916691f Change my mind on whether Deactivated can be entered before Active 
It was getting too convoluted: if something sets the state, the Screen should
enter that state
 2015-09-09 12:27:21 +01:00
Antony Male fc1198dae6 Add version task 2015-09-08 22:10:11 +01:00
Antony Male a90f1d3c2f Add ruleset 2015-09-08 22:04:12 +01:00
Antony Male c1b842342b Add NUnit VS test runner NuGet package 2015-09-08 22:03:33 +01:00
Antony Male 11d91e7323 Fix brace style 2015-09-08 22:03:19 +01:00
Antony Male af5d2f0273 Do not allow Initial -> Deactivated transition 
This caused a regression when screen states were added. Childre of
conductors are deactivated initially, then activated when the parent is
activated. This caused the Initial -> Deactivated transition. Then when
the child was activated, the 'from' state was not Initial, and so the
OnInitialActivate method was not called.

The choice to remain in Initial in this case makes sense: we don't want
to go to Deactivated (and come up with another mechanism for firing
OnInitialActivate), as that would fire OnDeactivate without there being
a corresponding OnActivate, which might mess things up.
 2015-09-08 22:03:12 +01:00
Antony Male 6ef82a580b Allow ActionExtension to be instantiated with zero parameters 2015-09-08 13:56:27 +01:00
Antony Male 5c511603b6 Fix 'Eliminate ViewManager' 2015-06-12 19:47:28 +01:00
Antony Male 3b01fac260 Move to gitlink for symbols 2015-06-02 19:49:17 +01:00
Antony Male f58d0486c0 Make 'View' static 2015-06-02 16:02:18 +01:00
Antony Male 5e412af659 Behave better if s:View.Model used on a bad container 
Fixes #6
 2015-06-02 16:01:12 +01:00
Antony Male 97192899eb Eliminate View.ViewManager 
I think that's the last step towards supporting multiple Applications
(if anyone every actually wants to do that). It's good architecture,
anyway
 2015-06-02 15:51:27 +01:00
Antony Male 9f3a7d665a Ensure View.ViewManager is set before Configure called 2015-04-05 17:46:17 +01:00
Antony Male 8479672028 Remove dependency on Application.Current from WindowManager 
This means that the WindowManager is entirely self-sufficient, and does
not rely on anything static
 2015-03-30 15:02:07 +01:00
Antony Male 25beb99dae Merge branch 'release/1.1.6' into develop 2015-03-24 09:26:15 +00:00
Antony Male 995484425f Bump version 2015-03-24 09:25:46 +00:00
Antony Male 337d947a30 Update changelog 2015-03-24 09:25:25 +00:00
Antony Male e222af3c84 Throw if the user tries to show a Window using s:View.Model 
Fixes #5
 2015-03-24 09:23:35 +00:00
Antony Male 9b27dcf3de ActionExtension assumes any delegate is an EventHandler 
This catches the case where there are events which aren't derived
from RoutedEventHandler, such as KeyDown
 2015-03-24 09:13:52 +00:00
Antony Male 01d1d21368 Merge branch 'release/1.1.5' into develop 2015-03-17 12:33:25 +00:00
Antony Male 1bb0e70691 Bump version 2015-03-17 12:30:30 +00:00
Antony Male 28aa42fa83 Update changelog 2015-03-17 12:30:03 +00:00
Antony Male 9fa749f0b7 Fix incorrect assertion 2015-03-17 12:27:57 +00:00
Antony Male 63a9c4a70f Avoid binding to IEnumerable in MessageBoxView 
According to dotMemory, this can cause a memory leak
 2015-03-17 12:27:56 +00:00
Antony Male 0e48896a6d StyletIoC: Don't use Type for the key to the builderUppers dict either 2015-03-17 12:27:56 +00:00
Antony Male a6cdca23ab StyletIoC: Optimize slightly by passing Type if available 
In some paths to some methods, we just know the RuntimeTypeHandle. In some,
we know both the Type and RuntimeTypeHandle. Optimize such that the Type
is used if available, otherwise Type.GetTypeFromHandle is used.
This should mean that StyletIoC is just as quick as it was before this
refactor.
 2015-03-17 12:27:55 +00:00