Skip to main content

MacMenu for APEX

A MacMenu sounds rather unhealthy, but if you can create your own one.... See it in action at the bottom of this page. The explanation on how to get this kind of result is also on that page.


Anonymous said…

a nice example, but i doesn't work work correct in Opera, the small images are displayed strange.

The example at works correct in Opera, so maybe there is some bug in your implementation?
Gary Myers said…
Pretty but worth pointing out that Apple did get awarded a patent for the magnification feature of its dock.
It doesn't seem to work quite right in Internet Explorer. Do you know why? Also can the magnification be adjusted?
Roel said…
@Sunjay: In IE the menu shows up at the bottom left of the screen (instead of centered). I don't know why - and I didn't dive into it. The magnification is somewhere calculated - probably dependant on a CSS setting...??
Marco Schlicher said…

Does the MacMenu also work in Apex 4.0 ?

can you please explain from were the CSS file should be created, is this from your page were the MacMenu is located or is this from the page.

And where soould the function call
to the jQuery 'start' function be created ?

Hi Roel,

can you please explain me the last step(4. Add a function call to the jQuery 'start' function:).

I am not getting where to insert the jquery code in apex.

Whether in dynamic action or Application process or In HTML Header of the page?

So please guide me on this flow.


Sharath SN

Popular posts from this blog

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 worse) while you…

Dockerize your APEX development environment

Nowadays Docker is everywhere. It is one of the main components of Continuous Integration / Continuous Development environments. That alone indicates Docker has to be seen more as a Software Delivery Platform than as a replacement of a virtual machine.

However ...

If you are running an Oracle database using Docker on your local machine to develop some APEX application, you will probably not move that container is a whole to test and production environments. Because in that case you would not only deliver a new APEX application to the production environment - which is a good thing - but also overwrite the data in production with the data from your development environment. And that won't make your users very excited.
So in this set up you will be using Docker as a replacement of a Virtual Machine and not as a Delivery Platform.
And that's exactly the way Martin is using it as he described in this recent blog post. It is an ideal way to get up and running with an Oracle database …

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 processing y…