Skip to main content

OOW2008 - Sunday

Due to the jet lag this Sunday had a very early start. I was wide awake at 5:oo AM, so I had a long time to check my e-mail, take a shower and eat a full American breakfast. After registering for the conference it took about 5 minutes to walk into someone I know...it's a small world after all.
For me the conference started with a Hands-on-Lab : Extending the APEX Framework with Web 2.0. To me there where just a few new features mentioned in the handbook, but I guess most people didn't finish all examples within an hour. The handbook will be available as an OBE within a couple of weeks. The next session was on Achieving ROI with Oracle Database 11g and APEX. It was about a new application Harvard Pilgrim needed to offer health insurance to individuals. Instead of taking 1000's of phone calls, they decided they needed an on line self service application - and built it in APEX. Another good example how you can build an application with APEX in less than a month. You can find the application here.
After that Joel Kallman presented on Globalization with APEX. Apart from Java (with resource bundles) and .Net (using resource files), in APEX you can do the translation after the development. It needs just 6 easy steps: Map, Seed, Export (to XLIFF), Translate, Import/Apply and Publish. The translated versions of an application are replica's from the original one (with their own application id). You can only make changes to the original application. After changes you just have to make the additional translations and (re)publish the translated one. Live has never been so easy. One free tip from Joel : Create your database using the AL32UTF8 character set, so you can easily handle all languages... Examples of multi language APEX applications are BioQuebec and ProMed. He also announced some new APEX 4.0 features, but I will collect all those features for a separate post.
After the session about Weird PL/SQL by Steven Feuerstein and the - funny political - keynote by Carville and Matalin I went to the Blogger meetup. Allways good to match names and faces...
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…

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…