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…

A review of APEX World 2017 - Day 1

Last week the SS Rotterdam was the beautiful location of the largest gathering of APEX Developers worldwide. With around 380 (!) attendees a new high was set. And they came from all over the world : I spotted people from The Netherlands, Belgium, Switzerland, Austria, Croatia, Germany, Denmark, Norway, UK, Ireland and the USA. And I even might have missed one or two ….

The event started with a presentation by the “father of APEX”, Mike Hichwa, talking about "Oracle APEX Past, Present and Future”. Of course everyone is curious what the APEX future might bring: Friendly URL’s, automated testing, more JSON, concurrent APEX versions, third party Oauth 2 authentication (think Facebook, Google), APEX app diff and more, a lot more, REST capabilities. And now we have to wait for APEX 5.2 … and that might take a while! 
After this keynote, the conference split up in three tracks. After the coffee break I returned to to big theatre where Geertjan Wielenga talked about "Finally Javas…

Push changed rows to an Interactive Grid

For pushing changes from the database to the end user, the regular solution is using websockets. A change in a record is detected - using a trigger or using the CQN (Change Query Notification) feature - and a notification is send to a websocket server. That websocket server broadcasts the notification over a channel to all browsers that are tuned in to that websocket channel. Then the browser reacts to that notification, usually showing an alert or refreshing a report. This trick is described on multiple sites, just Google for "oracle apex websockets" or similar.

So back in the old days, we used that notification in the browser to refresh the (interactive) report. But along comes the Interactive Grid (IG). While he full-refresh mechanism still works for IG, an IG has also the option to refresh just one row.  So wouldn't it be awesome that just the changed row(s) get refreshed upon a change in the database, instead of the whole report? Can we do it ... yes we can!
First i…