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…

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…