Skip to main content

Travelling to OOW 2010

Yesterday was one of those days. Crossing the Atlantic and ending up with crossing 9 timezones. So that day had 33 hours...(so you can definitely have more than 24 hours in a day!).
I got up at 6 AM, traveled to Schiphol (Amsterdam Airport) by train. At Schiphol it was crowded! People with large bags everywhere, no one standing in line. Giant congestion for the border security etc. And then there is the obligatory chat with a security officer when boarding (did you pack your bag yourself, brought anything etc..). The strange thing is the US carriers seem to be obliged doing that - but only for inbound flights??
But the good thing was: I managed to upgrade my first leg of the trip (to Minneapolis). Never traveled Business Class before, but, man! what a joy!. Imagine long, broad seats with lots of buttons on the armrest. If you use the right ones, you can get the chair in a 100% horizontal position - while massaging your back! And then there is the drinks and the food... I would love to travel this way every time, but hey, budget is limited - and frequent flyer miles are too.
In Minneapolis I had originally a 1,5 hour layover, but when we arrived it was shrunk to 1 hour. With one airplane full of Japanese visitors in front of my at the border security. Luckily it took only around half an hour to pass the security, so a good half an hour left to grab a coffee and walk to the connecting plane. No business class this time, but a crowded economy. So: Plug in iPod and close eyes...
Got a cab in SF to the house (Jacco rented it - with his girlfriend Margot), got some good food with the three of us, had a few beers and went to bed around 10 PM. 
And of course woke up at 2.30, 3, 3.30, 4.15, 5.45...and finally got out of bed and made myself a coffee. 
Looking forward to the rest of the day: Usergroup sessions, Keynote, ACE Dinner...here I come!


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…