Skip to main content

It is even more easy to replace the APEX with the jQuery calendar...

In a previous post I described how to replace the default APEX calendar with a better looking jQuery calendar. But one of the steps is that the "Display as" and "HTML Form Element Attributes" needed to be changed. But using jQuery more extensively that isn't even necessary. When you put the following code in an HTML Region on Page 0 (assuming you already included the jQuery stuff), all existing APEX calendar items are automagically 'converted' to jQuery calendar items. (No guarantee though: I didn't test it on all sorts of pages, may be dependent on your template). Look here for a live demo...

$(function(){
// Remove original Datepicker
$("td.datepicker + td" ).remove();
// Add jQuery Datepicker to all Datepicker input fields that are not hidden
$("td.datepicker > input[type!=hidden]" ).datepicker(
{ dateFormat : 'dd/mm/yy'
, closeText : 'X'
, clearText : ''
, showOn : 'button'
, buttonImage : '#WORKSPACE_IMAGES#calendar.gif'
, buttonImageOnly : true
});
});

Comments

Patrick Wolf said…
Hi Roel,

is there a reason why you are using "each" instead of just using

$("td.datepicker > input[type!=hidden]" ).datepicker

Because that also seems to work and is a little bit shorter and easier to read.

Greetings
Patrick
Patrick Wolf said…
Or you can even use a more compact version which uses the jQuery chaining:

$("td.datepicker")
.next("td")
.remove()
.end()
.children("input[type!=hidden]")
.datepicker(
{ dateFormat : 'dd/mm/yy'
, closeText : 'X'
, clearText : ''
, showAnim : 'scale'
, showOptions : { origin: ['top', 'left'] }
, showOn : 'button'
, buttonImage : '#WORKSPACE_IMAGES#calendar.gif'
, buttonImageOnly : true
});

Too bad that the comment function doesn't allow a PRE tag to format the code. If you use chaining, indenting the code is very important so that you see the structure and which result set is used.

Greetings
Patrick
Louis-Guillaume said…
Roel, thanks for the idea.
Patrick, thanks for the more compact syntax.
Roel said…
Thanks Patrick & Louis-Guillaume.
So the code gets shorter every time....
Tim Ward said…
I'm doing the following to replace datepickers in apex 3.2 with the JQuery Datepickers, but my only problem is the images doesn't display next to the field.. Any ideas why that would happen?

"<"link rel="stylesheet" type="text/css" href="#IMAGE_PREFIX#jquery/css/redmond/jquery-ui-1.8.4.custom.css" /">"

"<"script type="text/javascript" src="#IMAGE_PREFIX#jQuery/js/jquery-1.4.2.min.js"">""<"/script">"

"<"script type="text/javascript" src="#IMAGE_PREFIX#jQuery/js/jquery-ui-1.8.4.custom.min.js"">""<"/script">"

"<"script type="text/javascript"">"
$(document).ready(function () {
$(".datepicker ">" input[id]").datepicker();

$.datepicker.setDefaults({
dateFormat: 'dd-M-yy',
changeMonth: true,
changeYear: true,
closeText: 'Done',
showButtonPanel: true,
duration: 'slow',
prevText: 'Previous',
showOtherMonths: true,
selectOtherMonths: true,
dayNamesShort: ['Sun','Mon','Tue','Wed','Thu','Fri','Sat'],
dayNamesMin: ['Sun','Mon','Tue','Wed','Thu','Fri','Sat'],
constrainInput: true,
showOn: 'both',
buttonImage: '#IMAGE_PREFIX#asfdcldr.gif',
buttonImageOnly: true,
buttonText: 'Calendar',
autoSize: true
});

});

$(function(){
// Remove Original Date Picker //
$("td.datepicker + td").remove();

// Add jQuery DatePicker to all DatePicker input fields not hidden //
$("td.datepicker ">" input[type!=hidden]").datepicker();
});

$(document).ready(function(){
$(".datepickernew").datepicker();
});
"<"/script">"
Roel said…
Tim, where do they display? Can you set up an example on apex.oracle.com?
Tim Ward said…
Guess I should have said that they don't display at all...

I'll try to do something at apex.oracle.com, but don't they use 4.0 now?
Tim Ward said…
Seems to work fine on Apex 4.0....

Just weird that using the code I showed that the calendar image won't show up on the internal replaced date pickers...

The image shows up if I create a Text Item with class="datepickernew" in the HTML Form Element Attributes of the page.

Popular posts from this blog

apex_application.g_f0x array processing in Oracle 12

If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one: then you disable the " Escape special characters " property and the result is an updatable multirecord form. That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for

Filtering in the APEX Interactive Grid

Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the  APEX_IR.ADD_FILTER  procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good old Employ

Stop using validations for checking constraints !

 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function