Skip to main content

UKOUG Day 3

The (rather ambitious) schedule for today was :

Lost in JDeveloper by Sten Vesterli : Sten guided the (Forms experienced) audience in creating an ADF Swing Client App ofcourse declaratively (next to AJAX this is the buzzword of the conference : everything should be declarative, you can be a programmer when you' re able in controlling your mouse ;-) ).
'Christmas
Programming Real Applications with APEX by Andrew Woodward : Again everything declarative but now using APEX instead of JDev. The point was: you can create simple applications faster than using Oracle Forms but when you need more advanced features you'll need to program Javascript and AJAX. But that's only temporarily, because in the next version(s) you also will be able to create AJAX components declaratively.

Modelling on the cheap by Andrew Clarke (I chaired this one) : Andrew sketched out the pros and cons of different modelling tools - from whiteboards to (free) datamodelling tools. As far as he knows the best free datamodelling tool on the market today is Schemester.

Oracle SQL Developer Advanced Features by Sue Harper : Sue pointed out how to make our own extensions - as extra tabs and right-mouse-options - on SQL Dev and demonstrated the power of the Migration Workbench. Also APEX content in your database is visible throug SQL Dev and a nice new feature (in the next version) will be to possibility to view trace files as a very flexible TKProf like output!

Oracle Forms Roundtable by Grant Ronald : In this round table all attendees could present their views on Oracle Forms and what features should be added in subsequent releases. Alas not much came out - I think we are so "comfortable" with the imperfections of Form... Grant suggested a couple of enhancements like a kind of JTable option (where you can click on the header for automated sorting etc) and a new look-and-feel / color scheme. Ofcourse no fixed promises where made...

Integration of BI Publisher and APEX by Dimitri Gielis : Dimitri, enthousiastic as ever, showed the possibilities of using BI Publisher for creating very good looking reports. The integration between the two products is very good. But a great disadvantage is that BI Publisher is not as free-of-charge as APEX is (maybe this is Oracle's way to earn some money out of APEX - apart from the database licenses?).

Special : Trevor Baylis - a World Famous British Inventor : Trevor, a 72 years old 'world famous' inventor (I never heard about him, but he is the inventor of, amongst a lot of other stuff, the wind-up radio - now I understand why we've got one from the organisation) presented his views on " invention". In his opinion you can learn to invent and, just like there is a School of Arts, there also should be a School of Inventions. The presentation was very amusing.

Event Dinner : One hall was transformed into a ' Christmas Eve' kind of room and we all enjoyed the drinks, food and (more or less) the DJ...
Post a Comment

Popular posts from this blog

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 …

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…

Push changed rows to an Interactive Grid

For pushing changes from the database to the end user, the regular solution is using websockets. A change in a record is detected - using a trigger or using the CQN (Change Query Notification) feature - and a notification is send to a websocket server. That websocket server broadcasts the notification over a channel to all browsers that are tuned in to that websocket channel. Then the browser reacts to that notification, usually showing an alert or refreshing a report. This trick is described on multiple sites, just Google for "oracle apex websockets" or similar.

So back in the old days, we used that notification in the browser to refresh the (interactive) report. But along comes the Interactive Grid (IG). While he full-refresh mechanism still works for IG, an IG has also the option to refresh just one row.  So wouldn't it be awesome that just the changed row(s) get refreshed upon a change in the database, instead of the whole report? Can we do it ... yes we can!
First i…