radicalfx / radical.windows Goto Github PK

From @mauroservienti on March 25, 2014 20:27

Copied from original issue: RadicalFx/Radical#35

Plan

• implementation in ApplicationBoostrapper
• expose conventions for resource key generation
• support in ViewResolver

Implementation details in #130

• documentation RadicalFx/documentation#77
• Tests (how?) not worth the complexity. Review once migrated to NET Core 3 RadicalFx/housekeeping#72

From @mauroservienti on April 21, 2016 9:2

Something like:

var conventions = s.GetService(typeof(IConventionsHandler));
this.Resources.Add("ConventionsHandler", conventions);

on boot completed

Copied from original issue: RadicalFx/housekeeping#58

Once property value change detection is in place we can enhance the commands (DelegateCommand and AutoCommandBinding features) to benefit from it.

As an opt-in behavior being able to detect if a property value is really changed can improve the already awesome memento experience.

Allows to control the scroll position based on a element in the VM

Similar to #24

From @fabiocbr75 on September 15, 2015 19:15

With AutoCommandBinding the viewmodel is very clean but I don't found how is possibile convert following code in AutoCommandBinding way.

XXXCommand = DelegateCommand.Create()
.OnExecute(o => MyFunc())
.OnCanExecute(o => CanRun)
.AddMonitor(PropertyObserver.For(this).Observe(v => v.prp1))
.AddMonitor(PropertyObserver.For(this).Observe(v => v.prp2))
.AddMonitor(NotifyCollectionChangedMonitor.For(this.MyObservableCollection));

Is it possible?

Thanks

Copied from original issue: RadicalFx/Radical#190

From @mauroservienti on April 1, 2015 14:47

Actually we have a ShouldReleaseView conventions that is only used by the UI Composition engine, I think that internally the ViewReleaseHandler should call ShouldReleaseView before moving on if the ViewReleaseBehavior is not ViewReleaseBehavior.Force

Copied from original issue: RadicalFx/Radical#135

From @mauroservienti on March 26, 2014 10:19

Copied from original issue: RadicalFx/Radical#48

From @mauroservienti on November 4, 2014 8:1

Add an error summary control that can automatically render the errors collection exposed by the validation engine.

Copied from original issue: RadicalFx/Radical#101

It does not work correctly in some cases changing the property in the ViewModel

e.g. track mouse position, handy when dealing with design surfaces

Provide an async version of the following:

• IExpectViewLoadedCallback;
• IExpectViewActivatedCallback;
• IExpectViewShownCallback;
• IExpectViewClosingCallback;
• IExpectViewClosedCallback;

Add the ability to decorate a VM with a ExposeViewModelAsStaticResourceAttribute to trigger the convention.

• Implemntation #311
• Documentation RadicalFx/documentation#150

Investigate if there is any way and what is the effort to allow AutoCommandBinding to support RelativeSource

From @mauroservienti on March 26, 2014 10:13

Add a new behavior to auto generate listview/gridview columns based on the ITypedList implementation od the DataSource if any.

Copied from original issue: RadicalFx/Radical#42

From @mauroservienti on March 26, 2014 10:12

verificare lo stato della griglia del fx 4.0. Quando hai 2 colonne in FillMode fare in modo che al resize di una l'altra continui a stare in "fill", in generale è necessario migliorare l'experience dell "FillMode", ad esempio facendo si che si adegui al contenuto dell'header o delle colonne.

Copied from original issue: RadicalFx/Radical#41

We now have a WindowManager that works with attached properties, would be interesting to share the same behavior with the WindowControlBoxBehavior

• merge #51
• fix nuget command line dependency in CI 592ba20
• Update dependencies to latest stable
• Update nuspect to reflect new dependencies and SemVer

From @mauroservienti on March 12, 2015 8:11

Allow the user to bind a list to collection specifying a filter expression so that bound items are filtered given the user expression

Copied from original issue: RadicalFx/Radical#125

