Skip to main content

APEX on Mac OS X - Update II

After two days of consistent use, APEX on OS X has performed flawlessly! And it's fast - REALLY fast! Sure, there's no network there to slow things down, but when using Safari 4, it's just as fast as static pages!

Now that Oracle runs natively on OS X, I can stop relying on VMs for that service, and use SQL Developer, Firefox and other Mac tools for 100% of my development.

I just hope that the folks at Oracle make this a supported configuration at some point so that we don't have to keep running in an unsupported fashion.

Comments

Sujay said…
This comment has been removed by the author.
Patrick Wolf said…
Hi Scott,

with the to be released APEX Listener we should be able to support APEX on the Mac.

I installed 10gR2 and Tomcat+APEX Listener on my MacBook Pro yesterday and it really rocks! It's super fast! :-)

Patrick
Scott said…
Good to hear!

Any news as to when the rest of 10g will be included for the Mac?

- Scott -
Sujay said…
I installed Oracle 11g for Windows and am very disappointed to see Oracle 3.0.1.00.08 on it. I would have expected to see the latest 3.2 version.

About 11g for Mac, wonder when will that come out.
Scott said…
Sujay,

The reason that there's an older version of APEX on the 11g CD is that was likely the current version when the 11g CDs were cut. APEX is on its own release schedule, and does not always have the latest version on the same media as the database.

The beauty of APEX is that it only takes a few minutes to update it to the latest version!

As for 11g, I'm just happy that SOMETHING is out!

- Scott -
Sujay said…
Agreed, but considering Oracle Apex is such a beautiful product, I just feel Oracle doesn't really make the push for it. If I were Oracle I would go "All In" (poker term) with Oracle Apex :)
Anonymous said…
Has anyone built a one button install for Oracle 10g and Apex for Mac OS X?

Popular posts from this blog

Custom Export to CSV

It's been a while since I've updated my blog. I've been quite busy lately, and just have not had the time that I used to. We're expecting our 1st child in just a few short weeks now, so most of my free time has been spent learning Lamaze breathing, making the weekly run to Babies R Us, and relocating my office from the larger room upstairs to the smaller one downstairs - which I do happen to like MUCH more than I had anticipated. I have everything I need within a short walk - a bathroom, beer fridge, and 52" HD TV. I only need to go upstairs to eat and sleep now, but alas, this will all change soon... Recently, I was asked if you could change the way Export to CSV in ApEx works. The short answer is, of course, no. But it's not too difficult to "roll your own" CSV export procedure. Why would you want to do this? Well, the customer's requirement was to manipulate some data when the Export link was clicked, and then export it to CSV in a forma

Refreshing PL/SQL Regions in APEX

If you've been using APEX long enough, you've probably used a PL/SQL Region to render some sort of HTML that the APEX built-in components simply can't handle. Perhaps a complex chart or region that has a lot of custom content and/or layout. While best practices may be to use an APEX component, or if not, build a plugin, we all know that sometimes reality doesn't give us that kind of time or flexibility. While the PL/SQL Region is quite powerful, it still lacks a key feature: the ability to be refreshed by a Dynamic Action. This is true even in APEX 5. Fortunately, there's a simple workaround that only requires a small change to your code: change your procedure to a function and call it from a Classic Report region. In changing your procedure to a function, you'll likely only need to make one type of change: converting and htp.prn calls to instead populate and return a variable at the end of the function. Most, if not all of the rest of the code can rem

Logging APEX Report Downloads

A customer recently asked how APEX could track who clicked “download” from an Interactive Grid.  After some quick searching of the logs, I realized that APEX simply does not record this type of activity, aside from a simple page view type of “AJAX” entry.  This was not specific enough, and of course, led to the next question - can we prevent users from downloading data from a grid entirely? I knew that any Javascript-based solution would fall short of their security requirements, since it is trivial to reconstruct the URL pattern required to initiate a download, even if the Javascript had removed the option from the menu.  Thus, I had to consider a PL/SQL-based approach - one that could not be bypassed by a malicious end user. To solve this problem, I turned to APEX’s Initialization PL/SQL Code parameter.  Any PL/SQL code entered in this region will be executed before any other APEX-related process.  Thus, it is literally the first place that a developer can interact with an APEX p