9.3 Using Component View
This section explains how to view and edit database application pages using Component View.
9.3.1 Viewing a Page in Component View
To view a page in Component View:
-
Navigate to the Workspace home page.
-
Click the Application Builder icon.
-
Select an application.
-
Select a page.
The default view, Page Designer appears.
Tip:
If you previously viewed pages in Component View, Component View displays by default. -
On the Page Designer toolbar, click the Component View icon.
Component View appears.
You preview a page by running it. Running an application page displays the rendered version as end users would see it.
9.3.2 Editing a Page in Component View
This section explains how to edit a page in Component View.
9.3.2.1 About Using Component View
In Component View each page is divided into three sections: Page Rendering, Page Processing, and Shared Components. Each of these sections is broken into subsections with headings that identify a type of control, component, or application logic.
Description of the illustration ''cv1.png''
To edit a component, drill down on the component name or click the icon described in the following sections.
9.3.2.2 Edit All Icon
You can edit the controls, components, or logic within a given subsection by clicking the Edit All icon that displays to the right of the subsection title. The Edit All icon resembles a piece of paper with a pencil on top of it.
Description of the illustration ''cv_edit_all_ico.png''
9.3.2.3 Copy or Create Icons
You can copy or create controls or components by clicking the Copy and Create icons. The Copy icon resembles two small overlapping pages. Click the Copy icon to make a copy of an existing control or component.
Description of the illustration ''cv_copy_ico.png''
The Create icon resembles a plus (+) sign. Click the Create icon to create a control or component.
Description of the illustration ''cv_create_ico.png''
9.3.3 Understanding Page Rendering
This section describes the subsections under Page Rendering in Component View.
9.3.3.1 What Is Page Rendering?
Page rendering is the process of generating a page from the database. Developers use the Page Rendering section to modify controls that impact the rendering of a page, including page attributes, regions, buttons, items, and page processes.
9.3.3.2 Page Rendering
Table 9-1 describes the subsections under Page Rendering in Component View.
Table 9-1 Page Rendering Subsections
| Subsection | Description |
|---|---|
|
Page attributes control specific characteristics of a page such as the page name, display attributes such as the page title and the associated page template, header text, and the selected authorization scheme to name just a few. |
|
|
A region is an area on a page that serves as a container for content. Each page can have any number of regions. The content of a region is determined by the region source. For example, a region may contain a report based on a SQL query you define, or it may contain static HTML. You control the appearance of a region through a specific region template. You can use regions to group page controls (such as items or buttons). You can also create simple regions that do not generate additional HTML, or create elaborate regions that frame content within HTML tables or images. See Also: "About Regions," Oracle Database Development Guide for information about developing web applications with PL/SQL, and Oracle Database PL/SQL Packages and Types Reference for information about htp packages |
|
|
As you design your application, you can use buttons to direct users to a specific page or URL, or to enable users to submit a page. When you submit a page, the Application Express engine posts or processes information. A button implementation is determined by the button template. Buttons can be placed in predefined region template positions or among items in a form. See Also: "Creating Buttons" |
|
|
Items are HTML form elements such as text fields, select lists, and check boxes with an associated session state. Item attributes affect the display and behavior of items on a page. For example, these attributes can impact where a label displays, how large an item is, and whether the item displays next to or below the previous item. There are two categories of items: page items and application items. Page-level items are placed on a page and have associated user interface properties, such as Display As, Label, and Label Template. Application-level items are not associated with a page and therefore have no user interface properties. An application item can be used as a global variable. See Also: "Understanding Page-Level Items" and "Managing Application-Level Items" |
|
|
Processes are logic controls used to execute Data Manipulation Language (DML) or PL/SQL. For example, you can use a process to populate session state at the time a page is rendered, to execute some type of logic (for example, using PL/SQL), or to make a call to the rendering engine. Typically a process performs an action. A process may be hand coded PL/SQL, or the invocation of a predefined process. See Also: "Understanding Page Processes" and "Understanding Application Processes" |
|
|
Dynamic actions provide a way to define complex client-side behavior declaratively without the need for JavaScript. You can specify an action that is performed based on a defined set of conditions. You can also specify which elements are affected by the action and when and how they are affected. See Also: "Managing Dynamic Actions" |
9.3.4 Understanding Page Processing
This section describes the subsections under Page Processing in Component View.
9.3.4.1 What Is Page Processing?
Page processing is the process of submitting a page. A page is typically submitted when a user clicks a button. Use the Page Processing section to specify application logic such as computations, validations, processes, and branches.
9.3.4.2 Page Processing
Table 9-2 describes the subsections under Page Processing in Component View.
Table 9-2 Page Processing Subsections
| Subsection | Description |
|---|---|
|
Computations are units of logic used to assign session state to items and are executed at the time the page is processed. See Also: "Understanding Page Computations" |
|
|
Processes are logic controls used to execute Data Manipulation Language (DML) or PL/SQL. Processes are executed after the page is submitted. See Also: "Understanding Page Processes" |
|
|
Branches enable you to create logic controls that determine how the user navigates through the application. See Also: "Controlling Navigation Using Branches" and "About the When Button Pressed Attribute" |
9.3.5 Understanding Shared Components
This section describes the subsections that may display under Shared Components in Component View.
See Also:
"Managing Shared Components"9.3.5.1 What Are Shared Components?
The Shared Components section contains common elements that can display or be applied on any page within an application.
See Also:
"Managing Shared Components"9.3.5.2 Shared Components
Table 9-3 describes the subsections under Page Processing in Component View.
Table 9-3 Shared Components Subsections
| Subsection | Description |
|---|---|
|
Tabs are an effective way to navigate between pages of an application. Application Builder includes two types of tabs: standard tabs and parent tabs. An application having only one level of tabs uses a standard tab set. A standard tab set is associated with a specific page. You can use standard tabs to link users to other pages within your application. A parent tab set functions as a container to hold a group of standard tabs. Parent tabs give users another level of navigation and context (or sense of place) within the application. See Also: "Creating Tabs" |
|
|
A list of values (LOV) is a static or dynamic definition used to display a specific type of page item, such as a radio group, check box, popup list, or select list. LOVs can be static (that is, based on a set of predefined display and return values) or dynamic (based on SQL queries that select values from tables). Once created, an LOV can then be referenced by one or more page items. You define LOVs at the application level by running the LOV Wizard and adding them to the List of Values repository. See Also: "Creating Lists of Values at the Application Level" |
|
|
A breadcrumb is a hierarchical list of links that is rendered using a template. For example, you can display breadcrumbs as a list of links or as a breadcrumb path. See Also: "Creating Breadcrumbs" |
|
|
A list is a collection of links that is rendered using a template. For each list entry, you specify display text, a target URL, and other attributes that control when and how the list entry displays. You control the display of the list and the appearance of all list entries by linking the list to a template. See Also: "Creating Lists" |
|
|
A theme is a named collection of templates that defines the application user interface. Each theme contains templates for every type of application component and page control, including individual pages, regions, reports, lists, labels, menus, buttons, and list of values. See Also: "Using Themes" |
|
|
Templates control the look and feel of the pages in your application. As you create your application, you specify templates for pages, regions, reports, lists, labels, menus, buttons, and popup lists of values. Groups of templates are organized into named collections called themes. See Also: "Creating Custom Themes" |
|
|
You can provide security for your application by specifying an authorization scheme. Authorization is a broad term for controlling access to resources based on user privileges. |
|
|
Use a navigation bar to link users to various pages within an application. You can use a navigation bar to enable users to log in, log out, or link to Help text. The location of a navigation bar depends upon the associated page template. A navigation bar icon enables you to display a link from an image or text. When you create a navigation bar icon you can specify an image name, text, display sequence, and target location (a URL or page). See Also: "Creating a Navigation Bar Entry" |
9.3.6 Creating a Page Control Component View
Page controls includes items, buttons, branches, computations, processes, or validations.
To add a page control in Component View:
-
View the page in Component View. See "Viewing a Page in Component View."
-
On the Navigation bar, click the Create menu and then select Page Component.
The Create Page Component wizard appears.
-
Select one of the following:
-
Item. See "Understanding Page-Level Items."
-
Button. See "Creating Buttons."
-
Branch. See "Controlling Navigation Using Branches."
-
Computation. See "Understanding Page Computations."
-
Process. See "Understanding Page Processes."
-
Validation. See "Understanding Validations."
-
-
Follow the on-screen instructions.