Skip to main content

Riga Dev Day 2015

While waiting at the airport for my plane back to Amsterdam, I have some time to write down my experiences of the last few days in Riga.
After arriving in the hotel, I walked to the old part of town and strolled around. The old part looks very medieval (it is - so no surprises there) with cobblestone streets, old houses and very few cars. Nice!
Then back to hotel, in time for the "official" speaker tour. With a small bus we toured around town for 45 minutes and we walked the old town (again) for another 45 minutes - but now including some stories about the buildings we saw. It was rather cold, so I was quite happy when we got back to the bus and on to the restaurant for the speakers dinner. All very well organised "extra's". Thanks guys!

The event itself was held in a movie theatre in a mall. About 400 attendees filled up the large keynote room pretty quickly. The nice thing about this setting is that the screens are huge and excellent: I've never seen my presentation that big! Also the fact that some people were eating popcorn during the presentations added something to the "movie effect". I would like to see more events in venues like this!
As they conference was a combination of three user groups (Google Dev, Java and Oracle) it was very easy to attend a session that is way out of my comfort zone. So I did a few sessions on Android, Node and REST API's. Just to see something different. My own session was well attended with around 50 people. Just a few of them were actual APEX Developers, the rest was DBA, PL/SQL - or out of their Google/Java comfort zone.
After the event we grabbed a cab bak to the hotel to drop off our bags and a cab back into the old town for the afterparty. Music, some food and lots of drinks. It was fun. Afterwards a cab back to to hotel for the after-afterparty. 
This morning after checking out, I walked back into the old city to check out the parts I haven't seen yet, like the big market halls. Then taxi back to the airport...

All in all a great event, very well organised. Thanks for inviting me - and thanks to the Oracle ACE program for the support !
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…