Designer

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
Designer
Monday, June 18, 2012PrintSubscribe
Working with Data Views

Data views are instances of data controllers that are placed in page containers.

The picture below shows the four data views on the Customers page, placed in two different containers.

Four views in two containers on the Customers page.

Creating a Data View

A data view can be created by activating the context menu on a container and selecting New Data View option.

New Data View context menu option on the container.

The New Data View button on the Project Explorer toolbar can also be used.

New Data View toolbar option for container.

This will open the New Data View form in the Project Designer window. Specify the controller and view. Press OK button to add the view to the container. The Id of the view will be automatically assigned, and can be changed in the Project Explorer.

New view created in container1 of My Test Page.

Moving Data Views

Data views can be moved into different locations.

Dragging a data view and dropping it onto another data view will place it after the target data view.

View2 dropped on view4 data view.     View2 moved after view4 when dropped.

Using the context menu commands Cut and Paste will also lead to the same result.

Cut context menu option for view2 data view.     Paste context menu option for a data view.

Dropping a data view on the right side of another data view will place it after the target data view.

Drop data view view3 on the right side of view2.      View3 will be placed after view2.

Dropping a data view on the left side of another data view will place it before the target data view.

Drop view2 on the left side of view3.     View2 will be placed before view 3.

Dropping a data view on a container will place the data view at the bottom of the target container. The application framework will try to assign the correct Filter Source, if it is available on the page. Otherwise, it will be cleared.

View1 dropped on container2.     View1 moved at the bottom of container2.

If CTRL key is held down when the data view is dropped on a container, the data view will be duplicated. If there is a name conflict, the new data view will be renamed. Context menu commands Copy and Paste can be used for the same purpose.

View1 ctrl dropped onto container2.     View1 duplicated as view5.

Dropping a data view on a page will move the data view into a new container at the bottom of the page.

Dropping view5 onto My Test Page.     View5 placed into a new container.

When multiple data views are dropped, they will be dropped in the order of selection. In the example below, the data views were selected in the following order: view1, view2, view3, view4, view5. The views were then dropped on container2.

All views on My Test Page selected.     All views dropped on container2.

Renaming Data Views

A data view can be renamed by activating the context menu and selecting Rename option.

image     View1 of container1 in Rename mode.

Deleting Data Views

Data views can be deleted via the context menu Delete action.

Delete context menu action for two selected data views.

Monday, June 18, 2012PrintSubscribe
Working with Containers

Containers are placed on pages in order to hold data views (instances of data controllers) and controls (instances of custom user controls), and determine the layout of elements on the page.

Here are examples of containers with various content on two different pages.

Customers page with container1 and container2.     Two containers with views on the Home page.

Creating a Container

A container can be created in a page by activating the context menu for the target page and selecting New Container option.

New Container in Customers page.

The Project Explorer toolbar also displays the New Container icon.

New Container icon on the Project Explorer toolbar.

This will open the New Container properties page in the Designer window.

The Name of the container will be automatically assigned, and can be renamed in the Project Explorer.

The Flow property determines whether the container will be placed on the next row or column on the page. If the container has a Flow of “New Row”, the standard icon will be used.

New container with Flow of 'New Row' uses the default container icon.

If the container has a Flow of “New Column”, a different icon will be displayed.

New container with Flow of 'New Column' uses special container icon.

Moving Containers

A container can be dragged to a new location.

When a container is moved or copied, all child data views and controls are moved with it as well. If there are any duplicate names, a number will be appended to the name. The application framework will attempt to identify the correct data view Filter Source for the destination.

If the container is dropped directly onto another container, then it will be moved after the target container.

Dragging container 'c101' onto container1.     Container 'c101' was dropped after container1.

One can also use the context menu to Cut a container, and then Paste it on another container. This will move it after the target container.

Cut command for container 'c101'.     Paste command on 'container1'.     Container 'c101' pasted after container1.

If a container is dropped on the right side of another container, then it will be moved after the target container.

Container 'c101' dragged after container2.     Container 'c101' dropped after container2.

If a container is dropped on the left side of another container, then it will be moved before the target container.

Container 'c101' dragged before container2.     Container 'c101' dropped before container2.

Containers can also be dropped on pages to move the container to the bottom of the hierarchy on that page. This can also be done using Cut and Paste context menu options.

Container 'c101' dropped on Orders page.     Container 'c101' placed at the end of Orders page.

If a container is dropped on another page while CTRL key is pressed, then the container will be duplicated in the target page. This can be done using Copy and Paste context menu commands.

Container 'c101' duplicated onto Customer Demo page.     Duplicate of 'c101' container placed at the end of Customer Demo page.

If multiple containers are dropped on a target, then they will be moved or copied depending on the order of selection. In the example below, the order of selection was container4, container2, and container3. The selected containers were dropped on the left side of container1. This resulted in the order: container4, container2, container3, container1.

Multiple selection dragged before container1.     Containers on Customers page reordered.

Renaming Containers

A container can be renamed by activating the context menu and selecting Rename option. The keyboard shortcut F2 will also activate Rename mode. The application framework will prevent saving a container with a duplicate name.

Context Menu 'Rename' option for container 'c101'.     Container 'c101' in renaming mode.

Deleting Containers

A container can be deleted using the Delete context menu option, or by pressing Delete on the keyboard.

Context menu 'Delete' option for container1 on Customers page.

Multiple containers can be deleted at once by making a multiple selection and pressing Delete on the keyboard.

Multiple containers deleted.

Friday, June 15, 2012PrintSubscribe
Working with Pages

The Pages tab on the Project Explorer displays a hierarchy of application elements, starting with pages. Pages are composed of containers with data views and custom user controls.

