User Interface

Labels
AJAX(112) App Studio(9) Apple(1) Application Builder(245) Application Factory(207) ASP.NET(95) ASP.NET 3.5(45) ASP.NET Code Generator(72) ASP.NET Membership(28) Azure(18) Barcode(2) Barcodes(3) BLOB(18) Business Rules(1) Business Rules/Logic(140) BYOD(13) Caching(2) Calendar(5) Charts(29) Cloud(14) Cloud On Time(2) Cloud On Time for Windows 7(2) Code Generator(54) Collaboration(11) command line(1) Conflict Detection(1) Content Management System(12) COT Tools for Excel(26) CRUD(1) Custom Actions(1) Data Aquarium Framework(122) Data Sheet(9) Data Sources(22) Database Lookups(50) Deployment(22) Designer(178) Device(1) DotNetNuke(12) EASE(20) Email(6) Features(101) Firebird(1) Form Builder(14) Globalization and Localization(6) How To(1) Hypermedia(2) Inline Editing(1) Installation(5) JavaScript(20) Kiosk(1) Low Code(3) Mac(1) Many-To-Many(4) Maps(6) Master/Detail(36) Microservices(4) Mobile(63) Mode Builder(3) Model Builder(3) MySQL(10) Native Apps(5) News(18) OAuth(9) OAuth Scopes(1) OAuth2(13) Offline(20) Offline Apps(4) Offline Sync(5) Oracle(11) PKCE(2) Postgre SQL(1) PostgreSQL(2) PWA(2) QR codes(2) Rapid Application Development(5) Reading Pane(2) Release Notes(184) Reports(48) REST(29) RESTful(29) RESTful Workshop(15) RFID tags(1) SaaS(7) Security(81) SharePoint(12) SPA(6) SQL Anywhere(3) SQL Server(26) SSO(1) Stored Procedure(4) Teamwork(15) Tips and Tricks(87) Tools for Excel(3) Touch UI(93) Transactions(5) Tutorials(183) Universal Windows Platform(3) User Interface(338) Video Tutorial(37) Web 2.0(100) Web App Generator(101) Web Application Generator(607) Web Form Builder(40) Web.Config(9) Workflow(28)
Archive
Blog
User Interface
Sunday, March 31, 2013PrintSubscribe
Auto Hide Data Views

The Auto Hide property is used to hide child data views or containers when a master record has not been selected.

Self

Let’s create a page that will contain two data views: Customers and Orders. The orders will be filtered by the selected customer.

Start the Project Designer. In the Project Explorer toolbar, click on the New Page icon.

Creating a new page.

Assign a name to the page.

Property Value
Name Auto Hide Test

Press OK to save the page. In the Project Explorer, drop the new page node on the right side of Home node to place it second in the menu.

Moving Auto Hide Test page.

Switch to the Controllers tab. Hold down Ctrl key, and click on Customers and Orders data controller nodes. Right-click, and press Copy.

Copying Customers and Orders data controller nodes.

Switch back to the Pages tab. Right-click on Auto Hide Test page, and press Paste. The controllers will be instantiated as data views in individual containers.

Pasting onto 'Auto Hide Test' page.     Two data views instantiated from the pasted data controllers.

Double-click on Auto Hide Test / c102 / view2 (Orders) node. Make the following changes:

Property Value
View grid1
Filter Source view1
Filter Field #1 CustomerID
Auto Hide Self

Press OK to save. On the toolbar, press Browse.

Navigate to the Auto Hide Test page. Note that only a list of customers is visible on the page.

Only master data views is visible on the page.

When a customer is selected, the filtered list of orders is displayed underneath.

When master record is selected, the child view is displayed.

Container

When there are multiple child data views in a single container or tabs, it is advisable to hide the whole container instead.

In the Project Explorer, double-click on Auto Hide Test / c102 / view2 (Orders, grid1) –> view1 node.

Node view1 in container c102 of page Auto Hide Test.

Change the following values:

Property New Value
Activator Tab
Text Orders

Save the data view. Browse the web app – notice that the tab element is not hidden when no customer is selected.

The tab element is not hidden.

The data view will appear when a master record is selected.

Data view is shown when master record is selected.