Whenever the user wants to show a view, modal or not, a variation of the following code needs to be used:

class OpenMyAmazingViewMessageHandler : AbstractMessageHandler<OpenMyAmazingViewMessage>, INeedSafeSubscription
{
   readonly IViewResolver viewResolver;
   readonly IConventionsHandler conventions;

   public OpenMyAmazingViewMessageHandler(IViewResolver viewResolver, IConventionsHandler conventions)
   {
       this.viewResolver = viewResolver;
       this.conventions = conventions;
   }

   public override void Handle(object sender, OpenMyAmazingViewMessage message)
   {
       var view = viewResolver.GetView<MyAmazingView, MyAmazingViewModel>(vm => 
       {
          //init code here
       });

       view.Owner = this.conventions.GetViewOfViewModel(sender) as Window;
       view.ShowDialog();
   }
}

One thing Radical could do is to introduce a ShowViewMessage class such as:

class ShowViewMessage
{
   public Type ViewType{ get; set; }
   public bool AsModal{ get; set; }
}

and a generic handler, similar to the above one that handles the logic to show the requested view, what the above misses is the ability to add custom initialization data that can be passed to the VM. One thing that we could introduce is something similar to RadicalFx/Radical.Windows.Presentation#5 or we can add an interface to the VM such as ICanBeInitialized<T> and add another message such as:

class ShowViewMessage<T> : ShowViewMessage
{
   public T Data{ get; set; }
}

with this in place opening a View would be as simple as:

await broker.DispatchAsync( this, new ShowViewMessage<MyInitData>()
{
   ViewType = typeof( MyAmazingView ),
   Data = new MyInitData()
   {
      //....
   }
} );

and at the same time implement ICanBeInitialized<MyInitData> on the VM.

@micdenny thoughts?

From @mauroservienti on November 4, 2014 8:9

Hints are an amazing way to help the user to understand what to do and to document the application. We currently support CueBanners via an attached property and a behavior.
We should also support a way to automatically show documentation, beside of each control, rendering for example a "?" that when clicked will popup a list of hints/suggestions statically known or bound to the view model.

Copied from original issue: RadicalFx/Radical#103

Currently the VisualTreeCrawler has the ability to find a single child. A nice addition could be to enable the user to find all the children given the type and a condition.

When using the IViewResolver the user can inject an interceptor action that will be invoked before the ViewModel is wired to the View to manipulate the ViewModel.

When dealing with singleton ViewModels the above interceptor will be invoked only the first time, then is ignored. We should log a warning ⚠️:

Copied from original issue: RadicalFx/Radical#175

From @mauroservienti on March 26, 2014 10:36

Copied from original issue: RadicalFx/Radical#54

When using a touch enabled device controls such as ListView have the elastic behavior when scrolling and reaching the end or the top of the scroll area. This behavior allows the user to disable the elastic behavior.

class DisableManipulationBoundaryFeedback : Behavior<ListBox>
    {
        protected override void OnAttached()
        {
            base.OnAttached();
            this.AssociatedObject.ManipulationBoundaryFeedback += listBox_ManipulationBoundaryFeedback;
        }

        void listBox_ManipulationBoundaryFeedback(object sender, System.Windows.Input.ManipulationBoundaryFeedbackEventArgs e)
        {
            e.Handled = true;
        }

        protected override void OnDetaching()
        {
            base.OnDetaching();
            this.AssociatedObject.ManipulationBoundaryFeedback -= listBox_ManipulationBoundaryFeedback;

        }
    }

EditorBinding and CommandBinding

We have a bunch of features to release and I started to think that the build failures we are facing might be due to the actual Radical.Windows package

• code
• doco

Similar to #24

From @mauroservienti on May 30, 2015 9:21

Starts from the assumption that the incoming content needs to be wrapped in a TabItem.

Copied from original issue: RadicalFx/Radical#162

From @mauroservienti on May 25, 2015 9:55

Can depend on RadicalFx/Radical#154

