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.
The document summarizes goals and concepts for iOS development, including:
1. It discusses using common iOS UI elements like text fields, labels, sliders and switches, and handling actionsheets and alerts.
2. It explains application delegates and how they handle events on behalf of other objects. The UIApplication delegate is discussed.
3. It provides an overview of view controllers and their role in linking an app's data and visual interface, and describes their life cycle and common methods.
4. Automatic Reference Counting (ARC) is introduced as replacing the need to manually manage memory by releasing objects.
This document provides instructions and code snippets for building mobile apps with React Native. It discusses building a BMI calculator app and stopwatch app to demonstrate React Native features. Key points covered include initializing projects, building the user interface, adding styles, handling user input, using state to update the UI, and separating components. Methods like setState() and binding are explained. The full source code is provided for reference. Exercises are suggested to extend the apps further.
This is the workshop presentation material for the Point-And-Click App Building Hands-On Workshop (HOW) being presented at Dreamforce 2015 in the DevZone. This content pairs with the "Suggestion Box App" project live in Trailhead
Luke Cushanick Admin Tips and Tricks for Salesforce Trailblazer Community Chr...Anna Loughnan Colquhoun
Luke Cushanick Admin Tips and Tricks for Salesforce Trailblazer Community Christchurch & Wellington, virtual Zoom meeting, jointly hosted by Rebecca D'Arcy and Anna Loughnan
Creating A User‑Defined Function In Excel Using VbaChester Tugwell
Excel includes many different functions that help you complete calculations, but have you ever wished for a function that that doesn’t exist in Excel? If you have, this tutorial will explain how to create a function DIY style.
The document provides tips and tricks for using the iSMA Tool software. It lists over 30 features of the tool, describing how each one aims to help users by making tasks more convenient, improving user experience, saving time and effort, and allowing for better management, analysis and customization. The tool allows users to be more productive and perform tasks more quickly and easily through features like auto-updating, customizable interfaces, advanced search functions, bulk actions, and extensive customization options.
The document summarizes goals and concepts for iOS development, including:
1. It discusses using common iOS UI elements like text fields, labels, sliders and switches, and handling actionsheets and alerts.
2. It explains application delegates and how they handle events on behalf of other objects. The UIApplication delegate is discussed.
3. It provides an overview of view controllers and their role in linking an app's data and visual interface, and describes their life cycle and common methods.
4. Automatic Reference Counting (ARC) is introduced as replacing the need to manually manage memory by releasing objects.
This document provides instructions and code snippets for building mobile apps with React Native. It discusses building a BMI calculator app and stopwatch app to demonstrate React Native features. Key points covered include initializing projects, building the user interface, adding styles, handling user input, using state to update the UI, and separating components. Methods like setState() and binding are explained. The full source code is provided for reference. Exercises are suggested to extend the apps further.
This is the workshop presentation material for the Point-And-Click App Building Hands-On Workshop (HOW) being presented at Dreamforce 2015 in the DevZone. This content pairs with the "Suggestion Box App" project live in Trailhead
Luke Cushanick Admin Tips and Tricks for Salesforce Trailblazer Community Chr...Anna Loughnan Colquhoun
Luke Cushanick Admin Tips and Tricks for Salesforce Trailblazer Community Christchurch & Wellington, virtual Zoom meeting, jointly hosted by Rebecca D'Arcy and Anna Loughnan
Creating A User‑Defined Function In Excel Using VbaChester Tugwell
Excel includes many different functions that help you complete calculations, but have you ever wished for a function that that doesn’t exist in Excel? If you have, this tutorial will explain how to create a function DIY style.
The document provides tips and tricks for using the iSMA Tool software. It lists over 30 features of the tool, describing how each one aims to help users by making tasks more convenient, improving user experience, saving time and effort, and allowing for better management, analysis and customization. The tool allows users to be more productive and perform tasks more quickly and easily through features like auto-updating, customizable interfaces, advanced search functions, bulk actions, and extensive customization options.
Symfony can be used to create an ecommerce app. You can also easily integrate ReactJS on the front-end of your Symfony ecommerce app and use Cloudinary for storing images.
Green Lantern Framework with Selenium IDESrilu Balla
This document describes a framework called Green Lantern for creating automated tests that are resilient to user interface changes. It involves naming elements on web pages with a consistent convention, storing test data separately, and taking screenshots at each step to log results. The framework allows test scripts to be reused across similar applications. It also simplifies updating scripts when interfaces change by focusing updates in element repositories rather than throughout scripts. The document provides detailed instructions for setting up projects using the framework with examples for testing Gmail, Netflix, and Yahoo login pages.
This document provides an overview of building Lightning components in Salesforce. It discusses setting up the development environment, creating an Aura-enabled Apex controller, and building the core components of an account locator app including AccountList, AccountMap, and handling intercomponent communication. Key aspects covered include loading external libraries, iterating over data, firing custom events, and integrating with the Salesforce1 mobile app. The goal is to create a reusable AccountLocator component that displays a map and list of accounts, centers the map on selection, and loads account details in Salesforce1.
This document describes the steps to create a salary advance workflow in SharePoint using Visual Studio. The workflow allows employees to request a salary advance, which is then sent to the accounts department for approval or rejection. Key steps include:
1. Creating a new SharePoint project in Visual Studio and defining the URL of the associated web application and list.
2. Adding a sequential workflow and associating it with the salary advance list.
3. Defining a while loop to hold recurring activities until workflow completion.
4. Adding if/else branches for approved, rejected, and initiated statuses and activities like logging, emailing, and terminating the workflow.
5. Populating the if conditions and branches
Supercharge Your Pages - New Ways to Extend the Confluence EditorAtlassian
The new Confluence editor brings never before seen capabilities to our developers to extend the editor. During this session, Klaus Ihlberg will explain how users use Confluence today and how to use this information and the new capabilities, to develop apps that supercharge Confluence pages.
Lab: Mobile App Development with XPages and Extension LibraryWorkFlowStudios
The document describes creating a mobile application using XPages to view movies and actors from an existing Notes database. It involves modeling the mobile page flow with main and detail pages, creating the pages using Mobile Page controls, and adding views and panels to display the movie and actor data. Tapping a movie in the list transitions to a new page displaying that movie's actors, fetched via lookups to the underlying Notes documents.
The Green Lantern Framework provides a standardized way to automate regression tests across applications with changing UIs. It involves capturing UI elements, renaming them with English aliases, categorizing the elements, and writing scripts that use the aliases. This allows scripts to be reused across similar applications by changing the alias mappings as needed. It provides more maintainable, reusable automation than traditional record-and-play tools that break with any UI changes.
The document discusses concepts and best practices for building single page applications (SPAs) using a component-based architecture. Everything the user interacts with should be a component. Components should be based on state rather than modifying the DOM directly. Data fetching conventions include matching API endpoints to serializers and actions. Services discussed include a dispatcher, store, and mixins for handling actions, managing component scopes, and fetching additional API data.
For the first time, 'WordPress-Trivandrum' had a Live Demo Session.
WordPress is not just about blogging. We’ve experienced e-commerce and social media revolution. It's time for another one, the Internet of Things or IoT. There are a handful of automation plugins and services available for WordPress and the number is about to grow. In this session, we will have a look at what we can do with WordPress for connecting our website to real-world Things – "The Internet of Things".
Key focus:-
• Google Assistant
• Amazon Alexa
• IFTTT
• Philips Hue
• Arduino
• Raspberry Pi
Live Demos: -
• Get a Light flashing when someone comments in posts
• Get an Alert sound when you receive an order in your shop
• Add photos to the Photo Gallery whenever you post it in Instagram
• Ask Google Assistant to create a new post
• Get an alert when someone submits a custom web form you created
The document discusses various Android widgets such as TextView, ImageView, EditText, CheckBox, and RadioButton. It provides code examples for how to implement each widget in an Android application. For TextView, it demonstrates how to display simple text. For ImageView, it shows how to display an image. For EditText, it explains how to create an editable text field. For CheckBox, it provides an example of a checkbox that can be checked or unchecked. And for RadioButton, it discusses using radio buttons within a RadioGroup so that only one can be selected at a time.
The document provides tips for finding resources in the Eclipse workspace using a visitor. It describes creating a class that implements IResourceProxyVisitor and overriding the visit() method. This method would check each resource proxy for a match to the location string and return the resource if found. This allows recursively searching the workspace to locate a resource based on its path or other identifier.
Slides for the hands on lightning component workshop that is accompanying the trailhead found https://developer.salesforce.com/trailhead/project/account-geolocation-app
This document provides tips and tricks for Odoo development. It discusses module structure, creating new tables and inheriting existing tables, creating menu items and CRUD for models, creating master-detail relationships between models, creating models from multiple models using queries, creating buttons that trigger actions, sending emails via API using email templates, and creating job schedules using automated actions.
The document discusses the Controls object in Microsoft Small Basic, which allows adding controls like text boxes and buttons to the graphics window. It describes various operations and properties of the Controls object, such as AddTextBox to add a text box, GetTextBoxText to retrieve text from a text box, and ButtonClicked and TextTyped events. Control events can generate actions when a button is clicked or text is typed in a text box. The document provides an example of a program that uses the Controls object and ends by asking the reader to write a program to display a simple form with text boxes and a submit button.
The document discusses Quick Test Professional (QTP) user-defined functions. It covers:
- Creating public and private functions associated with test objects or globally
- Registering public functions to test objects using the Function Definition Generator
- Adding registered functions as steps in tests by selecting the test object and registered operation
A quick run through explaining actions and filters that are used throughout WordPress (with useful metaphors) and some examples. It is intended to demonstrate that actions and filters are not as scary as people might think and that they can very easily make significant changes with only a few lines of code.
This is the workshop presentation material for the Lightning Components Hands-On Workshop (HOW) being presented at Dreamforce 2015 in the DevZone. This content pairs with the Lightning Components Trailhead project live in Trailhead as of Dreamforce 2015.
show code and all classes with full implementation for these Program S.pdfAlanSmDDyerl
show code and all classes with full implementation for these Program Specifications.
Example products ( camcorder, dvd player, blueray player, tv, camera, xbox 360, ps4, Wii,
laptops, iphone, battery, smart phones, computer desktop, printer, usb, mouse)
Develop an inventory management system for an electronics store. The inventory system should
have the following functionalities:
BuildInventory: read a text file containing electronics products information and dynamically
store them in an array of pointers.
ShowInventory: display all inventory items.
UpdateInventory: ask for item id and quantity. If found display cost and update Product object
info (reduce Product's quantity and potentially update restocking flag).
Terminate: save current inventory to a text file.
This programming assignment illustrates the following concepts:
Text file reading and writing.
Arrays of pointers and dynamic memory allocations with new and delete.
Inheritance.
C++ type casting: static_cast.
NOTE: This assignment is not about polymorphism or dynamic_cast! Your program should not
contain any virtual function and/or use of dynamic_cast mechanism or point deductions will
apply. You will have opportunity to use polymorphism in the next assignment.
Class Design
You need at least three classes.
class InventoryItem (minimum implementation specified below) - This is the base class.
Protected member data: item id (integer) and restocking (bool).
Public static data:
const integer (item id): initialize to 9999.
const bool (restocking): initialize to false.
Constructors
Default constructor: initialize item id and restocking using the default static data with member
initializer syntax.
Non-default constructor: take 2 parameters.
Destructor: output "InventoryItem <item id> with <true/false> restocking destroyed ..."
Public member functions:
mutator/accessor for restocking, item id.
Display : to show InventoryItem item id and restocking (true/false). item id must be displayed as
a 4-digit integer with leading 0s if < 1000.
class Product : derived from InventoryItem class (minimum implementation specified below).
Private member data: name (string), quantity (integer) and price (double).
Public static data:
const string (name): "No Product".
const int (quantity): 0
const double (price): 0.99
Constructors (use member initializer syntax)
Default constructor: set member data to static data's default values above. Must explicitly invoke
the base class' default constructor.
Non-default constructor: take five parameters (id, restocking, name, quantity and price). Must
explicitly invoke the base class' non-default constructor.
Destructor: output "Product: <item id>, Name<name>, quantity<quantity>, price <price>,
restocking<true/false> destroyed ...".
Public member functions:
accessors/mutators for name, quantity, price.
Display: invoke Display from base class, then display its own data. NOTE: If the product
restocking is true somehow indicate it using "special effects" such as ***** or wh.
Program Specifications in c++ Develop an inventory management system f.docxsharold2
Program Specifications in c++
Develop an inventory management system for an electronics store. The inventory system should have the following functionalities:
BuildInventory: read a text file containing electronics products information and dynamically store them in an array of pointers.
ShowInventory: display all inventory items.
UpdateInventory: ask for item id and quantity. If found display cost and update Product object info (reduce Product's quantity and potentially update restocking flag).
Terminate: save current inventory to a text file.
This programming assignment illustrates the following concepts:
Text file reading and writing.
Arrays of pointers and dynamic memory allocations with new and delete.
Inheritance.
C++ type casting: static_cast.
NOTE: This assignment is not about polymorphism or dynamic_cast! Your program should not contain any virtual function and/or use of dynamic_cast mechanism or point deductions will apply. You will have opportunity to use polymorphism in the next assignment.
Class Design
You need at least three classes.
class InventoryItem (minimum implementation specified below) - This is the base class.
Protected member data: item id (integer) and restocking (bool).
Public static data:
const integer (item id): initialize to 9999.
const bool (restocking): initialize to false.
Constructors
Default constructor: initialize item id and restocking using the default static data with member initializer syntax.
Non-default constructor: take 2 parameters.
Destructor: output "InventoryItem <item id> with <true/false> restocking destroyed ..."
Public member functions:
mutator/accessor for restocking, item id.
Display : to show InventoryItem item id and restocking (true/false). item id must be displayed as a 4-digit integer with leading 0s if < 1000.
class Product : derived from InventoryItem class (minimum implementation specified below).
Private member data: name (string), quantity (integer) and price (double).
Public static data:
const string (name): "No Product".
const int (quantity): 0
const double (price): 0.99
Constructors (use member initializer syntax)
Default constructor: set member data to static data's default values above. Must explicitly invoke the base class' default constructor.
Non-default constructor: take five parameters (id, restocking, name, quantity and price). Must explicitly invoke the base class' non-default constructor.
Destructor: output "Product: <item id>, Name<name>, quantity<quantity>, price <price>, restocking<true/false> destroyed ...".
Public member functions:
accessors/mutators for name, quantity, price.
Display: invoke Display from base class, then display its own data. NOTE: If the product restocking is true somehow indicate it using "special effects" such as ***** or whatever effect you'd like.
Cost : take an integer as its only parameter representing the quantity (how many product to be sold) and return the total cost (price * quantity parameter).
class InventorySystem: (minimum implement.
Program Specifications in c++ Develop an inventory management syste.docxsharold2
Program Specifications in c++
Develop an inventory management system for an electronics store. The inventory system should have the following functionalities:
BuildInventory: read a text file containing electronics products information and dynamically store them in an array of pointers.
ShowInventory: display all inventory items.
UpdateInventory: ask for item id and quantity. If found display cost and update Product object info (reduce Product's quantity and potentially update restocking flag).
Terminate: save current inventory to a text file.
This programming assignment illustrates the following concepts:
Text file reading and writing.
Arrays of pointers and dynamic memory allocations with new and delete.
Inheritance.
C++ type casting: static_cast.
NOTE: This assignment is not about polymorphism or dynamic_cast! Your program should not contain any virtual function and/or use of dynamic_cast mechanism or point deductions will apply. You will have opportunity to use polymorphism in the next assignment.
Class Design
You need at least three classes.
class InventoryItem (minimum implementation specified below) - This is the base class.
Protected member data: item id (integer) and restocking (bool).
Public static data:
const integer (item id): initialize to 9999.
const bool (restocking): initialize to false.
Constructors
Default constructor: initialize item id and restocking using the default static data with member initializer syntax.
Non-default constructor: take 2 parameters.
Destructor: output "InventoryItem <item id> with <true/false> restocking destroyed ..."
Public member functions:
mutator/accessor for restocking, item id.
Display : to show InventoryItem item id and restocking (true/false). item id must be displayed as a 4-digit integer with leading 0s if < 1000.
class Product : derived from InventoryItem class (minimum implementation specified below).
Private member data: name (string), quantity (integer) and price (double).
Public static data:
const string (name): "No Product".
const int (quantity): 0
const double (price): 0.99
Constructors (use member initializer syntax)
Default constructor: set member data to static data's default values above. Must explicitly invoke the base class' default constructor.
Non-default constructor: take five parameters (id, restocking, name, quantity and price). Must explicitly invoke the base class' non-default constructor.
Destructor: output "Product: <item id>, Name<name>, quantity<quantity>, price <price>, restocking<true/false> destroyed ...".
Public member functions:
accessors/mutators for name, quantity, price.
Display: invoke Display from base class, then display its own data. NOTE: If the product restocking is true somehow indicate it using "special effects" such as ***** or whatever effect you'd like.
Cost : take an integer as its only parameter representing the quantity (how many product to be sold) and return the total cost (price * quantity parameter).
class InventorySystem: (minimum implement.
The action bar provides consistency across Android apps and allows adding navigation features, search, and other actions. It displays the activity title and app icon. To add an action bar, activities must extend ActionBarActivity if supporting older Android versions, or set the theme if supporting API 11+. Action buttons and menu items are defined in XML and inflated into the action bar. Clicking items calls onOptionsItemSelected() to handle the action. The up button navigates to the parent activity.
Program Specifications Develop an inventory management system for an e.docxVictormxrPiperc
Program Specifications
Develop an inventory management system for an electronics store. The inventory system should have the following functionalities:
BuildInventory: read a text file containing electronics products information and dynamically store them in an array of pointers.
ShowInventory: display all inventory items.
UpdateInventory: ask for item id and quantity. If found display cost and update Product object info (reduce Product's quantity and potentially update restocking flag).
Terminate: save current inventory to a text file.
This programming assignment illustrates the following concepts:
Text file reading and writing.
Arrays of pointers and dynamic memory allocations with new and delete.
Inheritance.
C++ type casting: static_cast.
NOTE: This assignment is not about polymorphism or dynamic_cast! Your program should not contain any virtual function and/or use of dynamic_cast mechanism or point deductions will apply. You will have opportunity to use polymorphism in the next assignment.
Class Design
You need at least three classes.
class InventoryItem (minimum implementation specified below) - This is the base class.
Protected member data: item id (integer) and restocking (bool).
Public static data:
const integer (item id): initialize to 9999.
const bool (restocking): initialize to false.
Constructors
Default constructor: initialize item id and restocking using the default static data with member initializer syntax.
Non-default constructor: take 2 parameters.
Destructor: output "InventoryItem <item id> with <true/false> restocking destroyed ..."
Public member functions:
mutator/accessor for restocking, item id.
Display : to show InventoryItem item id and restocking (true/false). item id must be displayed as a 4-digit integer with leading 0s if < 1000.
class Product : derived from InventoryItem class (minimum implementation specified below).
Private member data: name (string), quantity (integer) and price (double).
Public static data:
const string (name): "No Product".
const int (quantity): 0
const double (price): 0.99
Constructors (use member initializer syntax)
Default constructor: set member data to static data's default values above. Must explicitly invoke the base class' default constructor.
Non-default constructor: take five parameters (id, restocking, name, quantity and price). Must explicitly invoke the base class' non-default constructor.
Destructor: output "Product: <item id>, Name<name>, quantity<quantity>, price <price>, restocking<true/false> destroyed ...".
Public member functions:
accessors/mutators for name, quantity, price.
Display: invoke Display from base class, then display its own data. NOTE: If the product restocking is true somehow indicate it using "special effects" such as ***** or whatever effect you'd like.
Cost : take an integer as its only parameter representing the quantity (how many product to be sold) and return the total cost (price * quantity parameter).
class InventorySystem: (minimum implementation s.
Symfony can be used to create an ecommerce app. You can also easily integrate ReactJS on the front-end of your Symfony ecommerce app and use Cloudinary for storing images.
Green Lantern Framework with Selenium IDESrilu Balla
This document describes a framework called Green Lantern for creating automated tests that are resilient to user interface changes. It involves naming elements on web pages with a consistent convention, storing test data separately, and taking screenshots at each step to log results. The framework allows test scripts to be reused across similar applications. It also simplifies updating scripts when interfaces change by focusing updates in element repositories rather than throughout scripts. The document provides detailed instructions for setting up projects using the framework with examples for testing Gmail, Netflix, and Yahoo login pages.
This document provides an overview of building Lightning components in Salesforce. It discusses setting up the development environment, creating an Aura-enabled Apex controller, and building the core components of an account locator app including AccountList, AccountMap, and handling intercomponent communication. Key aspects covered include loading external libraries, iterating over data, firing custom events, and integrating with the Salesforce1 mobile app. The goal is to create a reusable AccountLocator component that displays a map and list of accounts, centers the map on selection, and loads account details in Salesforce1.
This document describes the steps to create a salary advance workflow in SharePoint using Visual Studio. The workflow allows employees to request a salary advance, which is then sent to the accounts department for approval or rejection. Key steps include:
1. Creating a new SharePoint project in Visual Studio and defining the URL of the associated web application and list.
2. Adding a sequential workflow and associating it with the salary advance list.
3. Defining a while loop to hold recurring activities until workflow completion.
4. Adding if/else branches for approved, rejected, and initiated statuses and activities like logging, emailing, and terminating the workflow.
5. Populating the if conditions and branches
Supercharge Your Pages - New Ways to Extend the Confluence EditorAtlassian
The new Confluence editor brings never before seen capabilities to our developers to extend the editor. During this session, Klaus Ihlberg will explain how users use Confluence today and how to use this information and the new capabilities, to develop apps that supercharge Confluence pages.
Lab: Mobile App Development with XPages and Extension LibraryWorkFlowStudios
The document describes creating a mobile application using XPages to view movies and actors from an existing Notes database. It involves modeling the mobile page flow with main and detail pages, creating the pages using Mobile Page controls, and adding views and panels to display the movie and actor data. Tapping a movie in the list transitions to a new page displaying that movie's actors, fetched via lookups to the underlying Notes documents.
The Green Lantern Framework provides a standardized way to automate regression tests across applications with changing UIs. It involves capturing UI elements, renaming them with English aliases, categorizing the elements, and writing scripts that use the aliases. This allows scripts to be reused across similar applications by changing the alias mappings as needed. It provides more maintainable, reusable automation than traditional record-and-play tools that break with any UI changes.
The document discusses concepts and best practices for building single page applications (SPAs) using a component-based architecture. Everything the user interacts with should be a component. Components should be based on state rather than modifying the DOM directly. Data fetching conventions include matching API endpoints to serializers and actions. Services discussed include a dispatcher, store, and mixins for handling actions, managing component scopes, and fetching additional API data.
For the first time, 'WordPress-Trivandrum' had a Live Demo Session.
WordPress is not just about blogging. We’ve experienced e-commerce and social media revolution. It's time for another one, the Internet of Things or IoT. There are a handful of automation plugins and services available for WordPress and the number is about to grow. In this session, we will have a look at what we can do with WordPress for connecting our website to real-world Things – "The Internet of Things".
Key focus:-
• Google Assistant
• Amazon Alexa
• IFTTT
• Philips Hue
• Arduino
• Raspberry Pi
Live Demos: -
• Get a Light flashing when someone comments in posts
• Get an Alert sound when you receive an order in your shop
• Add photos to the Photo Gallery whenever you post it in Instagram
• Ask Google Assistant to create a new post
• Get an alert when someone submits a custom web form you created
The document discusses various Android widgets such as TextView, ImageView, EditText, CheckBox, and RadioButton. It provides code examples for how to implement each widget in an Android application. For TextView, it demonstrates how to display simple text. For ImageView, it shows how to display an image. For EditText, it explains how to create an editable text field. For CheckBox, it provides an example of a checkbox that can be checked or unchecked. And for RadioButton, it discusses using radio buttons within a RadioGroup so that only one can be selected at a time.
The document provides tips for finding resources in the Eclipse workspace using a visitor. It describes creating a class that implements IResourceProxyVisitor and overriding the visit() method. This method would check each resource proxy for a match to the location string and return the resource if found. This allows recursively searching the workspace to locate a resource based on its path or other identifier.
Slides for the hands on lightning component workshop that is accompanying the trailhead found https://developer.salesforce.com/trailhead/project/account-geolocation-app
This document provides tips and tricks for Odoo development. It discusses module structure, creating new tables and inheriting existing tables, creating menu items and CRUD for models, creating master-detail relationships between models, creating models from multiple models using queries, creating buttons that trigger actions, sending emails via API using email templates, and creating job schedules using automated actions.
The document discusses the Controls object in Microsoft Small Basic, which allows adding controls like text boxes and buttons to the graphics window. It describes various operations and properties of the Controls object, such as AddTextBox to add a text box, GetTextBoxText to retrieve text from a text box, and ButtonClicked and TextTyped events. Control events can generate actions when a button is clicked or text is typed in a text box. The document provides an example of a program that uses the Controls object and ends by asking the reader to write a program to display a simple form with text boxes and a submit button.
The document discusses Quick Test Professional (QTP) user-defined functions. It covers:
- Creating public and private functions associated with test objects or globally
- Registering public functions to test objects using the Function Definition Generator
- Adding registered functions as steps in tests by selecting the test object and registered operation
A quick run through explaining actions and filters that are used throughout WordPress (with useful metaphors) and some examples. It is intended to demonstrate that actions and filters are not as scary as people might think and that they can very easily make significant changes with only a few lines of code.
This is the workshop presentation material for the Lightning Components Hands-On Workshop (HOW) being presented at Dreamforce 2015 in the DevZone. This content pairs with the Lightning Components Trailhead project live in Trailhead as of Dreamforce 2015.
show code and all classes with full implementation for these Program S.pdfAlanSmDDyerl
show code and all classes with full implementation for these Program Specifications.
Example products ( camcorder, dvd player, blueray player, tv, camera, xbox 360, ps4, Wii,
laptops, iphone, battery, smart phones, computer desktop, printer, usb, mouse)
Develop an inventory management system for an electronics store. The inventory system should
have the following functionalities:
BuildInventory: read a text file containing electronics products information and dynamically
store them in an array of pointers.
ShowInventory: display all inventory items.
UpdateInventory: ask for item id and quantity. If found display cost and update Product object
info (reduce Product's quantity and potentially update restocking flag).
Terminate: save current inventory to a text file.
This programming assignment illustrates the following concepts:
Text file reading and writing.
Arrays of pointers and dynamic memory allocations with new and delete.
Inheritance.
C++ type casting: static_cast.
NOTE: This assignment is not about polymorphism or dynamic_cast! Your program should not
contain any virtual function and/or use of dynamic_cast mechanism or point deductions will
apply. You will have opportunity to use polymorphism in the next assignment.
Class Design
You need at least three classes.
class InventoryItem (minimum implementation specified below) - This is the base class.
Protected member data: item id (integer) and restocking (bool).
Public static data:
const integer (item id): initialize to 9999.
const bool (restocking): initialize to false.
Constructors
Default constructor: initialize item id and restocking using the default static data with member
initializer syntax.
Non-default constructor: take 2 parameters.
Destructor: output "InventoryItem <item id> with <true/false> restocking destroyed ..."
Public member functions:
mutator/accessor for restocking, item id.
Display : to show InventoryItem item id and restocking (true/false). item id must be displayed as
a 4-digit integer with leading 0s if < 1000.
class Product : derived from InventoryItem class (minimum implementation specified below).
Private member data: name (string), quantity (integer) and price (double).
Public static data:
const string (name): "No Product".
const int (quantity): 0
const double (price): 0.99
Constructors (use member initializer syntax)
Default constructor: set member data to static data's default values above. Must explicitly invoke
the base class' default constructor.
Non-default constructor: take five parameters (id, restocking, name, quantity and price). Must
explicitly invoke the base class' non-default constructor.
Destructor: output "Product: <item id>, Name<name>, quantity<quantity>, price <price>,
restocking<true/false> destroyed ...".
Public member functions:
accessors/mutators for name, quantity, price.
Display: invoke Display from base class, then display its own data. NOTE: If the product
restocking is true somehow indicate it using "special effects" such as ***** or wh.
Program Specifications in c++ Develop an inventory management system f.docxsharold2
Program Specifications in c++
Develop an inventory management system for an electronics store. The inventory system should have the following functionalities:
BuildInventory: read a text file containing electronics products information and dynamically store them in an array of pointers.
ShowInventory: display all inventory items.
UpdateInventory: ask for item id and quantity. If found display cost and update Product object info (reduce Product's quantity and potentially update restocking flag).
Terminate: save current inventory to a text file.
This programming assignment illustrates the following concepts:
Text file reading and writing.
Arrays of pointers and dynamic memory allocations with new and delete.
Inheritance.
C++ type casting: static_cast.
NOTE: This assignment is not about polymorphism or dynamic_cast! Your program should not contain any virtual function and/or use of dynamic_cast mechanism or point deductions will apply. You will have opportunity to use polymorphism in the next assignment.
Class Design
You need at least three classes.
class InventoryItem (minimum implementation specified below) - This is the base class.
Protected member data: item id (integer) and restocking (bool).
Public static data:
const integer (item id): initialize to 9999.
const bool (restocking): initialize to false.
Constructors
Default constructor: initialize item id and restocking using the default static data with member initializer syntax.
Non-default constructor: take 2 parameters.
Destructor: output "InventoryItem <item id> with <true/false> restocking destroyed ..."
Public member functions:
mutator/accessor for restocking, item id.
Display : to show InventoryItem item id and restocking (true/false). item id must be displayed as a 4-digit integer with leading 0s if < 1000.
class Product : derived from InventoryItem class (minimum implementation specified below).
Private member data: name (string), quantity (integer) and price (double).
Public static data:
const string (name): "No Product".
const int (quantity): 0
const double (price): 0.99
Constructors (use member initializer syntax)
Default constructor: set member data to static data's default values above. Must explicitly invoke the base class' default constructor.
Non-default constructor: take five parameters (id, restocking, name, quantity and price). Must explicitly invoke the base class' non-default constructor.
Destructor: output "Product: <item id>, Name<name>, quantity<quantity>, price <price>, restocking<true/false> destroyed ...".
Public member functions:
accessors/mutators for name, quantity, price.
Display: invoke Display from base class, then display its own data. NOTE: If the product restocking is true somehow indicate it using "special effects" such as ***** or whatever effect you'd like.
Cost : take an integer as its only parameter representing the quantity (how many product to be sold) and return the total cost (price * quantity parameter).
class InventorySystem: (minimum implement.
Program Specifications in c++ Develop an inventory management syste.docxsharold2
Program Specifications in c++
Develop an inventory management system for an electronics store. The inventory system should have the following functionalities:
BuildInventory: read a text file containing electronics products information and dynamically store them in an array of pointers.
ShowInventory: display all inventory items.
UpdateInventory: ask for item id and quantity. If found display cost and update Product object info (reduce Product's quantity and potentially update restocking flag).
Terminate: save current inventory to a text file.
This programming assignment illustrates the following concepts:
Text file reading and writing.
Arrays of pointers and dynamic memory allocations with new and delete.
Inheritance.
C++ type casting: static_cast.
NOTE: This assignment is not about polymorphism or dynamic_cast! Your program should not contain any virtual function and/or use of dynamic_cast mechanism or point deductions will apply. You will have opportunity to use polymorphism in the next assignment.
Class Design
You need at least three classes.
class InventoryItem (minimum implementation specified below) - This is the base class.
Protected member data: item id (integer) and restocking (bool).
Public static data:
const integer (item id): initialize to 9999.
const bool (restocking): initialize to false.
Constructors
Default constructor: initialize item id and restocking using the default static data with member initializer syntax.
Non-default constructor: take 2 parameters.
Destructor: output "InventoryItem <item id> with <true/false> restocking destroyed ..."
Public member functions:
mutator/accessor for restocking, item id.
Display : to show InventoryItem item id and restocking (true/false). item id must be displayed as a 4-digit integer with leading 0s if < 1000.
class Product : derived from InventoryItem class (minimum implementation specified below).
Private member data: name (string), quantity (integer) and price (double).
Public static data:
const string (name): "No Product".
const int (quantity): 0
const double (price): 0.99
Constructors (use member initializer syntax)
Default constructor: set member data to static data's default values above. Must explicitly invoke the base class' default constructor.
Non-default constructor: take five parameters (id, restocking, name, quantity and price). Must explicitly invoke the base class' non-default constructor.
Destructor: output "Product: <item id>, Name<name>, quantity<quantity>, price <price>, restocking<true/false> destroyed ...".
Public member functions:
accessors/mutators for name, quantity, price.
Display: invoke Display from base class, then display its own data. NOTE: If the product restocking is true somehow indicate it using "special effects" such as ***** or whatever effect you'd like.
Cost : take an integer as its only parameter representing the quantity (how many product to be sold) and return the total cost (price * quantity parameter).
class InventorySystem: (minimum implement.
The action bar provides consistency across Android apps and allows adding navigation features, search, and other actions. It displays the activity title and app icon. To add an action bar, activities must extend ActionBarActivity if supporting older Android versions, or set the theme if supporting API 11+. Action buttons and menu items are defined in XML and inflated into the action bar. Clicking items calls onOptionsItemSelected() to handle the action. The up button navigates to the parent activity.
Program Specifications Develop an inventory management system for an e.docxVictormxrPiperc
Program Specifications
Develop an inventory management system for an electronics store. The inventory system should have the following functionalities:
BuildInventory: read a text file containing electronics products information and dynamically store them in an array of pointers.
ShowInventory: display all inventory items.
UpdateInventory: ask for item id and quantity. If found display cost and update Product object info (reduce Product's quantity and potentially update restocking flag).
Terminate: save current inventory to a text file.
This programming assignment illustrates the following concepts:
Text file reading and writing.
Arrays of pointers and dynamic memory allocations with new and delete.
Inheritance.
C++ type casting: static_cast.
NOTE: This assignment is not about polymorphism or dynamic_cast! Your program should not contain any virtual function and/or use of dynamic_cast mechanism or point deductions will apply. You will have opportunity to use polymorphism in the next assignment.
Class Design
You need at least three classes.
class InventoryItem (minimum implementation specified below) - This is the base class.
Protected member data: item id (integer) and restocking (bool).
Public static data:
const integer (item id): initialize to 9999.
const bool (restocking): initialize to false.
Constructors
Default constructor: initialize item id and restocking using the default static data with member initializer syntax.
Non-default constructor: take 2 parameters.
Destructor: output "InventoryItem <item id> with <true/false> restocking destroyed ..."
Public member functions:
mutator/accessor for restocking, item id.
Display : to show InventoryItem item id and restocking (true/false). item id must be displayed as a 4-digit integer with leading 0s if < 1000.
class Product : derived from InventoryItem class (minimum implementation specified below).
Private member data: name (string), quantity (integer) and price (double).
Public static data:
const string (name): "No Product".
const int (quantity): 0
const double (price): 0.99
Constructors (use member initializer syntax)
Default constructor: set member data to static data's default values above. Must explicitly invoke the base class' default constructor.
Non-default constructor: take five parameters (id, restocking, name, quantity and price). Must explicitly invoke the base class' non-default constructor.
Destructor: output "Product: <item id>, Name<name>, quantity<quantity>, price <price>, restocking<true/false> destroyed ...".
Public member functions:
accessors/mutators for name, quantity, price.
Display: invoke Display from base class, then display its own data. NOTE: If the product restocking is true somehow indicate it using "special effects" such as ***** or whatever effect you'd like.
Cost : take an integer as its only parameter representing the quantity (how many product to be sold) and return the total cost (price * quantity parameter).
class InventorySystem: (minimum implementation s.
The document describes how to use the vtlib API to customize vtiger CRM. It provides examples for creating modules, tabs, blocks, fields, custom views, and enabling/disabling actions. The vtlib API allows easier development by automating common customization tasks like creating a new "Payslip" module with the necessary database tables, fields, and views. Test scripts demonstrate how to execute the API functions to fully create custom modules.
The document discusses various techniques for optimizing Django ORM queries to improve performance, including:
1. Using bulk_create, update, and transaction.atomic to perform bulk operations in a single query instead of multiple queries.
2. Prefetching related objects and selecting related fields to avoid N+1 queries when accessing related data.
3. Filtering and ordering prefetched querysets to further optimize related data retrieval.
4. Encapsulating optimizations like select_related in custom model managers to apply them automatically.
The key is to minimize the number of database hits by performing operations in bulk where possible instead of one-by-one. Selecting related fields, prefetching, and
Cis407 a ilab 6 web application development devry universitylhkslkdh89009
This document provides instructions for an iLab assignment to create a login form for a web application. Students are asked to:
1. Create a login form that validates username and password and assigns a session variable for the user's security level.
2. Restrict access to certain functions on an existing form based on the security level.
3. Add a user management form to allow adding, editing, and removing users, and testing the login and security functionality.
The assignment involves adding authentication code, restricting page elements based on roles, and creating a user database interface form. Students are provided detailed steps and advised to add comments to their code.
Practical Google App Engine Applications In PyEric ShangKuan
The document discusses techniques for building efficient applications on Google App Engine. It covers optimizing data storage and queries using the datastore, improving performance through caching and entity grouping, and techniques like zipimport and zipserve to work around file limits. Key recommendations include minimizing datastore calls, avoiding heavily indexing properties, rebinding query objects, and caching frequently accessed data in memcache.
Educate 2017: Customizing Assessments: Why extending the APIs is easier than ...Learnosity
Watch the video of this presentation: https://youtu.be/vevmhMXfiOU?t=1s
Learnosity is designed to support creative and powerful assessment building. So if you’ve ever looked on in envy or frustration at a competitor’s super-sleek assessment solution, then it’s time to rekindle your creative fire.
By quickly building professional-quality assessments using Learnosity’s tools, we’ll show how you can easily tailor every aspect of your assessment experience to make your end product just as polished, stylish and powerful as anything else on the market. But why make your assessments as good as what’s already out there when you can just as easily make them even better?
Using prime[31] to connect your unity game to azure mobile servicesDavid Voyles
Using prime[31] to connect your unity game to azure mobile services. More info at my blog: http://davevoyles.azurewebsites.net/prime31-azure-plugin-win8-wp8-unity-games-part-3/
need help completing week 6 ilab.. i will upload what I currently ha.docxniraj57
need help completing week 6 ilab.. i will upload what I currently have if you know the material please let me know. what the person to add on to what I currently have started.
iLab 6 of 7: Login and Security Levels (30 Points)
Submit your assignment to the Dropbox located on the silver tab at the top of this page.
(See Syllabus "Due Dates for Assignments & Exams" for due dates.)
i L A B O V E R V I E W
Scenario/Summary
In this week's lab, we will create a login form, validate a user based on their login name and password, and allow them to access the system or not. We will assign a session variable to determine the level of security the user has and allow certain functions to be displayed or not displayed in the existing frmPersonnel form depending on the assigned security level. (NOTE: In some cases the instructions for this lab will be less specific than in earlier labs, because you are expected to apply what you have learned in earlier weeks. Refer to the detailed instructions in previous weeks' labs if you need to do so.)
Instructions for Week 6 iLab: Login and Security Levels
Click on the link above to view the tutorial.
Please watch this tutorial before beginning the iLab.
The tutorial has audio.
Deliverables
When you try to log in, if you use User Name = Mickey and Password = Mouse, the frmMain form should open with all links visible. If you use User Name = Minnie and Password = Mouse, the frmMain form should open with only the Salary Calculator, View Personnel, and Search options should be available. You will have a new option called Manage Users that will allow you to add new users and remove or update existing users. Once you have verified that it works, save your website, zip up all files, and submit in the Dropbox.
Note on database connections: We are using a SQLDataSource control for the Edit employees feature we added. You should be using the connection string stored in the web.config file for your database connection for this control. Rather than creating a new connection each time, just use this connection. If you change the folder where your website is (e.g., you copy each week's work to a new location), you will need to update the web.config. The advantage of using the database connection in the web.config is that you only have to set the configuration in one location.
Before starting this week's lab, make sure everything is working and that all database connections are properly configured.
i L A B S T E P S
STEP 1: Login Form (10 points)
Open Microsoft Visual Studio.NET 2008.
Click the ASP.NET website named PayrollSystem to open it.
Create a new web form named frmLogin.
Drop a login control onto the form.
Set the properties of the login control as follows:
PROPERTY
VALUE
DestinationPageUrl
frmMain.aspx
TitleText
Please enter your UserName and Password in order to log into the system
Add the
Cool
Biz
Productions
, Inc.
logo to the frmLogin form. Do not hylerlink the logo.
Highlight everything in the form, then c.
The document provides instructions for a Google Wave workshop on building interactive gadgets and robots. The workshop covers getting started with Google Wave, downloading necessary files, building a simple voting gadget to demonstrate core gadget functionality, and building an interactive robot using the Google App Engine and Wave Robot API. Attendees will learn how to add external CSS and JavaScript, store and retrieve state data, and set callback functions to update gadgets in real-time in response to events.
XML is a markup language that allows users to define their own tags and structure for documents. It separates content from formatting and is extensible, platform-independent, and human-readable. Well-formed XML documents follow syntax rules like having matching open and close tags and properly nested elements. Valid XML documents also comply with constraints defined in their associated DTD. Common XML components include elements, attributes, namespaces, comments, and CDATA sections.
This document provides an overview of XML (Extensible Markup Language) including:
- The basic structure and components of an XML document including elements, attributes, entities, and advanced components.
- An example well-commented XML document.
- The basic rules for creating a well-formed XML document including being case sensitive, requiring start and end tags, proper nesting, and more.
- Common errors in element naming and how to avoid them.
- How to walk through modifying an example XML document to add new elements and ensure it remains well-formed.
XML (Extensible Markup Language) allows users to define their own customized markup languages to structure data. It was created as a simplified version of SGML to make it usable on the web. XML is important because it removes constraints of HTML and allows for richer content than HTML alone. XML will enable easier exchange of data between businesses and applications.
XML is a markup language that allows users to define their own tags and structure for documents. It separates content from formatting and is extensible, platform-independent, and human-readable. Well-formed XML documents follow syntax rules like having matching open and close tags and properly nested elements. Valid XML documents also comply with constraints defined in their associated DTD. Common XML components include elements, attributes, namespaces, comments, and CDATA sections.
This document provides an overview of XML (Extensible Markup Language) including:
- The basic structure and components of an XML document including elements, attributes, entities, and advanced components.
- An example well-commented XML document.
- The basic rules for creating a well-formed XML document including being case sensitive, requiring start and end tags, proper nesting, and more.
- Common errors in element naming and how to avoid them.
- How to add new elements and attributes to an example XML document to ensure it remains well-formed.
XML stands for Extensible Markup Language and is used to mark up data so it can be processed by computers, whereas HTML is used to mark up text to be displayed for users. Both XML and HTML use elements enclosed in tags, attributes, and entities, but XML only describes content while HTML describes both structure and appearance. XML allows users to define their own tags, and is strictly structured, making it suitable for data processing by computers.
This document provides an overview of XML, including its basic structure and components. XML documents use elements to structure and tag content. Elements must be properly nested within a single root element and can have attributes. The relationships between these elements form a tree structure. XML documents also support comments, processing instructions, and character encoding. CSS and XSLT can be used to display and transform XML for web users. While databases are better for structured data, XML is well suited for loosely structured or large records.
The document provides an introduction to shell scripting basics in UNIX/Linux. It discusses what a shell and shell script are, introduces the popular bash shell, and covers running commands, variables, logic, and other shell scripting concepts. The key points covered include:
- A shell is a program that takes commands and runs other programs. Popular shells include bash, csh, tcsh, and ksh.
- A shell script is a text file containing shell commands that is executable. Creating and running a simple "Hello world" script is demonstrated.
- Running commands, pipes, redirection, variables, logic, and flow control like if/else, for loops are explained.
- Useful bash
This document provides an introduction and overview of the Unix operating system. It covers topics such as getting help, the file system, the shell, network security, email clients, text editors, input/output redirection, printing, process management, and the X window system. The document is intended to help new Unix users understand basic Unix concepts and commands.
Linux is an open source operating system created by Linus Torvalds in 1991. It uses a Linux kernel and includes many common Unix tools. Linux is free to use and modify due to its open source licensing. It runs on many hardware platforms and is growing in popularity for servers, desktops, and embedded systems due to its low cost, stability, and security. Users can download Linux from distributions like Red Hat which package the Linux kernel with additional software and support.
After completing this section, students should be able to log into the Linux system, understand and manipulate the UNIX file system, describe the role of the shell, use basic file commands like cd, ls, cp, and rm, use standard input/output and piping, and understand the UNIX philosophy. The document provides an introduction to UNIX operating systems, shells, file systems, basic commands, and input/output redirection.
This document provides an overview of the C programming language, including its history, characteristics, and syntax. C was developed in the 1970s alongside Unix and became widely used for system programming. It allows for close interaction with the operating system and hardware. The document walks through a simple "Hello World" program to demonstrate C's syntax, including preprocessing, compilation, linking, and execution. It also provides a more complex guessing game example to illustrate additional C language features like variables, operators, conditionals, and loops.
This document provides an introduction to the C programming language. It discusses key concepts like functions, variables, data types, memory, scopes, expressions, operators, control flow with if/else statements and loops. It also explains how passing arguments by value means functions cannot directly modify their parameters, but passing addresses allows modifying variables in the calling scope. Overall it serves as a helpful primer on basic C syntax and programming concepts for newcomers to the language.
This document provides an overview of introductory concepts in C programming, including simple programs to print text and perform arithmetic. It covers basic syntax like comments, functions, variables, data types, operators, input/output, and conditional statements. Memory concepts are introduced, as well as the preprocessor, standard libraries, and control flow structures like if/else. Examples are provided to demonstrate printing text, taking user input, performing calculations, and making decisions based on relational comparisons.
This document provides an introduction to C programming over 13 pages. It covers the purpose and schedule of the lectures, differences between C and Java, C program structure, keywords, variables, data types, and more. The main points are that the lectures will provide a crash course in C with an emphasis on differences from Java, cover practical examples and topics related to C programming, and include history, language overview, pointers, memory management, compiling and debugging.
This document provides an introduction to programming in C. It begins by discussing computers, hardware, software, data, and information processing. It then discusses what programming is and how to approach solving problems through programming. The document outlines the major components of a C program and provides a first example program. It also covers key C programming concepts like variables, data types, expressions, control flow, functions, pointers, arrays, strings, structures, files and memory allocation. The document is intended to introduce readers to programming in C from a high level.
The document provides an overview of the C programming language. It begins with a brief history of C and how it evolved from the B programming language to support UNIX. It describes C as a systems programming language that is close to hardware but with higher-level constructs than assembly. The rest of the document outlines key C language concepts like data types, variables, operators, functions, and control structures. It provides examples of how to use basic programming elements like if/else statements and switch statements.
This document contains repeated text about printing or viewing notes pages for a preface rather than slides. It provides instructions to print or view notes pages for a preface section eight separate times without any other notable information.
This document provides an overview and objectives for a course on Oracle database administration. It covers topics such as controlling user access, managing schema objects, manipulating large data sets, generating reports, managing data in different time zones, retrieving data using subqueries, hierarchical retrieval, and regular expression support. Each chapter provides learning objectives and exercises for students to reinforce the concepts covered.
Regular expressions can be used in SQL to search, match, and replace strings. Key regular expression functions include REGEXP_INSTR, REGEXP_SUBSTR, and REGEXP_REPLACE. Meta characters like *, +, and [] are used to define patterns to match. For example, 'a+' would match one or more occurrences of 'a' in a string.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Infrastructure Challenges in Scaling RAG with Custom AI modelsZilliz
Building Retrieval-Augmented Generation (RAG) systems with open-source and custom AI models is a complex task. This talk explores the challenges in productionizing RAG systems, including retrieval performance, response synthesis, and evaluation. We’ll discuss how to leverage open-source models like text embeddings, language models, and custom fine-tuned models to enhance RAG performance. Additionally, we’ll cover how BentoML can help orchestrate and scale these AI components efficiently, ensuring seamless deployment and management of RAG systems in the cloud.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
AI 101: An Introduction to the Basics and Impact of Artificial IntelligenceIndexBug
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
11. LOVs and Buttons IF SHOW_LOV(’myLov’) THEN... When-Button-Pressed Name Roel Glenn Gary Michael Jeff Lynn Kate Patrice Pam ID 101 102 103 104 105 106 107 108 109 105 Employees (LOV) 105 Employee_Id LOV button
12.
13. Populating Image Items v ^ Database Fetch on query Image file (in the application server file system) WRITE_IMAGE_FILE READ_IMAGE_FILE
14.
15. Loading the Right Image READ_IMAGE_FILE (TO_CHAR(:ORDER_ITEMS.product_id)||’.JPG’, ’ JPEG’,’ORDER_ITEMS.product_image’ ); READ_IMAGE_FILE Image file in the application server file system
16. Populating Hierarchical Trees SET_TREE_PROPERTY Database When-Button-Pressed CREATE_GROUP_FROM_QUERY Record Group Car Ford Volvo VW Toyota -
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
Editor's Notes
Introduction Overview In this lesson, you will learn how to use triggers to provide additional functionality to GUI items in form applications.
Item Interaction Triggers There are several types of GUI items that the user can interact with by using the mouse or by pressing a function key. Most of these items have default functionality. For example, by selecting a radio button, the user can change the value of the radio group item. You will often want to add triggers to provide customized functionality when these events occur. For example: Performing tests and appropriate actions as soon as the user clicks a radio button, a list, or a check box Conveniently displaying an image when the user clicks an image item Defining the functionality of a push-button (which has none until you define it)
Item Interaction Triggers (continued) The following triggers fire due to user interaction with an item, as previously described. They can be defined at any scope.
Command Types in Item Interaction Triggers You can use standard SQL and PL/SQL statements in these triggers, like the example on the next page. However, you will often want to add functionality to items by calling built-in subprograms, which provide a wide variety of mechanisms. Although Forms allows you to use DML ( INSERT , UPDATE , or DELETE ) statements in any trigger, it is best to use them in commit triggers only. Otherwise the DML statements are not included in the administration kept by Forms concerning commit processing. This may lead to unexpected and unwanted results. You learn about commit triggers in Lesson 21. Note: During an unhandled exception, the trigger terminates and sends the Unhandled Exception message to the operator. The item interaction triggers do not fire on navigation or validation events.
Command Types in Item Interaction Triggers (continued) Example of When-Radio-Changed When-Radio-Changed trigger on :CUSTOMERS.Credit_Limit . When the user changes the credit limit, this trigger immediately confirms whether the customer has outstanding orders exceeding the new credit limit. If so, a message warns the user. DECLARE n NUMBER; v_unpaid_orders NUMBER; BEGIN SELECT SUM(nvl(unit_price,0)*nvl(quantity,0)) INTO v_unpaid_orders FROM orders o, order_items i WHERE o.customer_id = :customers.customer_id AND o.order_id = i.order_id -- Unpaid credit orders have status between 4 and 9 AND (o.order_status > 3 AND o.order_status < 10); IF v_unpaid_orders > :customers.credit_limit THEN n := SHOW_ALERT('credit_limit_alert'); END IF; END; Note: Displaying alerts is discussed in the next lesson.
Defining Functionality for Input Items You have already seen an example of adding functionality to radio groups; we now look at adding functionality to other items that accept user input. Check Boxes When the user selects or clears a check box, the associated value for the state is set. You may want to perform trigger actions based on this change. Note that the CHECKBOX_CHECKED function enables you to test the state of a check box without needing to know the associated values for the item. Example The When-Checkbox-Changed trigger (shown in the slide) on the :CONTROL.Case_Sensitive item enables a query to be executed without regard to case if the box is not checked.
List Items You can use the When-List-Changed trigger to trap user selection of a list value. For Tlists, you can trap double-clicks with When-List-Activated. With Forms Builder, you can also change the selectable elements in a list as follows: Periodically update the list from a two-column record group. Add or remove individual list elements through the ADD_LIST_ELEMENT and DELETE_LIST_ELEMENT built-ins, respectively: ADD_LIST_ELEMENT(’list_item_name’, index,’label’,’value’); DELETE_LIST_ELEMENT(’list_item_name’,index); Note: You can eliminate the Null list element of a list by setting Required to Yes. At run time, when the block contains queried or changed records Forms may not allow you to add or delete elements from a list item.
Defining Functionality for Noninput Items Displaying LOVs from Buttons If you have attached an LOV to a text item, then the user can invoke the LOV from the text item by selecting Edit > Display List or pressing the List Values key. However, it is always useful if a button is available to display an LOV. The button has two advantages: It is convenient alternative for accessing the LOV. It displays an LOV independently of a text item (using SHOW_LOV ). There are two built-ins that you can call to invoke a LOV from a trigger. These are LIST_VALUES and SHOW_LOV . LIST_VALUES Procedure This built-in procedure invokes the LOV that is attached to the current text item in the form. It has an optional argument, which may be set to RESTRICT , meaning that the current value of the text item is used as the initial search string on the LOV. The default for this argument is NO_RESTRICT .
Defining Functionality for Noninput Items (continued) SHOW_LOV Function This built-in function, without arguments, invokes the LOV of the current item. However, there are arguments that let you define which LOV is to be displayed, and what the x and y coordinates are where its window should appear: SHOW_LOV( ’lov_name’, x, y ) SHOW_LOV( lov_id, x, y ) You should note that either the LOV name (in quotes) or the LOV ID (without quotes) can be supplied in the first argument. Note: The lov_id is a PL/SQL variable where the internal ID of the object is stored. Internal IDs are a more efficient way of identifying an object.
Using the SHOW_LOV Function The SHOW_LOV function returns a Boolean value: TRUE indicates that the user selected a record from the LOV. FALSE indicates that the user dismissed the LOV without choosing a record, or that the LOV returned 0 records from its Record Group. Note You can use the FORM_SUCCESS function to differentiate between the two causes of SHOW_LOV returning FALSE . Create the LOV button with a suitable label, such as “Pick,” and arrange it on the canvas where the user intuitively associates it with the items that the LOV supports (even though the button has no direct connection with text items). This is usually adjacent to the main text item that the LOV returns a value to. You can use the SHOW_LOV function to display a LOV that is not even attached to a text item, providing that you identify the LOV in the first argument of the function. When called from a button, this invokes the LOV to be independent of cursor location.
Using the SHOW_LOV Function (continued) Switch off the button’s Mouse Navigate property of the button. When using LIST_VALUES , the cursor needs to reside in the text item that is attached to the LOV. With SHOW_LOV , this also maintains the cursor to in its original location after the LOV is closed, wherever that may be. Example This When-Button-Pressed trigger on the Customer_Lov_Button invokes an LOV in a PL/SQL loop, until the function returns TRUE. Because SHOW_LOV returns TRUE when the user selects a record, the LOV redisplays until they do so. LOOP EXIT WHEN SHOW_LOV( ’customer_lov’ ); MESSAGE(’You must select a value from list’); END LOOP;
Image Items Image items that have the Database Item property set to Yes automatically populate in response to a query in the owning block (from a LONG RAW or BLOB column in the base table). Nonbase table image items, however, need to be populated by other means. For example, from an image file in the file system: READ_IMAGE_FILE built-in procedure. You might decide to populate an image item from a button trigger, using When-Button-Pressed, but there are two triggers that fire when the user interacts with an image item directly: When-Image-Pressed (fires for a single click on image item) When-Image-Activated (fires for a double-click on image item) Note: The READ_IMAGE_FILE built-in procedure loads an image file from the application server file system. If you need to load an image file from the file system on the client, use a JavaBean.
Image Items (continued) READ_IMAGE_FILE Procedure This built-in procedure lets you load an image file, in a variety of formats, into an image item. READ_IMAGE_FILE(’filename’,’filetype’,’item_name’); Note The filetype parameter is optional in READ_IMAGE_FILE . If you omit filetype , you must explicitly identify the item_name parameter. The reverse procedure, WRITE_IMAGE_FILE , is also available. The WRITE_IMAGE_FILE built-in procedure writes an image file to the application server file system. If you need to write an image file to the file system on the client, use a JavaBean.
Example of Image Items The following When-Image-Pressed trigger on the Product_Image item displays a picture of the current product (in the ITEM block) when the user clicks the image item. This example assumes that the related filenames have the format: <product id>.jpg . READ_IMAGE_FILE(TO_CHAR(:ORDER_ITEMS.product_id)||'.jpg', 'JPEG', ‘ORDER_ITEMS.product_image' ); Notice that as the first argument to this built-in is datatype CHAR . The concatenated NUMBER item, product_id, must first be converted by using the TO_CHAR function. Note: If you load an image into a base table image item by using READ_IMAGE_FILE , then its contents will be committed to the database LONG RAW or BLOB column when you save changes in the form. You can use this technique to populate a table with images.
Populating Hierarchical Trees The hierarchical tree displays data in the form of a standard navigator, similar to the Object Navigator used in Oracle Forms Developer. You can populate a hierarchical tree with values contained in a Record Group or Query Text. At run time, you can programmatically add, remove, modify, or evaluate elements in a hierarchical tree. You can also use the property palette to set the populate properties of the hierarchical tree. The FTREE Package The FTREE package contains built-ins and constants to interact with hierarchical tree items in a form. To utilize the built-ins and constants, you must precede their names with the name of the package.
Populating Hierarchical Trees (continued) SET_TREE_PROPERTY Procedure This built-in procedure can be used to change certain properties for the indicated hierarchical tree item. It can also be used to populate the indicated hierarchical tree item from a record group. Ftree.Set_Tree_Property(item_name, Ftree.property, value); You can add data to a tree view by: Populating a tree with values contained in a record group or query by using the POPULATE_TREE built-in Adding data to a tree under a specific node by using the ADD_TREE_DATA built-in Modifying elements in a tree at run time by using built-in subprograms Adding or deleting nodes and the data elements under the nodes Example This code could be used in a When-Button-Pressed trigger to initially populate the hierarchical tree with data. The example locates the hierarchical tree first. Then, a record group is created and the hierarchical tree is populated. DECLARE htree ITEM; v_ignore NUMBER; rg_emps RECORDGROUP; BEGIN htree := Find_Item('tree_block.htree3'); rg_emps := Create_Group_From_Query('rg_emps', 'select 1, level, last_name, NULL, to_char(employee_id) ' ||' from employees ' || 'connect by prior employee_id = manager_id ' || 'start with job_id = ''AD_PRES'''); v_ignore := Populate_Group(rg_emps); Ftree.Set_Tree_Property(htree, Ftree.RECORD_GROUP,rg_emps); END;
Displaying Hierarchical Trees The Record Group or Query The columns in a record group or query that are used to populate a hierarchical tree are: Initial state: 0 (not expandable, 1 (expanded), or -1 (collapsed) Node tree depth: Use LEVEL pseudocolumn Label for the node: What the user sees Icon for the node: Picture displayed, if any Data: Actual value of the node
Interacting with JavaBeans In Lesson 10, you learned how to add a JavaBean to a form using the Bean Area item. The bean that you add to a form may have a visible component on the form itself, such as a Calendar bean that has its own button to invoke the bean. However, JavaBeans (such as the ColorPicker bean) do not always have visible component, so you may need to create a button or other mechanism to invoke the bean. Regardless of whether the bean is visible in the bean area, there must be some communication between the run-time form and the Java classes that comprise the bean. First, the form must be made aware of the bean, either by setting its Implementation Class property at design time or by registering the bean and its events at run time. Once the form knows about the bean, the form communicates to the bean by: Invoking the methods of the bean Getting and setting properties of the bean The bean communicates to the form by: Sending an event, such as the fact that the user selected a date or color Sending a list containing information needed by the form, such as what date or color was selected Returning a value from an invoked method
Interacting with JavaBeans (continued) The FBEAN package The FBEAN package contains Forms built-ins that enable you to code interactions with JavaBeans in PL/SQL, eliminating the need to know Java in order to communicate with the bean. Many of the built-ins take some of the same arguments: Item Name or Item Id (obtained with the FIND_ITEM built-in): The first argument for most of the FBEAN built-ins, referred to on the next page simply as ITEM . Item Instance: A reference to which instance of the item should contain the bean. This is applicable where the Bean Area is part of a multi-row block and more than one instance of the Bean Area is displayed. This is referred to on the next page as INSTANCE . You can use the value ALL_ROWS (or FBEAN.ALL_ROWS ) for the Item Instance value to indicate that command should apply to all of the instances of this Bean Area in the block. Note: This refers to the UI instance of the Bean Area, not the row number in the block. For example, in a block with 5 rows displayed and 100 rows queried, there will be 5 instances of the bean numbered 1 through 5, not 100 instances. Value: Can accept BOOLEAN , VARCHAR2 , or NUMBER datatypes.
Interacting with JavaBeans (continued) The FBEAN package (continued) Some of the built-ins in the FBEAN package are: GET_PROPERTY(ITEM,INSTANCE,PROPERTY_NAME) (returns VARCHAR2 ): Function that retrieves the value of the specified property SET_PROPERTY(ITEM,INSTANCE,PROPERTY_NAME,VALUE) : Sets the specified property of the bean to the value indicated INVOKE(ITEM,INSTANCE,METHOD_NAME[,ARGUMENTS]) : Invokes a method on the bean, optionally passing arguments to the method REGISTER_BEAN(ITEM,INSTANCE,BEAN_CLASS) : Registers the bean with the form at run time, making all its exposed attributes and methods available for the form’s bean item (The last argument is the full class name of the bean, such as 'oracle.forms.demos.beans.ColorPicker'.) ENABLE_EVENT(ITEM,INSTANCE,EVENT_LISTENER_NAME, SUBSCRIBE) ; the last argument is a BOOLEAN indicating whether to subscribe ( TRUE ) or unsubscribe ( FALSE ) to the event. Remember to precede calls to any of these built-ins with the package name and a dot, such as FBEAN.GET_PROPERTY(…) . You can pass arguments to these built-ins as either a delimited string or as an argument list. Deploying the Bean Because the bean itself is a Java class or set of Java class files separate from the form module, you need to know where to put these files. You can locate these either: On the middle-tier server, either in the directory structure referenced by the form applet’s CODEBASE parameter or in the server’s CLASSPATH . CODEBASE is by default the forms90java subdirectory of ORACLE_HOME . If using JInitiator, in a JAR file in the middle-tier server’s CODEBASE directory, and included in the ARCHIVE parameter so that the JAR file is downloaded to and cached on the client. For example: archive_jini=f90all_jinit.jar,colorpicker.jar (The CODEBASE and ARCHIVE parameters are set in the formsweb.cfg file.)
Interacting with JavaBeans (continued) Responding to Events When a user interacts with a JavaBean at run time, it usually causes an event to occur. You can use FBEAN.ENABLE_EVENT to register a listener for the event, so that when the event occurs Forms will fire the When-Custom-Item-Event trigger. In this trigger, you can code a response to the event. The :SYSTEM.CUSTOM_ITEM_EVENT and : SYSTEM.CUSTOM_EVENT_PARAMETERS variables contain the name of the event and information the bean is sending to the form. A typical interaction that could occur includes the following steps: 1. The user clicks the bean area for a Calendar bean. This bean area has a visible component on the form that looks like a button. The label is set to the hire date for an employee. 2. The Calendar bean is invoked and displays a calendar initially set to the employee’s hire date. 3. The user changes the date on the bean by picking a new month and year, then clicking on a day, which initiates the DateChanged event. 4. The When-Custom-Item-Event trigger obtains the changed date and assigns it back to the employee hire_date item, also changing the label on the bean area “button”.
Interacting with JavaBeans (continued) Coding a When-Custom-Item-Event Trigger In a When-Custom-Item-Event trigger to respond to JavaBeans events, you code the action that you want to take place when an event occurs. For example, when a user selects a date from the Calendar bean, the DateChange event takes place and the When-Custom-Item-Event trigger fires. In the code for the When-Custom-Item-Event trigger on the Calendar bean area item, you need to obtain the name of the event. If it is the DateChange event, you must obtain the new date and assign it to a form item, such as the employee’s hire date. You can use the system variables containing the event and parameter information: declare hBeanEventDetails ParamList; eventName varchar2(80); paramType number; eventType varchar2(80); newDateVal varchar2(80); newDate date := null; begin hBeanEventDetails := get_parameter_list (:system.custom_item_event_parameters ); eventName := :system.custom_item_event ; if(eventName = 'DateChange') then get_parameter_attr(hBeanEventDetails, 'DateValue', ParamType, newDateVal); newDate := to_date(newDateVal,'DD.MM.YYYY'); end if; :employees.hire_date := newDate; end; The above example is for a bean that uses hand-coded integration. If you use the FBEAN package to integrate the bean, the name of the value passed back to the form is always called ‘DATA’. For example: get_parameter_attr(:system.custom_item_event_parameters, 'DATA',paramType,eventData); (where paramType and eventData are PL/SQL variables you declare in the When-Custom-Item-Event trigger, like paramType and newDateVal in the preceding example). Note: There are many examples of JavaBeans in the Forms Demos that you can download from OTN: http://otn.oracle.com/sample_code/products/forms/index.html
Interacting with JavaBeans (continued) Getting Values from JavaBeans without Events Not all information from JavaBeans is obtained via events. For example, a JavaBean may return a value when one of its methods is invoked. This value may be assigned to a PL/SQL variable or Forms item, similarly to the way a function returns a value. An example of this is the ColorPicker bean that you added to the Customer form in Lesson 9. It contains a single method that returns a value, and also has no visible component in the bean area of the form. To invoke the bean and obtain a value from it, you can use a Forms push button and trigger with code similar to the following: vcNewColor := FBean.Invoke_char(hColorPicker, 1,'showColorPicker','&quot;Select color for canvas&quot;'); The INVOKE_CHAR built-in is used to call a method that returns a VARCHAR2 value. 1. User clicks button to invoke the bean. 2. Color Picker component displays. 3. User selects a color. 4. Color value (RGB values in comma-separated list) is returned to the vcNewColor variable. The code can then use the color value to set the canvas color.
Summary In this lesson, you should have learned to use triggers to provide functionality to the GUI items in form applications. The item interaction triggers accept SELECT statements and other standard PL/SQL constructs.
Summary (continued) There are built-ins for check boxes, LOV control, list item control, image file reading, hierarchical tree manipulation, interaction with JavaBeans, and so on.
Practice 16 Overview In this practice, you create some additional functionality for a radio group. You also code interaction with a JavaBean. Finally, you add some triggers that enable interaction with buttons. Writing a trigger to check whether the customer’s credit limit has been exceeded Coding a button to enable users to choose a canvas color for a form Creating a toolbar button to display and hide product images Note: For solutions to this practice, see Practice 16 in Appendix A, “Practice Solutions.”
Practice 16 1. In the CUSTG XX form, write a trigger that fires when the credit limit changes. The trigger should display a message warning the user if a customer’s outstanding credit orders (those with an order status between 4 and 9) exceed the new credit limit. You can import the pr16_1.txt file. 2. Click Run Form to run the form and test the functionality. Hint: Most customers who have outstanding credit orders exceed the credit limits, so you should receive the warning for most customers. (If you wish to see a list of customers and their outstanding credit orders, run the CreditOrders.sql script in SQL*Plus.) Customer 120 has outstanding credit orders of less than $500, so you shouldn’t receive a warning when changing this customer’s credit limit. 3. Begin to implement a JavaBean for the ColorPicker bean area on the CONTROL block that will enable a user to choose a color from a color picker. Create a button on the CV_CUSTOMER canvas to enable the user to change the canvas color using the ColorPicker bean. Set the following properties on the button: Label: Canvas Color Mouse Navigate: No Keyboard Navigable: No Background color: white The button should call a procedure named PickColor, with the imported text from the the pr16_3.txt file. The bean will not function at this point, but you will write the code to instantiate it in Practice 20. 4. Save and compile the form. You will not be able to test the Color button yet, because the bean does not function until you instantiate it in Practice 20. 5. In the ORDG XX form CONTROL block, create a new button called Image_Button and position it on the toolbar. Set the Label property to Image Off. 6. Import the pr16_6.txt file into a trigger that fires when the Image_Button is clicked. The file contains code that determines the current value of the visible property of the Product Image item. If the current value is True, the visible property toggles to False for both the Product Image item and the Image Description item. Finally, the label changes on the Image_Button to reflect its next toggle state. However, if the visible property is currently False, the visible property toggles to True for both the Product Image item and the Image Description item. 7. Save and compile the form. Click Run Form to run the form and test the functionality. Note: The image will not display in the image item at this point; you will add code to populate the image item in Practice 20.