Skip to main content

ODTUG Kaleidoscope 2008 : APEX rules!

In a couple of weeks ODTUG's Kaleidscope 2008 takes off. This years theme seems to be: APEX, APEX and again..APEX. At least, for me it is. Because my preliminary schedule is packed with 24(!) APEX sessions in 5 days. So at Thursday afternoon I should know everything I always wanted to know about APEX, but were afraid to ask.
I'm looking forward visiting New Orleans and meet again some friends from the Oracle blogosphere. I will report back my findings here!

So here's the schedule:

































DateFrom To Title Presenter
Sunday 9:00 10:00 Managing the Army's Enterprise Real Property Planning with Oracle APEX Bharat Pappu and Brian Duffy

10:00 11:00 Creating Dynamite Applications that Deliver Kathy Hunsicker

11:15 12:15 Oracle Application Express: Power to the People Rich Mutell, Dimitri Gielis, John Scott

13:00 14:00 How IntelliReal used Oracle Application Express to Rapidly Build their Production Environment Chris Ostrowski

14:00 15:00 Mastering Unreasonable Deadlines with APEX at the German Telecom Shops Dietmar Aust

15:15 16:15 How Iron Mountain Has Used APEX to Improve Operational Abilities Within the Enterprise Chris Veenstra

16:15 17:15 APEX Roundtable With Panel of Presenters Moderated by Scott Spendolini

18:00 19:30 Welcome Reception and Jam Session
Monday 10:30 12:00 APEX Hints, Tips, and Best Practices John Scott

13:15 14:15 The Top 10 - No 11 - New Features of Oracle Database 11g Tom Kyte

14:30 15:30 Forms Migration to Java ADF Rohit Bhalla

16:00 17:00 Use the Power of APEX Dictionary Views to Increase the Quality of Your APEX Applications Karen Van Hellemont

17:15 18:15 Oracle Application Express (APEX) Version 3.1 David Peake
Tuesday 8:00 9:00 APEX Development: Watch It Live Bill Holtzman

9:15 10:15 You Can't Do THAT in a Browser! Extending Oracle APEX with Third Party Components Scott Spendolini

10:30 11:30 Advanced Oracle Application Express Tips and Techniques Chris Ostrowski

12:45 13:45 APEX Experts Panel (SIG) Scott Spendolini

14:00 15:00 Application Express in Support of Institutional Strategic Planning Tanya Podchiyska

15:15 16:45 Writing a Custom Authentication Scheme for Application Express: A Case Study Raj Mattamal

17:00 18:00 Explore and Benefit the APEX Repository Michiel Jonkers

18:00 19:30 Meet the Oracle Ace Directors and Oracle Aces Reception
Wednesday 8:00 9:00 Creating Dynamite Applications in Application Express that Deliver Kathy Hunsicker

9:15 10:15 Building Advanced Tabular Forms Marcie Young

10:30 11:30 Creating Advanced Charts in Oracle Application Express Dimitri Gielis

13:30 14:30 Increase Your Oracle APEX Development Productivity with Open Source Tools Patrick Wolf

14:45 15:45 How to Hack an Oracle Application Express Application Anton Nielsen

16:00 17:00 Building the New Stuff: AJAX, JSON, and APEX 3.1 Carl Backstrom

18:30 21:30 New Orleans Party
Thursday 8:30 12:00 APEX Versus ADF Lucas Jellema, Dimitri Gielis

Post a Comment

Popular posts from this blog

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…

Refresh selected row(s) in an Interactive Grid

In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid. The use case I'll cover right here is probably more common - and therefore more useful!

Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user.The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even worse) while you…

Dockerize your APEX development environment

Nowadays Docker is everywhere. It is one of the main components of Continuous Integration / Continuous Development environments. That alone indicates Docker has to be seen more as a Software Delivery Platform than as a replacement of a virtual machine.

However ...

If you are running an Oracle database using Docker on your local machine to develop some APEX application, you will probably not move that container is a whole to test and production environments. Because in that case you would not only deliver a new APEX application to the production environment - which is a good thing - but also overwrite the data in production with the data from your development environment. And that won't make your users very excited.
So in this set up you will be using Docker as a replacement of a Virtual Machine and not as a Delivery Platform.
And that's exactly the way Martin is using it as he described in this recent blog post. It is an ideal way to get up and running with an Oracle database …