Skip to main content

Collaborate 2011 - Day 1

Travelling to Orlando went smooth. Very smooth even. The first leg to Boston arrived about a half hour early and as I was sitting right in front of the Economy class, I could leave the plane as one of the first. So I arrived at the border securty as the third non-US citizen. So checkin in the US costed about two minutes. I even arrived at the luggage belt before it actually started running - usually my bag is already off the belt when I arrive there. After an almost two hour layover, in the second plane I managed to get two seats at the exit row. So I could move wherever I liked. And at Orlando airport a taxi was immediately available so I arrived at the hotel around 6:30 AM. After some real American food (burger, beer & fries) I hit the sack around 10. 
The next morning I managed to stay more or less asleep until 7. From 9 to 12 I sat at the pool until it was getting too hot and went to the registration of Collaborate.The conference is in the Orlando Conference Centre. I thought Moscone in San Francisco was a big place, but this is way bigger. The staff rides around on Segways...
Today there was only one session on my schedule : "Fusion, Soup to Nuts". The whole idea was to show all the technical details that's used for building Fusion Apps, by a number of different presenters. I think the idea is quite good, but the operation could be better. Alongside that, the projector screen was way too small for that big room. And one of the speakers couldn't resize his resolution, so his demo was unreadable for everyone who wasn't at the front row. The sequel ended with a presentation of Fusion Applications (by Debra, who else). It even contained a semi-live demo - a.k.a. a viewlet. As Fusion Apps isn't available yet, they weren't allowed to do a live demo. But, I have to admit, the user interface looks very, very slick!
This first day of Collaborate ended with a reception, with some food (pizza slices etc) and drinks. I bumped into Borkur and his colleague Peter (from RittmanMead) and also met Gwen and a colleague of hers (from Pythian).
All in all a nice first day - looking forward to tomorrow as the "real" conference starts!
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…