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

How to create neatly formatted Excel documents using PL/SQL?

If there is a requirement to produce output from an application into Excel, you would probably create a CSV (Comma Separated File) with the data and start Excel to show the data - at least that's what I did...until now. The drawback of this solution is that you could only produce data and no nice layout. But Excel is also capable of opening HTML-files and using this you could create Excel files with data and magnificent layout! Let me give an example: 1. Create a procedure to show the data in formatted in an HTML table. CREATE OR REPLACE PROCEDURE display_emp_list IS v_emp_count NUMBER(5); v_empno NUMBER(8); v_ename VARCHAR2(50); v_job emp.job%TYPE; v_sal emp.sal%TYPE; v_bg_color VARCHAR2(10) := ''; CURSOR c_emp IS SELECT empno, initcap(ename), job, sal FROM emp ORDER BY ename; BEGIN SELECT COUNT(*) INTO v_emp_count FROM emp; owa_util.mime_header('application/ms-excel', FALSE); htp.p('Content...

Refresh selected row(s) in an Interactive Grid

In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid . The use case I'll cover right here is probably more common - and therefore more useful! Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user. The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even wors...

APEX ReadOnly Pages - The easy way

If your Oracle APEX Application requires different types of access - full access or readonly - for different types of users, you can specify a Read Only Condition on Page level (or Region, Item, Button, etc.).  You can set an Authorization Scheme on Application level, so it'll be applied to all pages. So if you have an Authorization Scheme named 'User Can Access Page' defined by a PL/SQL function like this: return apex_authorization.user_can_access_page ( p_app_id  => :APP_ID , p_page_id => :APP_PAGE_ID , p_user    => :APP_USER );  then you can code all the logic in the database using the APEX Repository, your own tables or a combination to define whether a user has access to that page or not. But alas it is not possible to define something similar Application wide for a Read Only condition. You can specify an Authorization Scheme 'User has Read Only Access' using a similar signature as the one above and use that on each and e...