Skip to main content

ODTUG Kaleidoscope 2008 : Day 4 - ADF vs APEX and Wrap Up

The last morning of this years ODTUG was completely filled with one three hour session: APEX versus ADF 'shootout'. Although the presenters, Lucas and Dimitri, quickly stated that there was no violence to be expected, the audience was hoping for some clear statements.

Lucas and Dimitri both built an application using their favorite tool and demo'ed it to the audience. Both failed on one part - as live demo's tend to do - so it was 1-1 at mid time. After the break the match continued with some nice features shown on both sides. Both presenters where dared to say something positive on the other tools. For Dimitri this was the most difficult part: "I can't come up with anything nice to say about JDeveloper".

After a complete comparison, there was one clear winner: The audience!

Thanks to both of you guys for this joint effort!

So to wrap up: ODTUG is a great event. Not great in the sense that you're overwhelmed with 1,000's of people (there were about 700 attendees), but exactly the opposite. Due to the fact that it is rather small, you'll find yourself having a beer (or two) with all kind of guru's, experts, co-bloggers etc. Especially that relaxed, cool atmosphere is what makes ODTUG such an excellent event.

One more note about 'atmosphere': New Orleans in June is so hot and humid, that you barely can stand the outside temperature for more than 10 minutes - on the opposite : inside (in particular inside the Sheraton) the air conditioning is turned to the max. So every time you get from the outside to the inside, or the other way round, you have to deal with a temperature difference that feels like a 20 C.

Also the Sheraton is a good place to stay and from the 43th floor I had a great view on the river. Could have been better if somebody had cleaned the window - but who cleans windows at that height?

I hope to see everybody again next year - in Monterey (?).
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…