Skip to main content

Get your abstracts in for the best conference of 2014 !

We're just in the second half of the 2013 and now we're already talking about "The best conference of 2014"? 
Yep! And this conference will be held on Jun 22-26 in Seattle. So I am talking about ODTUG Kscope 14. What else could it be .... And the best conference needs the best preparation.  And as content is one of the main things that makes this conference awesome, we need our content lined up as soon as possible. And that's why the call for papers is open now and will be open until October 15 (no extension!). So you still have two months to come up with a subject you're passionate about. If there is something you want to share with the Kscope audience, this is your chance. As we need content for all attendees, from beginner to advanced and for every subject, I am pretty sure you can think of a few things that you can talk about! And this is also an excellent opportunity to dive into a subject and learn yourself: Just submit an abstract of something you want to know more about yourself! 

As the Content Lead for the APEX track, I've already selected a team of 12 knowledgable persons that will evaluate all abstracts after October 15 in order to construct the best APEX track ever!

O yeah, did I mention you get a free pass when you're abstract is selected? Makes it even more worthwhile!
See you in Seattle!

For registration, information, submit your abstracts and more, see http://kscope14.com/
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…