Top-level pages are pages on the first level of the hierarchy.

The examples of top-level pages are Home, Customers, Employees, Categories, Customer Demographics, and Region. The examples of child pages are Orders, Customer Demo, Order Details, Employee Territories, and Products.

The Project Explorer displays a hierarchy of pages and page elements.

Creating a Page

A top-level page is created by clicking on the New Page icon on the toolbar.

New Page icon at the top of Project Explorer window.

This will open the New Page form where page properties can be specified.

The properties Name, Index, and Path effect the creation of a page.

The Name must be a unique sequence of alphanumeric characters that start with a letter.

The Index is an optional numerical order of the page. If it is not specified, then it will be assigned automatically when the page is saved. If it is specified, then the designer will try to position the page in the requested order.

The Path determines the hierarchical location of a page, as well as reflecting the text displayed on the menu to the end user. The vertical bar character “|” is used to separate multiple levels in the hierarchy. If there is no separator, then the page will be placed at the top of the hierarchy.

Below are sample settings for a new top-level page with a specific Index and Path.

Property Value
Name MyNewPage
Index 1005
Path My New Page

The page will be placed in the specified location based on the path and index when created in the Northwind sample.

New Page with index and path placed at specified location.

Here are the properties for a new page with an existing multi-level path.

Property Value
Name MyNewPage
Path Customers | Orders | My New Page

The page will be placed in the correct location. If the Path includes separators, then any Index is ignored, and the page is placed as the last child of an existing parent.

Page created with an existing mult-level path will be placed in the correct location.

If there is no matching path, then the missing parent pages will be created.

Property Value
Name MyNewPage
Path Customer2 | Orders | My New Page

The parent pages will have a special icon, because the External URL property of the parent pages is set to “about:blank”. Such pages will not have a physical implementation in the application and will simply designate static nodes in the navigation hierarchy.

Page created with a nonexisting multilevel path will create blank pages to match the path.

If a top-level page is created without a specified Index, then the page will be placed at the bottom of the hierarchy.

Property Value
Name MyNewPage
Path My New Page

The framework will automatically handle index allocation after the page is created – it will assign the first page with Index of “1000” and auto-increment by “10” for every succeeding page.

New Page with path but without index placed at the end of the list of pages.

If a page is created without a path, then it will become a system page. This page will not appear on the menu, but can be accessed via URL. The new system page will be added at the bottom of the hierarchy with a different icon. System pages are typically used to provide utility functions in applications and are meant to be presented to users through programmatic commands.

Page created without a path will be a system page.

When a page is selected in the Project Explorer, the New Child Page option will be available on the toolbar. It can also be accessed via the context menu of the page node.

New Child Page icon on the toolbar of Project Explorer.

Selecting this option will open the New Child Page form in the Designer window with Index and Path properties unavailable.

Specifying a name and creating a child page will add the page as the last child of the parent.

Creating a child page under Customers page node.

Rearranging Pages

Moving pages in the hierarchy can be accomplished by dragging and dropping the page nodes in the Project Explorer window. Dropping a page onto another page will place it under the hierarchy of the target page.

Dragging and dropping My New Page onto Orders page node.     My New Page moved under Orders page node.

The page can be moved from one node to another with Cut and Paste commands in the context menu. Use the Cut option on the context menu, and use Paste on the target page.

Cut context menu option on My New Page node.     Paste context menu option on Orders controller.

Holding CTRL while dropping directly onto a page will duplicate the page. If the drop location already has a page with the same name, the duplicated page name will be appended with a number. This can also be done by copying the first page, and then pasting the page in another location.

My New Page being copied onto Orders page node.     My New Page duplicate page node appended with a number.

Dropping a page on the right side of a target page node will place the page after the target. The mouse cursor will indicate where the page will be placed.

My New Page dropped after Orders page node.     My New Page dropped after Orders page node.

Dropping a page on the left side of a target page node will place the page before the target.

My New Page dropped before Orders page node.     My New Page page node placed before Orders in the Project Explorer.

Dragging and dropping a page with child nodes will move the child page nodes as well. Cutting or copying a page with children will also move or copy the entire group to the new location.

Reports page node with child pages dropped on Region page node.     Reports page node moved under Region along with all child pages.

Multiple pages can be selected by holding CTRL and clicking on pages. Clicking on a page node, holding SHIFT, and clicking another page node will select a range.

Customers, Employees, Categories, and Region page nodes selected.

Any drag and drop operations will be based on the order of selection. For example, the pages below were selected in the order of Customers, Employees, Categories, Region, and dropped to the right of Home. This resulted in the pages being reordered to Home, Region, Categories, Employees, and Customers.

Several selected pages dropped after Home node.     Several selected pages dropped after Home node.

Deleting Pages

Delete a page by right-clicking on the page and selecting Delete option.

Delete option for Customer Demographics page node.

You can also select the page(s) and press Delete on your keyboard.

Multiple page deletion prompt.

Renaming Page Nodes

The context menu of page nodes offers Rename option. If the command is activated on a top-level or child page, then the selected segment of the page Path will change. If the command is activated on a system page, then the Title of the page will change. The Path of a system page is always empty.

The following example shows renaming of the Customers / Orders / My New Page page node.

My New Page with Rename context menu option.     My New Page renamed.

The keyboard shortcut F2 will activate rename command on the selected page node. 

If you need to change the physical Name of the page, then select the page and change the Name property in the Designer window.

Hiding Pages from Navigation Menu

For certain pages, it may not be necessary to place them on the navigation menu. The Include in Menu option will remove the page from the menu.

Using the 'Exclude from Menu' context menu option for 'Customer Demographics' page.      'Customer Demographics' page is now excluded from the menu.

The page is still accessible via URL.