Skip to main content

Collecting ideas for APEX 4.0 Plug-Ins...using Google Wave

As you all know by now APEX 4.0 will have some new functionality regarding the creation of Custom Item Types and Custom Region Types. These types will be called "Plug-Ins". The idea is that there will be a public App Store like library where you can up- and download plug-ins.

A snippet from the Oracle Open World APEX 4.0 presentation:
  • Easy way to enhance the existing built-in functionality of Oracle APEX with new item types, region types, dynamic actions, etc.
  • Developers use in similar fashion to native widgets
  • Wizard support and declarative setting of attributes
  • Included in APEX application export
  • By providing this plug-in system in APEX, we want to engage the APEX community to create a rich ecosystem around Oracle APEX.
The APEX Development Team can’t possibly incorporate all the widgets that developers would like to utilize. By using plug-ins developers can readily incorporate additional item / region types to enhance the functionality, appearance and user friendliness of their applications. Once defined, plug-in based components are created and maintained very much like standard APEX components. We believe that the APEX community will build many plug-ins and make them available to others. Much like with the SQL Developer plug-ins it will be up to the contributors whether these are freeware, etc.

In the demo the APEX Dev Team is showing an Amazon style 'star rating' (as an Item Type Plug-In). (like the image above)

So maybe now is time to gather ideas for Plug-Ins (using this cool collaboration tool). So don't be shy and add your ideas about the Plug-Ins you think you could use (or even create yourself !) or are just very cool....

Custom Item Types
  • Amazon like star rating
Custom Region Types
  • Google Wave
  • Google Visualizations
So please add your own ideas to this wave, and let's make collaboration happen...

Comments

Hi Roel,

Thanks for starting this. As soon as I can get my wave account I'll post some ideas.

Martin
Dimitri said…
Hmm I must be doing something wrong because I don't see the wave ...

Dimitri
Tony Fatouros said…
Hi Roel,

Would love to contribute to the Wave but my Google account has not been activated for Google Wave.

Are you able to send me an invite if possible pls.

Thanks.
Tony.
Roel said…
If I only had some spare invites...
Johannes said…
Great initiative Roel, pity you exclude non-wave users.
Roel said…
@Johannes: In the end we will all be Wavers... (one goal is also to examine the collaboration possibilities of Wave for these kind of things).
BTW: You can also add your ideas as a comment to this post, I'll take care that they'll be entered in the wave.
Cheers
Roel
Johannes said…
Hmm all Wavers, don’t let the “paranoids” amongst us hear that hear this.

Not a bad idea to test Wave with your initiative.

I’d like a Google Map (v3) plug-in, but if I look at the Apex 4.0 “brief” it looks like the built-in mapping will be so good that there might not be a requirement to use Google Maps.

Johannes
Johannes said…
Hi Roel,

I'm not sure it it can be seen as a plugin but I want to suggest it anyway

How about a plugin for Apex "themes", something similar to Joomla's Morph Toolset, see http://www.joomlajunkie.com/templates/morph/morph.html

Or a plugin that converts Joomla templates to Apex templates

Johannes

Popular posts from this blog

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…

Dockerize your APEX development environment

Nowadays Docker is everywhere. It is one of the main components of Continuous Integration / Continuous Development environments. That alone indicates Docker has to be seen more as a Software Delivery Platform than as a replacement of a virtual machine.

However ...

If you are running an Oracle database using Docker on your local machine to develop some APEX application, you will probably not move that container is a whole to test and production environments. Because in that case you would not only deliver a new APEX application to the production environment - which is a good thing - but also overwrite the data in production with the data from your development environment. And that won't make your users very excited.
So in this set up you will be using Docker as a replacement of a Virtual Machine and not as a Delivery Platform.
And that's exactly the way Martin is using it as he described in this recent blog post. It is an ideal way to get up and running with an Oracle database …

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…