Skip to main content

ODTUG: Wednesday

This day started off with a very nice presentation about the joys of Javascript by Dan "The Man"McGhan. In a very nice pace he took the audience by the hand and increased the difficulty level step-by-step. His key message was; Don't be scared of Javascript, because if you look close enough it is looks more like PL/SQL than you might think at first sight. Get to learn jQuery and do your thing!
Another nice presentation was about "RESTful Web Services" by Jason Straub. He demoed how you can use webservices withing APEX to manage the buckets and contents on an Amazon S3 cloud environment. He also pointed out that not only APEX can consume webservices, but also can act as the source of a webservice. In order to achieve that you have to create a report on a public page that returns either XML or Json. He didn't show a demo, but promised to get out a paper or how-to out there next week. Have to try that myself soon!
Another fine session was Tim St. Hilaire's session on "APEX and AJAX". Nice examples on how to handcode your Ajax processes (the 'old' way) and how to new Dynamic Actions to do it the APEX 4-way.
Then, finally, it was my turn to show the coolest Plug-In of the conference - at least, that's my humble opinion ;-). Around 60 - 70 people showed up and the presentation went very well. ended right on time again!
After that, I didn't have the energy to attend another session and just had a beer at the bar with some other Europeans (Debra, Alex, Marco, Jonathan, Tim etc).
Then it was time for the "big party": good food, more than enough drinks and a very good comedian (John Heffron). After some more drinks in the Presedentail Suite (thanks Mike Riley) it was time to head off to bed....

Comments

Popular posts from this blog

apex_application.g_f0x array processing in Oracle 12

If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one:
then you disable the "Escape special characters" property and the result is an updatable multirecord form.
That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for processing y…

Adding items to your Interactive Grid Toolbar

The APEX Interactive Grid uses the Toolbar widget to create the default Toolbar showing the Search box, Actions menu, Save button etc. And since quite a while there is a nice Plugin "Extend IG Toolbar" by Marko Goricki that makes it very easy to add additional buttons to the Toolbar.

But what if you need more than a button? 
Inspecting the contents of widget.toolbar.js, you can easily spot there can be added more to the Toolbar than just a button: The type of control, available values:
"STATIC", "TEXT", "SELECT", "BUTTON", "MENU", "RADIO_GROUP", "TOGGLE".
The first example will show a way to easily switch from one filter to another. Of course we could use the standard functionality and create two different Report views, but using a Radio Group on the Toolbar gives a more "Tab" like user experience.

So how can we create a Radio Group that looks like a switch in the Toolbar?
In the Javascript Code …

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…