Skip to main content

Create a favicon for your APEX 4.0 application

By
Probably totally superfluous, but a "favicon" is the little picture that shows up in your browser tab or bookmark list - like the example above. The APEX Page Templates support this nice feature by these two lines in the Header property :


So if you replace that default favicon file - which is not so cool - with your own, then you'll get something like the picture above. However, that file (on your virtual /i/ directory on a standard install) may be overwritten by the APEX default icon when upgrading or patching! That favicon will then be used for all your APEX applications A more flexible alternative is to go through all page templates and change the reference to your own favorite icon file to #APP_IMAGES#.ico (or to something like #IMAGE_PREFIX#my-icons/.ico. And of course upload a nice little icon for every application...
Labels:
Location: Arnhem, Nederland

Comments

Stew said…
Slick! As you said, not that important in the grand scheme of things, but still adds value to a site.

I just implemented in one of my sites.

Thanks!
4:48 pm
Anonymous said…
I have created a bookmark link in the page template, like so:

{a href="javascript:window.external.AddFavorite('http://apex.gov:7780/', 'LINK')">
Bookmark Site{/a>

How would I put the shortcut icon in this line of code.

By the way I had to put a squiggly brace in front of the a's and take out my span.

This bookmark link only works in IE, not in FireFox.
8:57 pm
Roel said…
See (your?) OTN Forum thread: http://forums.oracle.com/forums/thread.jspa?threadID=2130413&tstart=0
8:59 am
Post a Comment

Popular posts from this blog

Fix Interactive Report headers issue when using a Region Display Selector

By
When you have multiple Interactive Reports (IR) on your page and use a Region Display Selector to mimic tabs, you might notice some weird behaviour in the IR headings if you switch tabs. The headings are not positioned correctly and you get an extra empty row under the headings. It just looks weird and ugly. But if you resize your browser window, it all looks fine again (until you switch to another tab..) So can we fix this by creating a Dynamic Action that mimics that "browser window resize" event? Yes we can! Create a Dynamic Action that fires on Click of the jQuery selector li.apex-rds-item a . That should fire a JavaScript snippet :  apex.event.trigger(this.triggeringElement, "apexwindowresized"); So now a click on a tab not only switches from one IR to another but also fires that event that will "autofix" the IR headers. A simple solution for an annoying problem. This applies to APEX 5.0, I assume it will be solved in 5.1.
Post a Comment
Read more

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

By
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...
21 comments
Read more

Refresh selected row(s) in an Interactive Grid

By
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...
Post a Comment
Read more