Skip to main content

ODTUG Kaleidoscope 2008 : The day before


After an 18 hour trip from my home I arrived at the Sheraton in New Orleans. Luckily this time I also got my bag (at OOW 2007 it arrived a day later). A small wonder, because my transfer time in Houston was reduced from 1 ½ hour to 20 minutes due to the border control officer, who seemed to be very interested in all my predecessors in the queue. So I had to run from gate E to C. On the way I saw at a screen that The Netherlands where ahead against France with 1-0. At the time I arrived in New Orleans I called home and found out it turned out be a 4-1 victory!

When I came outside of the airport the tropical atmosphere hit me. It was about 32 C, but very very humid. After dropping of my luggage and freshening up a little in my room at the 43 floor, overlooking the Mississippi, I went out into the French Quarter. This area is packed with bars and restaurant and every bar seemed to have it’s own live music. I managed to stay awake until 9pm - that makes about 22 hours awake - and slept until 6:30 the next morning.

When I stepped out for a nice and quiet stroll through the French Quarter and the riverside it was so hot and humid already - or still - that my sunglasses blurred immediately. Like stepping into a tropical swimming pool. After my walk I took the old steamboat for a trip over the Mississippi and strolled over the Cajun / Zydeco and Tomato festival. New Orleans is very very lively: there is music on every corner and food stalls in between them. And of course the obvious street artists painting, breakdancing and reading hands. In this part of town there is not much damage left from Katrina three years ago, but also it didn’t suffer that much from The Storm as the locals seem to call it.

I hope I am over my jetlag already and ready for the start of the conference tomorrow morning at 8:30 : a full day ‘APEX Must hear success stories’

For those who are more of the visual type, I uploaded some pictures here.
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…

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…