A Glimpse of APEX 4.2

-


Yesterdays OGh APEX day in Zeist (NL) was a great success. The probably largest APEX-only congress (almost 300 APEX enthusiasts) was packed with 3 parallel tracks of presentations covering a wide variety of APEX related subjects.


The OGh organization committee again managed to invite well known APEX experts as speakers: Dimitri Gielis and John Scott (the dynamic APEX Evangelists Duo), Roel Hartman, Alex Nuijten, Patrick Barel (all ACE or ACED so far). Iloon Ellen Wolff, from Oracle NL, gave us some previews on Oracle’s Cloud Service, mostly slides and video’s. A live demo wasn’t possible, because there is something going on at Oracle and we may can expect some exciting news very soon.
The highlight, in my eyes, was Patrick Wolf’s keynote presentation, talking about the recent enhancements of 4.1.1,and, much more exciting, giving us a glimpse of what will come in the long awaited 4.2 upgrade. After showing the usual “Oracle Save Harbor Statement” the conference participants were treated with some live demos of the Oracle Application Express teams work on the new version. As far as I can tell now, they are doing a great job, especially in integrating the jQuery Mobile framework into APEX in a way that perfectly fits the “declarative way” you would expect from building applications with APEX. To mention just a few highlights (well, you know: everything mentioned might OR might not be a feature in a future version of APEX):
Multiple theme support in one application: means you can create mobile and “standard” pages in one application. This enhancement would take away the need to build and deliver separate applications for targeting different devices.
  • HTML5 Form Input Type support
    • This is a really essential feature for mobile support. APEX 4.2 will (or may not) support sub types for (Text) input elements.
  • Declarative Configuration
    • If you have taken a look at the jQuery Mobile framework already, you know that its components configuration is done by adding additional “data-” HTML attributes. In the screens I saw, these attributes where translated and integrated as element/region properties, just as you are used to from other APEX builder screens.
  • List-Views
    • One of the main components in jQuery Mobile with respect to presenting data on a mobile device will be (or may not be) very well integrated and support (or may not) all the major features the jQuery Mobile framework has to offer in a declarative way, like List Dividers, Count bubble and Search Bar Filter.


Pity I didn’t take any photos of APEX Builder screens during Patrick’s presentation. I was too busy modifying my own presentation about jQuery Mobile usage in version 4.1 that was scheduled later that day. I just had to refer to his presentation somehow. Integration jQuery Mobile “manually” looks so clumsy, compared to what we can expect from Oracle Application Express 4.2. I’m looking forward to the first (EA) releases of 4.2. When will that be? That’s the one question Patrick didn’t answer, not even under “Save Harbor” conditions.

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