Skip to main content

OOW2011 - Right around the corner!

Within one week San Francisco will be colored "Oracle red" again for Oracle Open World - including Oracle Develop and JavaOne. Around 50,000 - usually easy to recognize - attendees will cover the streets, while moving from one conference location to the other. And I am privileged to be one of them! In fact, I am even more privileged to attend the Oracle ACE Director briefing at Oracle HQ in Redwood on Thursday and Friday before the big event... So that will make about 1.5 week in the Bay Area.
Creating a schedule for OOW is as difficult as ever. No matter what tools they provide, the endless possibilities of picking that most interesting session amongst the 100 in the same time slot is cumbersome. And then there are all the "social events"... it is hard to pick the right one there too, because there is a large amount of overlap as well. But I managed...and created this schedule for that week - where orange = APEX, green = social and the rest is....well, the rest.


So it is going to be a busy week...but good fun anyway. The thing I like is that there are no "real" sessions before 10AM!

Comments

Dimitri Gielis said…
Hi Roel,

The APEX Meetup is planned for Tuesday... in your agenda you have it down for Monday, unless that is another meet up? ;-)

Just thought to tell you,
Dimitri
Roel said…
Thanks for pointing that out! It reduces the overlap just a little... They didn't gave you the best time slot of the event, did they? See you on Wednesday (probably)!

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…