Skip to main content

ODTUG: Tuesday

One of the highlights of todays conference was the "Plug-In Showcase" where Anton, Dietmar, Dan, Dimitri and Doug each showed a plugin they wrote the last couple of days. They showed some real simple ones, like a hover function up to more complex things like a Netlfix style drag and drop functionality. The conclusion is; Once you get the hang of it, writing Plug-Ins isn't that hard - and using good Plug-Ins is very simple. So Plug-Ins enhance your development speed dramatically and can be an enormous improvement to your end-user experience.
One other session was about changing the look-and-feel of your APEX page, using the templates and changing the css. The new Theme 4 in APEX 4.0 is even shipped with PSD (Photoshop) files that contain the sprites (a collection of images within one file) used within that template. You can edit these files in order to change the look of the buttons, regions and whatever else there's on your page.
Another nice one was "Oracle Trace Data for Developers" by Cary Millsap. The core message is: Don't purely rely on your tkprof output to analyze your performance (issues), because tkprof leaves out a lot of information that is in the raw data of the trace file, You might have to read and understand the trace file itself to get to the bottom of a problem.
Martin d'Souza did a a very nice job in his presentation about using the APEX Dictionary to improve your user interface by changing the way APEX shows the help, error handling etc. All done very nicely. Most (if not all) solutions also are available on his blog.
There even was a evening session today (visiting ODTUG is really hard work): A live PL/SQL Challenge by Steven Feuerstein. 10 nasty questions on PL/SQL had to be answered. When Steven showed the answers it now and then became more a Steven F Challenge, because some answers where not that obvious and clear and led to a lot of discussion - which was very good and fun to do! And of course congrats to Alex Nuijten who won the 500-dollar first prize. I ended up 7th and received a copy of Steven's lates book: PL/SQL for 11gR2 - 2 kilo added to my luggage!
After this a part of the Dutch contingent (Iloon, Learco, Alex and myself) went out for some fine Lebanese food. We closed off the day with a(nother) few drinks at the bar.
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…