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!
1 comment

Popular posts from this blog

Showing a success message after closing a modal dialog

APEX 5 comes with Modal Dialogs out of the box. Very neat. Especially for adding and changing data. And to minimise the number of time a user has to click, it could be useful to add a "Close Dialog" process after the actual data processing. When the data processing fails, the Dialog stays on top showing the error. When data processing runs fine, the Dialog is closed ... without any confirmation. And this might be scary for a shaky user.

So how can we provide the user some feedback? On Page 4 of the Sample Dialog Application you can see one solution: up on a Dialog Closed Event on the parent page it does a redirect to refresh the parent page appending the success message of the "Close Dialog" process. This has two drawbacks. First, it probably refreshes more than necessary. And second, if you're using multiple layers of dialogs (dialogs that open other dialogs) the message appears in the "parent dialog".
As an alternative you could follow these steps: 1…

It's happening again ... running for the ODTUG Board of Directors 😉

For the third time in a row I'll be running for ODTUG's Board of Directors. But after ending as a runner up twice, I am sure I'm going to make it this time! But not without your help!

My campaign statement this year is:
I have been attending and presenting at Kscope conferences since 2007. This not only resulted in a vast amount of knowledge, but also - and even more important - a huge number of friends from all over the globe.  I want to see ODTUG grow and spread this community feeling even more! 
My experience as an attendee, presenter and content lead has provided the basic foundation to be a director. Next to that, my personality and (global) network will be beneficial to the whole board and organization. 
Since March I have served on the Board of Directors in a limited term for a Director who stepped down due to a career change. This has allowed me to have unique insight of all the things that are going on in and around the ODTUG organization. As the train was already ro…

APEX 5 New Static File Features

In APEX 4 you could upload files - like CSS files, JavaScript files, Images and whatever else you like - into the APEX Repository. When you navigate to Shared Components, there is a Files section that offers three different options:
CSS Files are always uploaded (and changed !) for the whole Workspace. For Images and Static Files (usually JavaScript) you could choose whether they should be available for the whole Workspace or for a specific Application only. And if you had a lot of files - e.g. a lot of images - then you had to go through the upload process one-by-one. But that's usually a one time only thing. If you make changes to the CSS and JavaScript files - and that's a continuous process in development - then you had to delete the existing file and upload the new one. Over and over again. And meanwhile fighting the cache of the webserver and your browser.  And another irritating issue: You couldn't use relative references in your CSS or JavaScript files as they just…