Skip to main content

OOW2010 Sunday

In the evening of this day Oracle had organised a cruise for all ACE's. At least for who that were on time....(sorry Jacco, had to mention it). It was good fun, a nice trip with beautiful views of San Francisco at night. We had to leave during Larry's keynote, that overrun an hour or so. Larry announced the Exalogic machine. Also called "your own private cloud". He mentioned that Facebook could run on two of those machines. But thinking of that: if Facebook needs two, who needs one? I guess the installed base will not be that big. But you can also buy "half a rack"! The other big thing was the announcement of the general availability of Fusion Apps in 2011Q1, 5 years after it was mentioned first. The third thing was the new unbreakable Linux kernel, to overcome the - according to Oracle - slow development of Linux by Redhat. I wonder what will be left for the Wednesday keynote...probably the new Java roadmap...
Before the keynotes, there were some user group sessions, which turned out to be very good. Especially the way Tim St Hilaire "forced" his organisation in defining real priorities using a Netflix like drag and drop interface was cool. Also Chris Muir's presentation on JMeter gave a lot of insight on when and how to do load and stress tests of web applications in general - and APEX or ADF ones in particular.
All in all it was a great day...and it was only a half one!

Comments

Anonymous said…
Thanks Roel, missing the boat (hur hur) was a nice lesson in anger management :)

Popular posts from this blog

Fix Interactive Report headers issue when using a Region Display Selector

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.

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

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...

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 wors...