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...

Comments

Popular posts from this blog

How to create neatly formatted Excel documents using PL/SQL?

If there is a requirement to produce output from an application into Excel, you would probably create a CSV (Comma Separated File) with the data and start Excel to show the data - at least that's what I did...until now. The drawback of this solution is that you could only produce data and no nice layout. But Excel is also capable of opening HTML-files and using this you could create Excel files with data and magnificent layout! Let me give an example: 1. Create a procedure to show the data in formatted in an HTML table. CREATE OR REPLACE PROCEDURE display_emp_list IS v_emp_count NUMBER(5); v_empno NUMBER(8); v_ename VARCHAR2(50); v_job emp.job%TYPE; v_sal emp.sal%TYPE; v_bg_color VARCHAR2(10) := ''; CURSOR c_emp IS SELECT empno, initcap(ename), job, sal FROM emp ORDER BY ename; BEGIN SELECT COUNT(*) INTO v_emp_count FROM emp; owa_util.mime_header('application/ms-excel', FALSE); htp.p('Content...

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 wors...

APEX ReadOnly Pages - The easy way

If your Oracle APEX Application requires different types of access - full access or readonly - for different types of users, you can specify a Read Only Condition on Page level (or Region, Item, Button, etc.).  You can set an Authorization Scheme on Application level, so it'll be applied to all pages. So if you have an Authorization Scheme named 'User Can Access Page' defined by a PL/SQL function like this: return apex_authorization.user_can_access_page ( p_app_id  => :APP_ID , p_page_id => :APP_PAGE_ID , p_user    => :APP_USER );  then you can code all the logic in the database using the APEX Repository, your own tables or a combination to define whether a user has access to that page or not. But alas it is not possible to define something similar Application wide for a Read Only condition. You can specify an Authorization Scheme 'User has Read Only Access' using a similar signature as the one above and use that on each and e...