Skip to main content

The joy of international travel ... not

This morning I arrived rather early at SFO. When checking in I noticed that the first leg of my trip was delayed by almost 2 hours. And, originally, had a 1.5 hour layover in Minneapolis. So that wouldn't work anymore...
So Delta rescheduled my whole trip: From San Francisco to Los Angeles to Paris to Amsterdam. With a couple of hours of layover at each stop. Initially I would arrive around 11 AM in Amsterdam, but that will be around 8 PM now! So a nice 9 hour delay.
Luckily SFO offers a free 45 wifi service. As I have three wifi enabled devices I am fine for over 2 hours. I must get as much sleep as possible at every leg, to feel just a little bit alive tomorrow. Or the day after that. The one and only positive thing is that I can head straight to bed when I finally get home.
I really realty hope no other delays will pop up... (to be continued)

The continuation
So SFO - LAX took about 1,5 hours, then 3 hours of waiting. Next a 9 hours flight to Paris, and of course I got a seat right in the middle of the plane (no aisle, no window). Managed to get some sleep though. And saw a really nice movie: Greenberg. With Ben Stiller in a much less funnier role than usual. And the first part of When You're Strange, a "Rockumentary" about The Doors. Saved the second part for the next morning. Managed to get some sleep. Then in Paris another 4 hours of airport lallygagging. Another 1 hour flight to Amsterdam, a 1,5 train ride and then - finally - home. And also my luggage made it...
So a very, very, long trip indeed. But OOW was worthwhile. Again.

Comments

Johan Bolhuis said…
Hoi Roel,

Een beetje troost voor je, morgen mag je de hele dag rusten. Alexandra en ik zitten op de bank snot verkouden te wezen, dus de afspraak is verzet.

Groetjes en een voorspoedige reis verder,

Johan Bolhuis

(Tip voor jou en Linda: www.lettinggo.tv kun je de movie als stream bestellen. Wij vinden het een aanrader.
saban_arslan21 said…
This comment has been removed by a blog administrator.

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…