Skip to main content

APEX FLoating Developer Toolbar

By
During the APEX 4.0 session at last ODTUG a question was raised: "Can we have a floating developer toolbar" (the thing at the bottom of the page with a.o. the 'Home' and 'Debug' link). There is no need to wait for APEX 4.0 to get that (if it will be implemented as a new feature), you can have it NOW!
If you put the next piece of code in an HTML Region in Page 0 (or in your Template, whatever you like), the toolbar gets sticked to the bottom of your browser like glue...


I guess it only works for FireFox, but that doesn't matter, because that's the tool we're all using anyway, aren't we? Oh, yeah, and you need jQuery...
Labels:

Comments

Unknown said…
Well, that's a very nice tip!
Thanks.

It would also be nice to have keyboard shortcuts to those commands.
Since we are "restricted" to Firefox, I think that it could be accomplished a GreaseMonkey Script.
Patrick Wolf already created some shortcuts on his APEX Builder Plugin (http://www.inside-oracle-apex.com/oracle-apex-builder-plugin/).

Unfortunately, I don't have the skills required to do it...

Cheers,
Pedro
5:09 pm
Louis-Guillaume said…
Cool!

I prefer to add shortcuts to FF's header as a replacement for the developer toolbar.
The shortcuts can call URLs or JavaScript functions.

Try calling your JavaScript code from a FF shortcut to enable your "special floating mode". You won't have to modify any applications or templates.
5:16 am
Matthias said…
Roel,

I'm using Firefox 3.5 but I'm pretty new to JQuery. Should that work out of the box or do you have to install an add-on for that?

Matthias
3:23 pm
Matthias said…
Hi Roel,

I found out myself :-)
Had to download the JQuery libraries and then include them in my APEX page first. Now it works, nice trick!!

Matthias
3:37 pm
Matthias said…
Btw: it works in Internet Explorer 8 too!

Matthias
3:40 pm
Roel said…
@Matthias: You (only) need to install jQuery.
12:04 pm
Joel Grocock said…
Hi Roel,
Do you know if the same code could be used to develop a floating menu region in APEX i.e a floating lefthand menu page region that always stays pinned to the top of the page as you scroll down the page.
Any pointers appreciated ;-)
1:49 pm
Roel said…
Hi Joel,

You can set the posotion of that list region to fixed (same solution as the toolbar). For instance if you define a region without a Template and use Listin that region with Vertical Ordered List as the List Template and set the style (for instance in the region header) to:
<style>
.t1VerticalOrderedList{
margin-top:0;
position:fixed;
right:0;
}
</style>

Then the list will show up at the top right of the screen and stays there - even if you scroll all the way down!

Regards
Roel
2:59 pm
Post a Comment

Popular posts from this blog

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

APEX ReadOnly Pages - The easy way

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