Databases Reference
In-Depth Information
});
})(apex.jQuery);
At this point you should be ready to test the plug-in. Try adjusting the various settings, including the
alignment and offset settings, to see how they affect the plug-in at run time. Consider leveraging the
Position widget of jQuery UI in the future if you're building a plug-in that requires similar functionality.
Listing 11-4.
PL/SQL Code for the Save Value on Cascade Plug-in
FUNCTION password render (
p item IN APEX PLUGIN.T PAGE ITEM,
p plugin IN APEX PLUGIN.T PLUGIN,
p value IN VARCHAR2,
p is readonly IN BOOLEAN,
p is printer friendly IN BOOLEAN
)
RETURN APEX PLUGIN.T PAGE ITEM RENDER RESULT
IS
l retval APEX PLUGIN.T PAGE ITEM RENDER RESULT;
l name VARCHAR2(30);
l submit on enter VARCHAR2(1) := NVL(p item.attribute 01, 'Y');
l message icon VARCHAR2(20) := NVL(p item.attribute 02, 'ui-icon-alert');
l message text VARCHAR2(500) := NVL(p item.attribute 03, 'Caps Lock is enabled.');
l message width PLS INTEGER := NVL(p item.attribute 04, 150);
l message alignment VARCHAR2(20) := NVL(p item.attribute 05, 'center bottom');
l password alignment VARCHAR2(20) := NVL(p item.attribute 06, 'center top');
l offset VARCHAR2(20) := NVL(p item.attribute 07, '0');
l jqueryui theme VARCHAR2(30) := p plugin.attribute 01;
l onload code VARCHAR2(32767);
l crlf CHAR(2) := CHR(13)||CHR(10);
BEGIN
IF apex application.g debug
THEN
apex plugin util.debug page item (
p plugin => p plugin,
p page item => p item
);
END IF;
IF p is readonly OR p is printer friendly
THEN
NULL;--Password should not be displayed
ELSE
apex javascript.add library(
p name => 'com pluggen password',
p directory => p plugin.file prefix,
p version => NULL
