MDrivenWiki
Log in

WECPOF Goodies

From MDrivenWiki

WECPOF Goodies 1

When doing search UI’s with multiple search expressions like this:

WECPOF Goodies - 1.png

The used search expression is deduced from the rules explained here: The multi variable seeker

But having that is all fine – we need a way to tell the user what to expect from the search – ie it is often so that one search expression is associated with a specific column in search result and users have indicated that it is important to understand what the search logic has done.

So we added a tagged value on the SearchExpressions:  Eco.HiliteGridColumn , and you are supposed to set this to the value NameOfViewModelClassThatIsTheSearchResult.NameOfTheColumnToHiliteWhenThisParticularSearchExpressionIsInEffect.

If you do it may look like this:

SearchExpression TaggedValue Eco.HiliteGridColumn=SearchResultGrid.Efternamn

SearchExpression2 TaggedValue Eco.HiliteGridColumn=SearchResultGrid.Förnamn

And when you search in WECPOF:

WECPOF Goodies - 2.png

And another click (that moves the search to the other expression):

WECPOF Goodies - 3.png

WECPOF Goodies 2–GridAction

It is real easy to create an action that creates objects – but the result is not always very user friendly. It is not friendly to force the user to first hit a button to create a new row in a grid – then move to the new row to enter the text.

We made an effort to solve this issue in a generic way. We call the solution GridAction.

Example

Given this model

WECPOF goodies - 6.png

And this view model

WECPOF goodies - 7.png

You can get this WECPOF UI

WECPOF goodies - 8.png

Now we can very well require that the user first press the action “Create Class1” and then navigate to the new row and enters Attribut1.

But by adding an Action to the Nesting in Viewmodel that the Grid displays we get another way of doing it – the GridAction way:

WECPOF goodies - 9.png

By doing this – WECPOF adds a null row at the bottom of the lines in our grid:

WECPOF goodies - 10.png

The null row has the Action name on it – written in italic to separate it from normal rows (representing Class1 objects in this case).

User can write into the GridActionRow, and when user press enter or otherwise submit the edit this will happen:

  1. A ViewModel context variable called vGridActionArgument will be assigned the text you wrote
  2. The action will execute

So consider this implementation of the GridAction_NewClass1 action:

let x=Class1.Create in

(

  x.Attribute1:=vGridActionArgument

)

This will create a new Class1 object and assign the Attribute1 to the value entered in the GridActionRow:

WECPOF goodies - 11.png

The user experience is a lot better!

In the Class2 grid – that in this ViewModelView is a detail of the Class1 master – the GridAction expression looks like this:

let x=Class2.Create in

(

  x.Name:=vGridActionArgument;

  x.Class1:=vCurrent_AllInstances

)

So it both gets the new name and assigns to the correct Class1 owner – and the user just typed the name in the last row and pressed enter.

Further more…

If you make use of multi variable seekers – it is desirable to let the GridActionArgument in some grid act as the search expression.

So if you have a UI that enables you to add tenants to houses:

WECPOF goodies - 12.png

You want to user to be able to search and add in one blow – add a GridAction that is defined as this:

WECPOF goodies - 13.png

And the Search UI:

WECPOF goodies - 14.png

Now – when the user types and press enter this will happen:
1. vGridActionArgument gets the typed value
2. The action is executed
3. The action is defined to bring up the Seeker for Person
4. The vSeekParam that is used as filter will be set by the actions OnShow expression
5. WECPOF MAGIC will detect that this is a seeker and press enter – thus starting the search
6. If the result of the search is 1 exactly 1 then WECPOF MAGIC will recognize this as a good result and execute the After Modal Ok expression and thus closing the search UI and also assigning the tenant.
7. If the search result was different than 1 (zero or many but not 1) the search UI will stay open – so that the user can find some other criteria
WECPOF goodies - 15.png

Search result:

WECPOF goodies - 16.png

So the result was 2 rows – the search stays open…

WECPOF goodies - 17.png

Only 1 hit so everything is done for me:

WECPOF goodies - 18.png

WECPOF Goodies 3 Special viewmodel names

There are currently two ViewModel names that has special meaning to WECPOF. The first is “DropTargetViewModel” this is added to the WECPOF screen

WECPOF goodies - 4.png

This is good for things you always want to show or as a scratchpad where you can drag objects (see article about DragDropActions).

The second special name is “DefaultBackgroundViewModel” and that viewmodel is added here:

WECPOF goodies - 5.png

And this will show whenever you do not have any tabs open. This is good for information you want to present to the user when they start the application. Like maybe you want an easy navigation screen, or a message from SysAdmin about something, or a list of things with broken constraints.