Switch back to the Project Designer, and change Auto Hide to “Container”.

Property New Value
Auto Hide Container

Press OK to save, and press Browse. The tab element will now be hidden.

Tab element is now hidden.

Note that if the master view is in the same container as the child view, an Auto Hide of “Container” will hide both views.

Thursday, February 28, 2013PrintSubscribe
“Freezing” Data Fields

A common practice in data sheets is to “freeze” a column so that essential information is always displayed for each row. The second generation data sheet allows both freezing columns at run-time, as well as configuring a column to be frozen at design-time.

Freezing at Run-Time

Create a sample Northwind web application. Browse the site, and navigate to the Order Details page. On the action bar, press Actions | Show in Data Sheet.

Changing the grid view to data sheet view.

Activate the column header dropdown for Product Name, and press Freeze.

Activating 'Freeze' option for Product Name column.

All columns up to the frozen column will change color. When the data sheet is scrolled to the right, the frozen columns will continue to be displayed.

Frozen columns 'Order Customer#' and 'Product Name' continue to be displayed when the data sheet is scrolled to the right.

Columns can be added or removed from the freeze by activating the Freeze option for that column. You may unfreeze the column by activating the column header dropdown and pressing Unfreeze.

Unfreezing the Product Name column.

Freezing at Design-Time

Start the Project Designer. In the Project Explorer, double-click on Customers / Order Details / container1 / view1 (OrderDetails, grid1) / grid1 / ProductID –> ProductProductName data field node.

Data field 'ProductID' of view 'grid1'.

Assign a tag.

Property New Value
Tags data-sheet-freeze

Press OK to save the field. On the toolbar, press Browse. On the action bar, press Actions | Show in Data Sheet.

Changing the grid view to data sheet view.

When the data sheet loads, the Product Name column will be frozen by default.

The column 'Product Name' is frozen by default.

The frozen columns can still be changed by the user using the method described in the previous section.

Thursday, February 21, 2013PrintSubscribe
Action “When View” Property

The “When View” property allows controlling the visibility of an action based on the current view.

For example, let’s create a custom action that will display the extended price of an order detail. This action will be available on editForm1 and grid1 by default. Let’s prevent the action from being displayed on grid1 by using When View property.

Creating the Action and Business Rule

Start the Project Designer. In the Project Explorer, switch to the Controllers tab. Right-click on OrderDetails / Actions / ag3 (ActionBar) – New node, and press New Action.

Creating a new action in action group 'ag3'.

Assign the following values.

Property Value
Command Name Custom
Command Argument ShowExtendedPrice
Header Text Extended Price

Press OK to save. Right-click on OrderDetails / Business Rules node, and press New Business Rule.

Creating a new business rule in OrderDetails controller.

Use the following configuration:

Property Value
Type JavaScript
Command Name Custom
Command Argument ShowExtendedPrice
Phase Execute
Script
var extendedPrice = [UnitPrice] * (1 - [Discount]) * [Quantity];
alert(String.localeFormat('{0:c}', extendedPrice));

Press OK to save.

On the toolbar, press Browse. Navigate to the Order Details page. The Extended Price button will be present on the action bar. When you select a row and activate the button, the extended price will be displayed in an alert.

Extended Price action available on view 'grid1'.

Select a record – the action will also be available on editForm1.

Extended Price action available on view 'editForm1'.

Note that the action is not available on createForm1. This is because the When Last Command Name property of the action is blank (which is equivalent to “Select”). View createForm1 is activated by triggering the “New” action, resulting in the Extended Price action being hidden.

Specifying “When View”

Let’s restrict display of the Extended Price action to editForm1 using the When View property.

In the Project Explorer, double-click on OrderDetails / Actions / ag3 (ActionBar) – New / a100 – Custom, ShowExtendedPrice | Extended Price action node.

Extended Price action in the Project Explorer.

Change the When View property:

Property New Value
When View editForm1

Press OK to save.

Viewing the Results

On the toolbar, press Browse. Navigate to the Order Details page. Note that the action is no longer displayed in grid1.

Extended Price action not displayed in view 'grid1'.

Select a record. The action will be available in editForm1.

Extended Price action displayed in view 'editForm1'.

Continue to Custom Filter Panel