This document discusses windows and content canvases in Forms Builder. It describes windows as containers that display content canvases, which are surfaces that hold visual objects. It explains how to create new windows and canvases, set their properties, display a form module across multiple windows and canvases, and use windows and canvases to modularize form contents.
This document discusses supplementing the functionality of items in Oracle Forms applications using triggers and built-in functions. It describes various item interaction triggers that can be used with different item types. It also explains how to use built-in functions to populate lists, images, trees, and interact with JavaBeans from triggers. Common tasks covered include checking checkboxes, loading images, creating hierarchical trees, and registering beans. The document provides examples of triggers and built-ins for different form interaction scenarios.
WebUtil is a utility that enables Forms developers to interact with client machines from PL/SQL code. It provides functions for opening file dialogs, reading/writing files, executing OS commands, performing OLE automation, and obtaining client info. To use WebUtil, developers attach its library and subclass its object group, then can call functions after the form starts to interact with the client, such as opening a file dialog, reading an image into the form, or creating/opening a file on the client.
This document discusses various methods for reusing objects and code in Oracle Forms applications, including property classes, object groups, copying and subclassing objects, object libraries, SmartClasses, and reusing PL/SQL code through triggers, program units, and libraries. Property classes allow inheriting properties, object groups make related objects easy to reuse, and object libraries and SmartClasses simplify sharing reusable components. PL/SQL code can be reused by copying, subclassing, defining program units, or creating libraries.
This document discusses creating and modifying master-detail forms in Dynamics 365 Business Central. It covers creating relationships between data blocks, running a master-detail form with automatic linking and deletion rules, and modifying data blocks and their layouts using wizards in reentrant mode. The key points are that relationships can be set up manually or with a wizard, forms can be run with default coordination properties, and data blocks and layouts can be customized manually or with wizards in a non-destructive way.
Grid computing uses low-cost servers and modular storage to balance workloads and provide capacity on demand. Oracle's grid products include the Oracle Database, Application Server, and Enterprise Manager. Oracle Application Server provides services for building and deploying web applications. The Oracle Developer Suite includes tools for application development and business intelligence such as Forms Developer and Reports. Forms Services allows deployment of Forms applications to a web environment.
Define triggers
Identify the different trigger categories
Plan the type and scope of triggers in a form
Describe the properties that affect the behavior of a trigger
This document discusses how to create a basic form module in Oracle Forms. It covers creating an empty module, adding a data block using the Data Block Wizard and Layout Wizard, saving and compiling the form module, different file formats for storing modules, and deploying a form module to the application server. The key steps are to create an empty module, add a data block with the wizard, save and compile the form, move the files to the application server, and generate the module to run it in the browser.
This document discusses supplementing the functionality of items in Oracle Forms applications using triggers and built-in functions. It describes various item interaction triggers that can be used with different item types. It also explains how to use built-in functions to populate lists, images, trees, and interact with JavaBeans from triggers. Common tasks covered include checking checkboxes, loading images, creating hierarchical trees, and registering beans. The document provides examples of triggers and built-ins for different form interaction scenarios.
WebUtil is a utility that enables Forms developers to interact with client machines from PL/SQL code. It provides functions for opening file dialogs, reading/writing files, executing OS commands, performing OLE automation, and obtaining client info. To use WebUtil, developers attach its library and subclass its object group, then can call functions after the form starts to interact with the client, such as opening a file dialog, reading an image into the form, or creating/opening a file on the client.
This document discusses various methods for reusing objects and code in Oracle Forms applications, including property classes, object groups, copying and subclassing objects, object libraries, SmartClasses, and reusing PL/SQL code through triggers, program units, and libraries. Property classes allow inheriting properties, object groups make related objects easy to reuse, and object libraries and SmartClasses simplify sharing reusable components. PL/SQL code can be reused by copying, subclassing, defining program units, or creating libraries.
This document discusses creating and modifying master-detail forms in Dynamics 365 Business Central. It covers creating relationships between data blocks, running a master-detail form with automatic linking and deletion rules, and modifying data blocks and their layouts using wizards in reentrant mode. The key points are that relationships can be set up manually or with a wizard, forms can be run with default coordination properties, and data blocks and layouts can be customized manually or with wizards in a non-destructive way.
Grid computing uses low-cost servers and modular storage to balance workloads and provide capacity on demand. Oracle's grid products include the Oracle Database, Application Server, and Enterprise Manager. Oracle Application Server provides services for building and deploying web applications. The Oracle Developer Suite includes tools for application development and business intelligence such as Forms Developer and Reports. Forms Services allows deployment of Forms applications to a web environment.
Define triggers
Identify the different trigger categories
Plan the type and scope of triggers in a form
Describe the properties that affect the behavior of a trigger
This document discusses how to create a basic form module in Oracle Forms. It covers creating an empty module, adding a data block using the Data Block Wizard and Layout Wizard, saving and compiling the form module, different file formats for storing modules, and deploying a form module to the application server. The key steps are to create an empty module, add a data block with the wizard, save and compile the form, move the files to the application server, and generate the module to run it in the browser.
Non-input items that can be created include display items, image items, buttons, calculated items, hierarchical tree items, and bean area items. Display items and image items show information without input, buttons initiate actions, calculated items use formulas or summaries, tree items show hierarchical data, and bean areas execute Java code. These item types are created by changing an existing item's type or using tools in the Layout Editor and setting properties specific to each item type.
This document discusses writing flexible code that is reusable, generic, and avoids hard-coded object names to make maintenance easier. It describes using system variables to reference the current context and status. Built-in subprograms like GET_ and SET_ can retrieve and set properties of objects. Objects can be referenced by internal ID found using functions like FIND_, or indirectly using COPY and NAME_IN to pass values without hard-coding names. Flexible code is more efficient and reusable across applications.
This document discusses working with data blocks and frames in Oracle Forms. It covers identifying components of the Property Palette, managing object properties, creating and using Visual Attributes, controlling data block and frame properties, and creating and deleting data blocks. The key topics covered are using the Property Palette to modify object properties, setting properties to control data block behavior and appearance, setting frame properties, and creating and deleting data blocks.
Working in the Forms Developer Environment provides an overview of key concepts for navigating and customizing the Forms Builder interface. It describes Forms Builder components like the Object Navigator, Property Palette, and Layout Editor. It also covers setting environment variables for design and run time, running a form from Forms Builder, and using the online help facilities. The document aims to help users describe Forms Builder components, navigate the interface, identify main form objects, customize Forms Builder sessions, and identify main Forms executables.
This document discusses navigation in forms. It distinguishes between internal and external navigation, and describes how to control navigation with properties of the form, block, and item. It explains navigation triggers that fire during or after navigation, and navigation built-ins that can be used in triggers except those that fire during navigation. These include GO_FORM, GO_BLOCK, GO_RECORD, GO_ITEM, NEXT_BLOCK, and others. The document also provides examples of setting properties and using triggers and built-ins to control navigation flow.
This document provides an overview of LOVs (lists of values) and editors in Oracle Forms and describes how to create them. LOVs allow selecting a value for a text item from a dynamic list, and are created from a database query. Editors override the default editor for a text item and allow customizing the editing window. The document explains that LOVs are easiest to design using the LOV Wizard, which guides selecting columns and properties. Editors are created in the Object Navigator and associated with a text item's properties. Practice questions at the end involve creating an LOV attached to a text item and an Editor attached to another item.
This document describes how to run a Forms application using Oracle Application Server Containers for J2EE (OC4J). It explains that OC4J is used to run Forms applications on the development machine and test them in a web browser. When running a form, the Forms Client applet displays in the browser while the Forms Listener Servlet and Runtime Engine handle processing on the application server. Users can navigate forms and query, insert, update, and delete records in different operation modes.
The document discusses different types of canvases in Oracle Forms including stacked, toolbar, and tab canvases. It describes how stacked canvases overlay content canvases, toolbar canvases provide standard buttons and elements, and tab canvases organize information across pages. It provides instructions for creating these canvases, setting their properties, and placing items on tab pages.
The document discusses debugging triggers in Oracle Forms Builder. It describes the components of the Debug Console used for debugging, including the stack, variables, watch, form values, PL/SQL packages, and breakpoints panels. It explains how to run a form in debug mode, set breakpoints in client and stored code, step through code, and view variable values while debugging.
This document discusses run-time messages and alerts in Oracle Forms. It describes how Forms displays messages to inform users of events, and how to control message severity and suppress messages. There are different types of messages - informative, error, working, and application. It also discusses handling run-time errors of built-in subprograms, and using triggers to intercept system messages. The document covers setting properties of alerts, and controlling alerts with built-in functions. Finally, it discusses trapping database server errors using built-ins or exceptions.
The document provides instructions for using Oracle Forms Developer 10g to build internet applications, including an instructor guide with objectives, course content, and chapters on creating forms, working in the Forms Builder environment, creating data blocks and items, and more. It contains proprietary information from Oracle Corporation and is protected by copyright law.
This document provides an introduction to Oracle Forms Builder, a tool used to develop data entry and query screens. It discusses Forms Builder in client/server mode using a 2-tier architecture and in web mode using a 3-tier architecture. The document outlines some key features of Forms Builder including rapid application development, reusable objects, and improved developer productivity. It also provides instructions on setting user preferences and starting Forms Builder.
This document introduces Oracle Forms Developer and Oracle Forms Services. It describes how Oracle 10g products implement grid computing through a software infrastructure that uses low-cost servers and modular storage to balance workloads and provide capacity on demand. It outlines the components of Oracle Application Server 10g and Oracle Developer Suite 10g and describes the features of Oracle Forms Services and Oracle Forms Developer, including their architecture and benefits. It also provides an overview of the course application, which is a customer and order entry application for Summit Office Supply.
- Oracle Form Builder is a component of Oracle Developer/2000 that is used to create event-driven applications to enter, access, change, or delete data from an Oracle database.
- A Forms application consists of forms, menus, and libraries. Forms uses triggers, processes, and events to control user interactions and database transactions.
- The main components of a Forms application include windows, canvases, blocks, items, triggers, alerts, lists of values (LOVs), editors, parameters, program units, libraries, and object groups.
This document provides an overview of the speaker's background and experience with CAD software like AutoCAD and Inventor, as well as content center management. It then discusses best practices for setting up and managing an Inventor content center, including creating read/write libraries, defining categories and family tables, editing family tables, and publishing parts. The speaker offers to help customers develop customized Content Center implementation and training plans.
The document provides steps for installing and configuring the Math-Bridge system, including installing Java, copying system files, compiling, configuring the system properties and ports, adding courses, starting and stopping the server, and finalizing the administrator user configuration. It also provides tips for production settings like adjusting JVM settings and enabling caching.
2012.10 Liferay Europe Symposium, Alistair OldfieldEmeldi Group
This document outlines the approach and execution of migrating a Microsoft SharePoint site into Liferay. It describes inspecting the SharePoint environment and exporting content like pages, documents, and images into XML packages. Custom SharePoint web parts are reimplemented as Java portlets in Liferay. During import, URLs are rewritten and markup is filtered to replace links to the original SharePoint site. The automated, repeatable process allows full migration of content while reusing ported applications in new Liferay installations.
The document describes the architecture of a math training program called Math-Bridge. It includes components like Apache Tomcat for web delivery, Maverick as a model-view-controller framework, and a core component for system functionality. Content is stored and indexed in a ContentDB using technologies like Java, Lucene and OMDoc. A learner model tracks user progress. Other components include presentation of content, user accounts, exercises that interface with a computer algebra system, and a tutorial component. The program uses technologies like Java, databases, XMLRPC and XSLT to power its functionality.
Adobe Flex - Developing Rich Internet Application Workshop Day 2Shyamala Prayaga
This document provides an overview of the Flex 3: Developing Rich Internet Applications course. The course is divided into multiple units that introduce new concepts and include demonstrations, walkthroughs, and labs. Key topics covered include understanding Rich Internet Applications (RIAs), the Adobe Flex product line, Flex architecture, and learning Flex fundamentals like layouts, data binding, and user interface controls.
The document describes the folder structure and features of a sample MVC web application called BrowsePoint. The folder structure separates core files, configuration files, controllers, helpers, libraries, models, and views. Features include APC caching, HTTP request wrapping, and PHP session wrapping. Planned improvements include object mapping, logging, Memcache support, model class generation, improved configurations, and theme layout support.
This document discusses run-time messages and alerts in Oracle Forms. It describes how to handle errors from built-in subprograms, control system messages, create alerts, and handle database server errors. Key points covered include using FORM_SUCCESS to check for errors, the four types of Forms messages, and built-ins for controlling messages and alerts like SET_ALERT_PROPERTY and SHOW_ALERT. It also addresses trapping database errors using triggers or exception handlers.
This document discusses validation in Oracle Forms. It explains that Forms validates data at the form, block, record, and item levels. Validation occurs when the enter key is pressed or when a trigger leaves a validation unit. The document also discusses controlling validation through properties, triggers, and pluggable Java components, as well as tracking validation status. It provides examples of validating user input and using client-side validation.
Non-input items that can be created include display items, image items, buttons, calculated items, hierarchical tree items, and bean area items. Display items and image items show information without input, buttons initiate actions, calculated items use formulas or summaries, tree items show hierarchical data, and bean areas execute Java code. These item types are created by changing an existing item's type or using tools in the Layout Editor and setting properties specific to each item type.
This document discusses writing flexible code that is reusable, generic, and avoids hard-coded object names to make maintenance easier. It describes using system variables to reference the current context and status. Built-in subprograms like GET_ and SET_ can retrieve and set properties of objects. Objects can be referenced by internal ID found using functions like FIND_, or indirectly using COPY and NAME_IN to pass values without hard-coding names. Flexible code is more efficient and reusable across applications.
This document discusses working with data blocks and frames in Oracle Forms. It covers identifying components of the Property Palette, managing object properties, creating and using Visual Attributes, controlling data block and frame properties, and creating and deleting data blocks. The key topics covered are using the Property Palette to modify object properties, setting properties to control data block behavior and appearance, setting frame properties, and creating and deleting data blocks.
Working in the Forms Developer Environment provides an overview of key concepts for navigating and customizing the Forms Builder interface. It describes Forms Builder components like the Object Navigator, Property Palette, and Layout Editor. It also covers setting environment variables for design and run time, running a form from Forms Builder, and using the online help facilities. The document aims to help users describe Forms Builder components, navigate the interface, identify main form objects, customize Forms Builder sessions, and identify main Forms executables.
This document discusses navigation in forms. It distinguishes between internal and external navigation, and describes how to control navigation with properties of the form, block, and item. It explains navigation triggers that fire during or after navigation, and navigation built-ins that can be used in triggers except those that fire during navigation. These include GO_FORM, GO_BLOCK, GO_RECORD, GO_ITEM, NEXT_BLOCK, and others. The document also provides examples of setting properties and using triggers and built-ins to control navigation flow.
This document provides an overview of LOVs (lists of values) and editors in Oracle Forms and describes how to create them. LOVs allow selecting a value for a text item from a dynamic list, and are created from a database query. Editors override the default editor for a text item and allow customizing the editing window. The document explains that LOVs are easiest to design using the LOV Wizard, which guides selecting columns and properties. Editors are created in the Object Navigator and associated with a text item's properties. Practice questions at the end involve creating an LOV attached to a text item and an Editor attached to another item.
This document describes how to run a Forms application using Oracle Application Server Containers for J2EE (OC4J). It explains that OC4J is used to run Forms applications on the development machine and test them in a web browser. When running a form, the Forms Client applet displays in the browser while the Forms Listener Servlet and Runtime Engine handle processing on the application server. Users can navigate forms and query, insert, update, and delete records in different operation modes.
The document discusses different types of canvases in Oracle Forms including stacked, toolbar, and tab canvases. It describes how stacked canvases overlay content canvases, toolbar canvases provide standard buttons and elements, and tab canvases organize information across pages. It provides instructions for creating these canvases, setting their properties, and placing items on tab pages.
The document discusses debugging triggers in Oracle Forms Builder. It describes the components of the Debug Console used for debugging, including the stack, variables, watch, form values, PL/SQL packages, and breakpoints panels. It explains how to run a form in debug mode, set breakpoints in client and stored code, step through code, and view variable values while debugging.
This document discusses run-time messages and alerts in Oracle Forms. It describes how Forms displays messages to inform users of events, and how to control message severity and suppress messages. There are different types of messages - informative, error, working, and application. It also discusses handling run-time errors of built-in subprograms, and using triggers to intercept system messages. The document covers setting properties of alerts, and controlling alerts with built-in functions. Finally, it discusses trapping database server errors using built-ins or exceptions.
The document provides instructions for using Oracle Forms Developer 10g to build internet applications, including an instructor guide with objectives, course content, and chapters on creating forms, working in the Forms Builder environment, creating data blocks and items, and more. It contains proprietary information from Oracle Corporation and is protected by copyright law.
This document provides an introduction to Oracle Forms Builder, a tool used to develop data entry and query screens. It discusses Forms Builder in client/server mode using a 2-tier architecture and in web mode using a 3-tier architecture. The document outlines some key features of Forms Builder including rapid application development, reusable objects, and improved developer productivity. It also provides instructions on setting user preferences and starting Forms Builder.
This document introduces Oracle Forms Developer and Oracle Forms Services. It describes how Oracle 10g products implement grid computing through a software infrastructure that uses low-cost servers and modular storage to balance workloads and provide capacity on demand. It outlines the components of Oracle Application Server 10g and Oracle Developer Suite 10g and describes the features of Oracle Forms Services and Oracle Forms Developer, including their architecture and benefits. It also provides an overview of the course application, which is a customer and order entry application for Summit Office Supply.
- Oracle Form Builder is a component of Oracle Developer/2000 that is used to create event-driven applications to enter, access, change, or delete data from an Oracle database.
- A Forms application consists of forms, menus, and libraries. Forms uses triggers, processes, and events to control user interactions and database transactions.
- The main components of a Forms application include windows, canvases, blocks, items, triggers, alerts, lists of values (LOVs), editors, parameters, program units, libraries, and object groups.
This document provides an overview of the speaker's background and experience with CAD software like AutoCAD and Inventor, as well as content center management. It then discusses best practices for setting up and managing an Inventor content center, including creating read/write libraries, defining categories and family tables, editing family tables, and publishing parts. The speaker offers to help customers develop customized Content Center implementation and training plans.
The document provides steps for installing and configuring the Math-Bridge system, including installing Java, copying system files, compiling, configuring the system properties and ports, adding courses, starting and stopping the server, and finalizing the administrator user configuration. It also provides tips for production settings like adjusting JVM settings and enabling caching.
2012.10 Liferay Europe Symposium, Alistair OldfieldEmeldi Group
This document outlines the approach and execution of migrating a Microsoft SharePoint site into Liferay. It describes inspecting the SharePoint environment and exporting content like pages, documents, and images into XML packages. Custom SharePoint web parts are reimplemented as Java portlets in Liferay. During import, URLs are rewritten and markup is filtered to replace links to the original SharePoint site. The automated, repeatable process allows full migration of content while reusing ported applications in new Liferay installations.
The document describes the architecture of a math training program called Math-Bridge. It includes components like Apache Tomcat for web delivery, Maverick as a model-view-controller framework, and a core component for system functionality. Content is stored and indexed in a ContentDB using technologies like Java, Lucene and OMDoc. A learner model tracks user progress. Other components include presentation of content, user accounts, exercises that interface with a computer algebra system, and a tutorial component. The program uses technologies like Java, databases, XMLRPC and XSLT to power its functionality.
Adobe Flex - Developing Rich Internet Application Workshop Day 2Shyamala Prayaga
This document provides an overview of the Flex 3: Developing Rich Internet Applications course. The course is divided into multiple units that introduce new concepts and include demonstrations, walkthroughs, and labs. Key topics covered include understanding Rich Internet Applications (RIAs), the Adobe Flex product line, Flex architecture, and learning Flex fundamentals like layouts, data binding, and user interface controls.
The document describes the folder structure and features of a sample MVC web application called BrowsePoint. The folder structure separates core files, configuration files, controllers, helpers, libraries, models, and views. Features include APC caching, HTTP request wrapping, and PHP session wrapping. Planned improvements include object mapping, logging, Memcache support, model class generation, improved configurations, and theme layout support.
This document discusses run-time messages and alerts in Oracle Forms. It describes how to handle errors from built-in subprograms, control system messages, create alerts, and handle database server errors. Key points covered include using FORM_SUCCESS to check for errors, the four types of Forms messages, and built-ins for controlling messages and alerts like SET_ALERT_PROPERTY and SHOW_ALERT. It also addresses trapping database errors using triggers or exception handlers.
This document discusses validation in Oracle Forms. It explains that Forms validates data at the form, block, record, and item levels. Validation occurs when the enter key is pressed or when a trigger leaves a validation unit. The document also discusses controlling validation through properties, triggers, and pluggable Java components, as well as tracking validation status. It provides examples of validating user input and using client-side validation.
This document discusses query triggers in Oracle Forms. It describes the query processing steps, the different types of query triggers (pre-query and post-query triggers), and how to write triggers to screen and supplement queries. It also covers obtaining query information at runtime, overriding default query processing, and controlling trigger actions based on the form's query status.
This document discusses different types of input items in Oracle Forms, including check boxes, list items, and radio groups. It describes how to create each type by converting an existing item or using tools in the Layout Editor. Properties specific to each input type can be set, such as list elements for a list item or radio buttons for a radio group. Mapping other values allows non-listed values to be assigned an item display value. The overall goal is to learn how to create different input items that accept user input in Oracle Forms.
This document discusses creating and using triggers in Oracle Forms Builder. It describes the steps to create a trigger, including selecting a scope, invoking the trigger list, defining code in the PL/SQL editor, and compiling. Common trigger types like When-Button-Pressed and When-Window-Closed are described. The document also covers using built-in subprograms and variables in trigger code and limitations on certain built-ins.
This document discusses list of values (LOVs) and editors in Oracle Forms Builder. It describes how to create LOVs and editors manually or using wizards, set their properties, and associate them with text items in a form. LOVs provide dynamic lists for text items, pulling from a supporting record group or query. Editors override the default editor for text items to allow for custom formatting and functionality.
This document discusses how to create a master-detail form in Oracle Forms. It describes establishing relationships between data blocks, defining join conditions, setting deletion properties, and modifying block structure and layout. Key points covered include using the Data Block Wizard to create relationships, automatic block coordination when running the form, and using the Layout Wizard and Data Block Wizard in reentrant mode to modify existing blocks. The overall goal is to teach the reader how to build a basic master-detail form and manage the relationships between related data.
This document discusses writing flexible code in Oracle Forms. It describes flexible code as code that is reusable, generic, avoids hardcoded object names, and makes maintenance easier. It recommends using system variables and built-in functions to reference objects by ID or indirectly. This allows code to be written that is more efficient and generic. Specific techniques covered include using system variables for context, GET/SET properties functions, and functions like FIND and COPY to work with object IDs.
This document discusses triggers in Oracle Forms Builder. It defines triggers as event-activated program units. It describes different trigger categories including block processing, interface events, and validation triggers. It outlines the key components of a trigger as the event that fires it, the PL/SQL code that executes, and the scope level (form, block or item). It also addresses setting the execution hierarchy to control trigger firing order.
This document discusses various methods for reusing objects and code in Oracle Forms, including:
- Using property classes to inherit properties and standardize objects
- Grouping related objects into object groups for easy reuse
- Creating object libraries to share reusable components between forms
- Marking objects as SmartClasses for rapid, standardized application
It also covers reusing PL/SQL code through copying, subclassing, and defining library program units to call code from multiple places.
The document discusses transaction processing in Oracle Forms. It explains that Forms uses transactions to apply changes to the database, which involves two phases - post and commit. During commit, it validates the form and blocks, performs the necessary DML operations like insert, update, delete, and fires various commit triggers. Forms supports supplementing the transaction processing using triggers at different stages. It also discusses getting and setting the commit status, and using array DML to reduce network traffic.
This document provides instructions on creating non-input items in Oracle Forms, including display items, image items, buttons, calculated items, hierarchical tree items, and bean area items. It describes the properties and functions of each item type, and provides steps for creating examples of each type. The goal is to teach the reader how to identify non-input item types and create various kinds of static and dynamic content displays within Oracle Forms applications.
This document discusses navigation in Oracle Forms applications. It describes internal and external navigation, controlling navigation with object properties, and using navigation triggers. Key points covered include setting the first navigation block or item properties, writing pre- and post-triggers for forms, blocks, records and items, and using built-in navigation functions like GO_FORM and NEXT_RECORD in triggers. The summary reiterates that navigation can be controlled through properties or triggers, and outlines the different types of navigation triggers and built-ins that can be used.
The document provides an overview of the Oracle Forms Builder development environment. It describes Forms Builder components like the Object Navigator and Layout Editor. It explains how to navigate the Forms Builder interface, identify main form objects, customize Forms Builder sessions, use online help, and run forms. It also covers Forms modules types, setting runtime environment variables, and testing forms using the Run Form button.
This document discusses working with text items in Oracle Forms. It describes how to create text items, modify their appearance and properties, control their data and navigation behavior, and add functionality. Key topics covered include modifying font, color, and prompt properties; controlling data type, length, and initial values; and displaying help messages.
WebUtil is a utility that enables client-side functionality on Win32 clients. It consists of Java classes, Forms objects, and a PL/SQL library. WebUtil provides benefits such as only requiring PL/SQL coding knowledge, free download, and easy integration into Forms applications. To integrate WebUtil, a developer attaches the WebUtil library and subclasses the WebUtil object group. Then WebUtil functions can be used to interact with the client, such as opening file dialogs, reading/writing files, executing commands, and automating applications.
This document discusses adding functionality to items in Oracle Forms through triggers and built-in functions. It covers using triggers to interact with checkboxes, lists, buttons, images and trees. It also discusses populating items from databases, files and Java beans. Built-ins allow accessing properties, invoking methods and handling events of Java beans from Forms triggers. The overall aim is to supplement the functionality of both input and non-input items.
This document discusses how to create multiple form applications in Oracle Forms. It covers calling one form from another, defining shared functionality between forms, and sharing data among open forms through global variables, parameter lists, global record groups, and shared PL/SQL variables. The key benefits of multiple form applications are modularity, easier debugging, and improved performance and scalability.
This document discusses how to create a basic form module in Oracle Forms. It covers creating an empty form module, adding a data block using the Data Block Wizard and Layout Wizard, saving and compiling the form module, and different file formats. The key steps are creating an empty module, adding a data block manually or with wizards, saving the module, compiling it, and deploying it to the middle tier to run in a browser.
The document discusses Docker and Selenoid, with Docker being a tool to run applications in isolated containers and Selenoid being a tool for running Selenium tests in isolated Docker containers. Selenoid provides benefits over Selenium Grid like better resource usage, easier installation, and support for running each test in a separate container. The document also provides instructions for installing and running Selenoid using Docker or without Docker on different operating systems.
This document provides an introduction to Visual Basic 6.0 by describing its key components and features. It outlines the history of Visual Basic and how it evolved as a programming language. It then explains the main elements of the Visual Basic integrated development environment (IDE) playground, including the title bar, menu bar, toolbar, form window, toolbox, project explorer window, properties window, and form layout window. It also briefly mentions Visual Basic projects, object-oriented programming concepts, and concludes by thanking the reader.
Windows display content canvases and allow viewing one canvas at a time. Content canvases are surfaces that display within a window. Each window must have at least one content canvas. You can create additional windows in the Object Navigator and display different canvases or the same form module across multiple windows and canvases. Properties of windows and canvases allow setting positions, sizes, names and other attributes.
Windows display content canvases and allow viewing one canvas at a time. Content canvases are surfaces that display within a window. Each window must have at least one content canvas. You can create additional windows in the Object Navigator and display different canvases or the same form module across multiple windows and canvases. Properties of windows and canvases allow setting positions, sizes, names and other attributes.
Introduction to Docker - Vellore Institute of TechnologyAjeet Singh Raina
- The document introduces Docker, including what problem it solves for software development workflows, its key concepts and terminology, and how to use Docker to build, ship, and run containers.
- It compares Docker containers to virtual machines and discusses Docker's build process using Dockerfiles and images composed of layers.
- Hands-on demos are provided for running a first Docker container, building an image with Dockerfile, and using Docker Compose to run multi-container apps.
- Later sections cover Docker Swarm for clustering multiple Docker hosts and running distributed apps across nodes, demonstrated through a Raspberry Pi example.
- The document introduces Docker, explaining that it provides standardized packaging for software and dependencies to isolate applications and share the same operating system kernel.
- Key aspects of Docker are discussed, including images which are layered and can be version controlled, containers which start much faster than virtual machines, and Dockerfiles which provide build instructions for images.
- The document demonstrates Docker's build, ship, and run workflow through examples of building a simple image and running a container, as well as using Docker Compose to run multi-container applications like WordPress. It also introduces Docker Swarm for clustering multiple Docker hosts.
The document discusses a module for CMS Made Simple that transforms the backend into a responsive HTML5 web app for mobile devices. The module allows the backend to be available offline and content to be edited offline. When online again, it checks for conflicts and pushes any changes. It takes an approach of using client-side storage to make the backend available as a web app that can do most of what a native mobile app can do, without needing to go through app stores.
This document appears to be a PowerPoint presentation about Kubernetes. The presentation covers topics like what Kubernetes is, different Kubernetes installation types including all-in-one, single control plane and multi-worker, and single control plane with external etcd. It also discusses tools for deploying Kubernetes clusters locally like Minikube, Kind, and MicroK8s. The presentation includes charts, tables, and discusses using kubectl proxy to access the Kubernetes API. It concludes by thanking the audience.
This document provides an introduction to using the Eclipse integrated development environment (IDE) to create and run Java programs. It describes the key components of Eclipse, including editors, views, perspectives, and workspaces. It also explains how to set up a Java project in Eclipse, create packages and classes, write code including a main method, compile code, and run a program. The document uses examples like a simple text input/output program and a gallons to liters conversion program to demonstrate setting up, writing, compiling and running a Java application in Eclipse.
The document provides an overview of Worklight, an IBM product for developing mobile applications. It discusses the mobile development lifecycle challenges Worklight addresses like cross-platform development, testing on many device configurations, and faster release cycles. It describes Worklight's vision of an open platform for hybrid apps and its focus on enterprise needs. Key Worklight components are introduced, including the Worklight Server for delivery, integration and management of apps, the Worklight Console for analytics and control, and Worklight Studio as an IDE. The document demonstrates Worklight's capabilities through an example of creating a simple "Hello Worklight" application.
Creating Accessible Web Pages Using Dreamweaver Mx 2004brighteyes
Dreamweaver can be configured to promote accessibility by checking attributes when inserting elements. The document explores Dreamweaver's interface, including the document toolbar, window and property inspector. It demonstrates how to create a new web site, add text and headings to a page and save the file, changing properties in the design and code views. The goal is to learn the basics of the Dreamweaver interface and start building an accessible webpage.
The document provides an overview of key Eclipse terminology for new users, including: the workspace stores all projects; a project contains code for a single application; views display different types of information and outputs; and the Package Explorer, Navigator, Console, and Editor views show folders/files, program output, and code to edit. It also briefly describes the Eclipse menu for file management, editing, running programs, and customization.
Presentation shown by Alexander Kandzior in his OpenCms Days 2014 keynote.
The next major version 9.5 of OpenCms is ready and it’s easier to use than ever!
OpenCms 9.5 finally allows content managers to handle all of their editing tasks directly in the website, without the need to access the “power user” workplace interface.
New features in OpenCms 9.5 also include:
- Nested Containers
- User generated content
- PDF generation
- More options to reuse existing content
- Improved localization of container pages
- Several enhancements in the user interface
- Much better documentation
- An updated responsive demo based on Bootstrap
… and more!
The document provides an introduction to customizing and extending the Weblogic Console. It discusses reasons for customization such as rebranding to match corporate identity or differentiating environments. It describes extension points in the Weblogic Console UI hierarchy that allow for replacing or adding content. The document outlines steps to build a new Look and Feel including modifying configuration files, compiling JSPs, and creating a WAR file. It also discusses more complex customizations like using MBeans and adding new portlets.
This document provides instructions for customizing the Weblogic console login page and appearance through a series of labs. The labs cover setting up a Weblogic server domain, creating a console customization project, making initial customizations to things like login page styling and colors, exploring the existing console code to make more advanced customizations, and deploying the customized console. Specific customizations demonstrated include making the login panel border color and toolbar color dynamic based on the domain name. The labs build skills for exploring, understanding, and enhancing the Weblogic console user interface.
Drupal case study: Behind the scenes of website of University of TartuRené Lasseron
Story about migrating public website of one of the oldest universities in Europe from proprietary CMS to Drupal 7. Presented by Mekaia (http://mekaia.com) at DrupalCamp Baltics 2012 (http://www.drupalcamp.lv/).
This document outlines the requirements and structure for a technical book on Plone development. It will contain 14 chapters covering topics like custom content types, testing, internationalization and performance. Each chapter will include recipes to demonstrate concepts. The book will provide a comprehensive guide for building advanced Plone sites and products.
AWS Innovate: Moving Microsoft .Net applications one container at a time - Da...Amazon Web Services Korea
This document discusses moving Microsoft .NET applications to containers. It provides a brief history of .NET and its evolution to support cross-platform development. It explores using .NET and Docker to develop applications on Windows and deploy them in Linux containers on AWS. It demonstrates developing an ASP.NET application on Windows and running it in a Linux container on AWS EC2. It summarizes that Microsoft has made cross-platform development easier with .NET Core, existing applications can run in Docker containers under Mono or .NET Core, and AWS supports .NET and Docker applications through services like EC2 and ECS.
This document provides an overview of using the UICatalog sample code to learn about the user interface components available in UIKit. It discusses downloading and running the UICatalog sample, and how to capture screenshots of the user interface elements to create mockups and prototypes. It also includes background information on Objective-C, UIKit, the model-view-controller (MVC) pattern, and the basic structure of an iOS application.
Introduction
Overview
With Oracle Forms Developer you can take advantage of the GUI environment by displaying a form module across several canvases and in multiple windows. This lesson familiarizes you with the window object and the default canvas type, the content canvas.
Windows and Canvases
With Forms Builder you can display an application in multiple windows by using its display objects—windows and canvases.
What Is a Window?
A window is a container for all visual objects that make up a Forms application. It is similar to an empty picture frame. The window manager provides the controls for the window that enable such functionality as scrolling, moving, and resizing. You can minimize a window. A single form may include several windows.
What Is a Canvas?
A canvas is a surface inside a window container on which you place visual objects such as interface items and graphics. It is similar to the canvas upon which a picture is painted. To see a canvas and its contents at run time, you must display it in a window. A canvas always displays in the window to which it is assigned.
Note: Each item in a form must refer to no more than one canvas. An item displays on the canvas to which it is assigned, through its Canvas property. Recall that if the Canvas property for an item is left unspecified, that item is said to be a Null-canvas item and will not display at run time.
Windows and Content Canvases (continued)
What Is a Viewport?
A viewport is an attribute of a canvas. It is effectively the visible portion of, or view onto, the canvas.
The Content Canvas
Forms Builder offers different types of canvases. A content canvas is the base canvas that occupies the entire content pane of the window in which it displays. The content canvas is the default canvas type. Most canvases are content canvases.
The Relationship Between Windows and Content Canvases
You must create at least one content canvas for each window in your application. When you run a form, only one content canvas can display in a window at a time, even though more than one content canvas can be assigned to the same window at design time.
At run time, a content canvas always completely fills its window. As the user resizes the window, Forms resizes the canvas automatically. If the window is too small to show all items on the canvas, Forms automatically scrolls the canvas to bring the current item into view.
Note: You can assign multiple content canvases to a window; however, only one content canvas at a time can be displayed in a window.
The Default Window
When you create a new form module, Forms Builder creates a new window implicitly. Thus, each new form module has one predefined window, which is called WINDOW1. You can delete or rename WINDOW1, or change its attributes.
Uses and Benefits of a New Window
You can create additional windows in which to display your form application. A new or second window provides the ability to do the following:
Display two or more content canvases at once.
Modularize the form contents.
Switch between canvases without replacing the initial one.
Take advantage of window manager functionality such as minimizing.
Displaying a Form Module in Multiple Windows
You can create additional windows in a form so that you can:
Display more than one content canvas at a time
Switch between content canvases without the need to replace the first one
Separate the form module into multiple layouts
Use features of the window manager, such as allowing the user to resize or close a window
You can create two different types of windows:.
A modal window is a restricted window that the user must respond to before moving the input focus to another window. Modal windows:
Must be dismissed before control can be returned to a modeless window
Become active as soon as they display
Require a means of exit or dismissal
A modeless window is an unrestricted window that the user can exit freely. Modeless windows:
Can be displayed at the same time as multiple other modeless windows
Are not necessarily active when displayed
Are the default window type
Creating a New Window
To create a new window, perform the following steps:
1.Select the Windows node in the Object Navigator and click Create.
2.A new window entry displays, with a default name of WINDOWXX.
3.If the Property Palette is not already displayed, double-click the window icon to the left of the new window entry.
4.Set the window properties according to your requirements.
Note: For your new window to display, you must specify its name in the Window property of at least one canvas. To display a console to end users, set the form-level property Console Window to the window in which you want to display the console. To hide the console, set the property to <Null>.
Setting Window Properties
You set properties for windows to determine their behavior and appearance. Some of these properties are:
1.X/Y Position: Specifies the location of the window within the containing window.
2.Title: The title to be displayed; if not specified, uses the name indicated by the window Name property
3.Horizontal/Vertical Toolbar Canvas: Specifies the toolbar canvas to be displayed horizontally across the top or vertically to the left of the window; selected from all horizontal/vertical toolbar canvases assigned to this window
4.Modal: Specifies if window is modal, requiring the user to dismiss the window before any other user interaction can continue, like Question window above
5.Show Horizontal/Vertical Scroll Bar: Whether a horizontal or vertical scroll bar should display on the window
6.Hide on Exit: Whether Forms hides the window automatically when the end user navigates to an item in another window (not shown on slide)
For a description of other properties that affect the behavior of windows, click the property in the Property Palette and press [F1].
GUI Hints
GUI Hints are recommendations to the window manager about the window appearance and functionality. There are certain properties under the Functional group that enable you to make these recommendations:
Close Allowed: Enables the mechanism for closing the window (Forms responds to user attempts to close the window by firing a WHEN-WINDOW-CLOSED trigger.)
Move/Resize Allowed: Whether user can move and resize the window
Maximize/Minimize Allowed: Whether user can zoom or iconify the window
Inherit Menu: Whether the window displays the current form menu
Displaying a Form Module on Multiple Layouts
You can have more than one content canvas in your form application. However, remember that only one content canvas can display in a window at one time. To display more than one content canvas at the same time, you can assign each content canvas to a different window.
Now you can display the form module on multiple layouts or surfaces.
Creating a New Content Canvas
Creation of a content canvas can be implicit or explicit.
Implicitly Creating a Content Canvas
There are two ways of implicitly creating a new content canvas:
1.Layout Wizard: When you use the Layout Wizard to arrange data block items on a canvas, the wizard enables you to select a new canvas on its Canvas page. In this case, the wizard creates a new canvas with a default name of CANVASXX.
2.Layout Editor: When there are no canvases in a form module and you invoke the Layout Editor; Forms Builder creates a default canvas on which you can place items.
Explicitly Creating a Content Canvas
You can create a new content canvas explicitly by using the Create icon in the Object Navigator.
Creating a New Content Canvas (continued)
To explicitly create a new content canvas, perform the following steps:
1.Click the Canvases node in the Object Navigator.
2.Click the Create icon.
3.A new canvas entry displays with a default name of CANVASXX.
4.If the Property Palette is not already displayed, click the new canvas entry and select Tools > Property Palette.
5.Set the canvas properties according to your requirements.
Note: Double-clicking the icon for a canvas in the Object Navigator will invoke the Layout Editor instead of the Property Palette.
Setting Content Canvas Properties
You can set properties to determine how the canvas is to be displayed. Several properties in the Physical group are depicted in the slide: Width, Height, and Viewport X/Y Position on Canvas. For a canvas to display at run time, its Window property must also be specified.
In the General group, you can choose the Canvas Type. This lesson covers the Content Canvas; other canvas types are presented in the next lesson.
In the Functional group, you can set Raise on Entry to affect whether the canvas is always brought to the front of the window when the user navigates to an item on the canvas. You use this property when the canvas is displayed in the same window with other canvases. Forms always ensures that the current item is visible. Even if Raise on Entry is set to No, Forms will bring the canvas to the front of the window if the user navigates to an item on the canvas that is hidden behind other canvases.
Performance Tip: To reduce the time that is needed to display the initial screen, keep the number of items initially displayed to a minimum. You can hide elements, such as canvases, that are not immediately required. To do this, set the canvas Raise on Entry property to Yes, and set Visible to No.
Summary
In this lesson, you should have learned:
About the relationship between windows and content canvases
How to create a new window
How to create a new content canvas
How to display a form module on multiple layouts by displaying each canvas in a separate window
Practice 11 Overview
In this practice session, you will customize windows in your form modules. You will resize the windows to make them more suitable for presenting canvas contents. You will also create a new window to display the contents of the INVENTORIES block.
Change the size and position of the window in the CUSTOMERS form. Change its name and title. Save and run the form.
Modify the name and title of the window in the ORDERS form.
Create a new window in the ORDERS form. Make sure the contents of the INVENTORIES block display in this window. Save and run the form.
Note: For solutions to this practice, see Practice 11 in Appendix A, “Practice Solutions.”
Practice 11
1.Modify the window in the CUSTGXX form. Change the name of the window to WIN_CUSTOMER, and change its title to Customer Information. Check that the size and position are suitable.
2.Save, compile, and run the form to test the changes.
3.Modify the window in the ORDGXX form. Ensure that the window is called WIN_ORDER. Also change its title to Orders and Items. Check that the size and position are suitable.
4.In the ORDGXX form, create a new window called WIN_INVENTORY suitable for displaying the CV_INVENTORY canvas. Use the rulers in the Layout Editor to help you plan the height and width of the window. Set the window title to Stock Levels. Place the new window in a suitable position relative to WIN_ORDER. Ensure that the window does not display when the user navigates to an item on a different window.
5.Associate the CV_INVENTORY canvas with the window WIN_INVENTORY. Compile the form. Click Run Form to run the form. Ensure that the INVENTORIES block is displayed in WIN_INVENTORY when you navigate to this block. Also make sure that the WIN_INVENTORY window is hidden when you navigate to one of the other blocks.
6.Save the form.