Today was the first day of presentations. First, however, was the welcoming ceremony/keynote address. The highlight (for me, at least) was the “false” keynote–they announced the keynote speaker; a man came out, gave a presentation, and then revealed that he was not actually Joey Asher–he was Don McMillan, an engineer/comedian (who will also be performing Wednesday night on the Queen Mary). Don's presentation was very funny (I especially liked his pie chart->cake chart->birthday cake chart->wedding cake chart sequence), and I'm looking forward to seeing him perform again.
As for the presentations…the first one I went to was APEX Adolescence, by Scott Spendolini. The first part was an overview of APEX's history, from Oracle Flows, through Project Marvel, to HTML DB, and then through the various versions of APEX to where we are now. After that, he launched into a discussion of the need for the APEX developer community to really work on establishing best practices–security, version tracking, etc.–since APEX is working its way into areas that are generally audited (“central IT”, to use Scott's terms).
The second presentation I went to was Patrick Wolf's demonstration of the new error handling options in APEX 4.1. Very exciting (I know, that sounds sooo geeky…oh, well). I'm not sure I'm thrilled that you have to go into globalization to customize the text messages (or write your own PL/SQL error handling routines), but it has to go somewhere, so…(shrug)
For the last session, I went to David Peake's discussion of using APEX to extend the E-Business Suite (based on this white paper). If you're on EBS r12 and want to link it to your APEX, follow the white paper–you'll have a configuration that is certified by Oracle (and thus able to get support on it).
Finally, in the evening, I went to the APEX Open Mic Night; the part I liked best was Dan McGhan's demo of a plugin he's going to be releasing soon to make it somewhat easier to include modal dialogs in your applications. Still takes a few steps to get setup, but much better than coding it yourself.