• implementation
• doco

Copied from original issue: RadicalFx/Radical#151

From @mauroservienti on November 4, 2014 8:6

Add a behavior that shows all the errors related to a control on the UI.
Currently WPF has the notion of error template, the default template renders only one error at a time, since in the real world each control, bound to a property, can have multiple errors at the same time we and we support it we should provide a built-in way to show all the errors

Copied from original issue: RadicalFx/Radical#102

From @mauroservienti on May 25, 2015 11:25

AutoCommandBinding binds the CanExecute logic to a Boolean property whose name is the same as the command name with a Can prefix. Using a property prevents the command to pass parameters and context to the CanExecute logic.
We need to support methods as well, such as bool CanSomeCommand( Object optionalArgument ).

Copied from original issue: RadicalFx/Radical#154

A Region is a WPF MarkupExtension, thus it's instance is created and managed by WPF, there are scenarios in which it could be interesting to enable regions to have dependencies coming from other sources, such the IoC container. We have no control on regions creation however we have full control on region registration and shutdown via the RegionManager.
The RegionManager could be evolved to allow injection of callbacks so that a third party can add custom behaviors when a region is registered and when a region is shutdown. Would be interesting to:

• Expose 3 events: RegionRegistered, Shutdown and RegionShutdown
• Broadcast the same events using MessageBroker messages

Replace the EventArgs with a

public class ValidationStatusChangedEventArgs : EventArgs
{
    public ValidationStatusChangedEventArgs( string ruleSet, string propertyName )
    {
        this.RuleSet = ruleSet;
        this.PropertyName = propertyName;
    }

    public ValidationStatusChangedEventArgs( string ruleSet )
    {
        this.RuleSet = ruleSet;
    }

    public string RuleSet { get; private set; }
    public string PropertyName { get; private set; }
}

Related to RadicalFx/Radical#178

From @mauroservienti on November 17, 2014 13:58

Introduce a convention to allow anonymous initializers on ViewModel(s) when retrieving the View:

GetView(new { CompanyId = xxx, CreationDate = yyy } )

viewModel.Initialize(String companyId=null, String creationDate = "Today");

• It should work as MVC Model Binding works for actions on controllers

Copied from original issue: RadicalFx/Radical#106

From @mauroservienti on March 26, 2014 10:20

"public void Do() // Call when not passing CommandParameter
{
// do something
}
public void Do(decimal parameter) // Call when passing CommandParameter
{
// do something
}"

Copied from original issue: RadicalFx/Radical#49

Extend the WindowControlBoxBehavior to allow to control the Window icon visibility

Bounds the scroll viewer position

• implement new convention and default one #183
• documentation RadicalFx/documentation#76
• Tests (how?)

The conventions design in RadicalFx/Radical.Windows.Presentation#24 is wrong. The thing a user might need to change more frequently is not how to expose the VM as a resource but which key to use for the resource.
Actually the only way to do it is to override the ExposeViewModelAsStaticResource conventions and replace other than the resource key the whole logic to expose the VM.

This is useless, IMO. We should at first allow users to have a ViewModelStaticResourceKeySelector convention.

We have the Observer/Monitor concept to connect sources of changes, mostly, to commands.

Could be interesting to add support for Reactive Extensions' Observer/Observable concepts greatly increasing options for end users.

From @mauroservienti on March 20, 2014 7:32

Since we support IExpectViewClosingCallback w/ CancelEventArgs even for views managed by the UI Composition system (RegionService) it means that a view can block the close process, but currently this view must be the root view that we are explicetly closing because the "closing" state is not notified to nested views, only the closed and dispose.
In orther to achieve that a 2-phase closing process must be introduced, the first stage is to ask to all the view chan, in that specific scope, if they agree to be closed, and if "true" proceed with the closing process otherwise block everything.

How does this interacts with the application shutdown process?

Copied from original issue: RadicalFx/Radical#1

Copied from original issue: RadicalFx/Radical#150