ODTUG Kaleidoscope 2009 - Monterey, CA

-
 
Last week I visited the ODTUG Kaleidoscope 2009 Conference in Monterey, California. Now, that I got over my jetlag and back to work, I'm trying to order and evaluate all the impressions, ideas and inspirations I got during this event.

I brought three green flashlight bouncing balls back home for my kids (got them from one of the exhibiting vendors). Of course they had lots of fun test-bouncing these goodies immediately. This is, kind of, what I feel right now: I really would like to start playing around with some of the techniques, tools and frameworks I learned about ("research", as I would describe it to my manager).

On second thought, evaluating the information I got, putting it into my work's context and then test driving it seems a better approach to me. Definitely when I saw the devastating effect of the bouncing balls on our livingroom's interior. ADF, APEX, jQuery, REST, SOAP, SOA, jXLS, ... when to use what and where? Still, the technique is not the driver, but the result that has to be achieved. So, I’m going to take a step back and take my time for a hype-free, closer look into some topics. I will try to share my findings in this blog.

Comments

Post a Comment

Popular posts from this blog

Remember Me - APEX Autologin

-
Image
I promised to publish about this subject to one of the attendees during my presentation at KScope 12 in San Antonio. I used this functionality in my demo application ( FifApex ) and it seems there is interest in how to do this. Most of the public websites like Facebook, LinkedIn, Twitter, Amazon or OTN do have it: an option to stay logged in, even if you closed the browser, so you do not have to authenticate each time you visit the site again. I’m pretty used to it and would be surprised if a website didn’t offer this convenient feature. OK, it’s not entirely secure, but, as I said, very convenient. I’m working on a “consumer” site/application, I’m building it with APEX and I want to offer this “remember me” option too. I knew an APEX based website that does offer this feature ( www.plsqlchallenge.com ) and I had a chat with the developer that implemented it’s login mechanism, Paul Broughton from Apex Evangelists . So, here my thanks to him for the original inspiration.   Or...
Read more

Dynamic Date Range in APEX Datepicker - no Plugin required

-
Image
The build in jQuery UI Datepicker of Application Express is a very versatile component and it is very easy to configure the basic settings with the Page Item properties. One of the properties you can set, is the range of selectable dates by entering a Minimum and Maximum Date value. The “syntax” of these values is based on the jQuery UI Datepicker components date format capabilities, so this might be looking a bit awkward to us Oracle folks at first sight. Next to giving a static value or one of these Datepicker calculations you can reference an APEX Page Item to set the range values, which is a nice thing as we are able to calculate a range dynamically, based on some database value/calculations. The bummer is: the calculation only gets executed during the rendering phase of the page and changing the referencing Page Item’s value won’t change the Datepicker range. What you really want (yes, you do), is to be able to reference Page Items to control the Minimum and Maximum Date dynamica...
Read more

Tabular Forms on Complex Views - using INSTEAD OF Triggers

-
Image
Creating tabular forms in Apex is relative straight forward. One gets fully generated, instant insert/update/delete functionality. Unfortunately (for the form developer), tables are usually part of a more or less complex data model, which is optimized for data storage, rather then for form-layout. Well, Apex offers some possibilities to the developer to enable tabular forms beyond 1:1 table based. Collections One alternative is to create your tabular form using the Apex Collection API. There is a good article on Martin Giffy D'Souza’s blog describing this technique. This collection-approach basically pre-fetches data into a (PL/SQL) collection from a query/cursor. The “collected” data will be displayed in the form. An on-submit page process will store the data submitted from the form into the collection. After this you can perform some validation before submitting the data to table(s) in an on-submit page process. Database Views Well, I favor an approach that keeps the...
Read more