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…

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…