Skip to main content

OOW 2010 about to start!

I just printed out my boarding pass for my 10.50 flight tomorrow morning. From Amsterdam, via Minneapolis to San Francisco takes around 11,5 hours time, with 1,5 hours overlay in Minneapolis. I hope that'll be enough to pass the US-border control!
It will be a busy week, with lots of sessions and networking events. I won't put my whole session schedule up here, that might set the expectation that I also will attend all these sessions... 
But in short: Sunday afternoon will mostly be filled by the ODTUG APEX sessions, and maybe pick a part of the Welcome keynote alongside.
Monday will be a combination of good old PL/SQL, APEX, Fusion, Fusion Apps, Exadata.  Tuesday has a similar picture: APEX, ESB, JavaFX and Tom Kyte's keynote. Wednesday is of course Larry's keynote (with or without Iron Man), and some database related sessions. Thursday I've planned to attend two more APEX sessions, before I have mine: at 12:30 in Hotel Nikko called "Using Edition-Based Redefinitions in an Oracle Application Express environment". And in my current schedule that also will be the last one. Funny, 'cause last year I had the opening session (Sunday 8.30 AM) and this year they put me way in the back of the schedule...
Also the networking part is packed: The ACE Dinner on Sunday; on Monday the ODTUG meetup, Benelux Happy Hour and the OTN Night clash more or less; Tuesday afternoon there is a One Logica lunch (where I can meet all colleagues present at the venue), and in the evening there is the traditional Blogger Meetup, followed by the APEX Meetup and the Benelux Cocktail Party (sounds like too much drinking...). Wednesday and Thursday no specialties: "just" the Appreciation event and the "It's a wrap!" thing.
Really looking forward to it!
Post a 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…