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

Filtering in the APEX Interactive Grid

By
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 o...
1 comment
Read more

Stop using validations for checking constraints !

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