Skip to main content

Why do I attend Kscope?

Kscope14 will be my 6th Kscope event. After New Orleans, Monterey, Washington, Long Beach and New Orleans again (yes, I missed San Antonio), this year Seattle will be the place to be at the end of June.

So why do I spent quite a lot of time and money to visit this event? That's because of two reasons: the content and the fellow attendees. Without any doubt the content of Kscope is best you can get in one conference. And it doesn't matter whether your interested in database development, APEX or Hyperion, there's only one conference with that much awesome presentations. And that draws a certain type of people: your fellow attendees. The size of the event and the location (usually) offers an unique opportunity to meet and greet whoever you want. You don't have to make an appointment to talk to someone, as there is a huge chance you'll run into each other at a presentation, during lunch or at the bar. Speaking of lunch ... there is no conference or event that serves better food than Kscope!

During Kscope14 I will do two presentations myself. One in the beginners track about "Starting mobile development with APEX" and one about "Creating hybrid APEX applications".

As the APEX Content Lead, I am looking forward to all (APEX) presentations. Especially all the planned APEX 5 presentations will have my attention. Apart from those I planned to attend the "Pins, Polygons, and Perspectives: Visualizing Geographic Data in APEX" by Christoph Ruepprich and "Oracle APEX + Node.JS A Primer" by John Scott.
Another thing I also like (and has been requested during previous conferences), is the "intro track". So the first two days of the conference we do have one (out of three) complete track 100% dedicated to APEX beginners. And another thing I'm fond of are our "newbie slots". In order to prevent an unequal competition between newbie presenters and well known APEX rock stars, we planned the presentations of the Kscope newbies against each other. So they all get an equal chance to get a full room!

So, right now you understand I am looking forward to Kscope14 a lot. And I hope I'll meet you there in June. Visit http://kscope14.com for all details, abstracts, location and registration.

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…