Skip to main content

ODTUG: Tuesday

By
One of the highlights of todays conference was the "Plug-In Showcase" where Anton, Dietmar, Dan, Dimitri and Doug each showed a plugin they wrote the last couple of days. They showed some real simple ones, like a hover function up to more complex things like a Netlfix style drag and drop functionality. The conclusion is; Once you get the hang of it, writing Plug-Ins isn't that hard - and using good Plug-Ins is very simple. So Plug-Ins enhance your development speed dramatically and can be an enormous improvement to your end-user experience.
One other session was about changing the look-and-feel of your APEX page, using the templates and changing the css. The new Theme 4 in APEX 4.0 is even shipped with PSD (Photoshop) files that contain the sprites (a collection of images within one file) used within that template. You can edit these files in order to change the look of the buttons, regions and whatever else there's on your page.
Another nice one was "Oracle Trace Data for Developers" by Cary Millsap. The core message is: Don't purely rely on your tkprof output to analyze your performance (issues), because tkprof leaves out a lot of information that is in the raw data of the trace file, You might have to read and understand the trace file itself to get to the bottom of a problem.
Martin d'Souza did a a very nice job in his presentation about using the APEX Dictionary to improve your user interface by changing the way APEX shows the help, error handling etc. All done very nicely. Most (if not all) solutions also are available on his blog.
There even was a evening session today (visiting ODTUG is really hard work): A live PL/SQL Challenge by Steven Feuerstein. 10 nasty questions on PL/SQL had to be answered. When Steven showed the answers it now and then became more a Steven F Challenge, because some answers where not that obvious and clear and led to a lot of discussion - which was very good and fun to do! And of course congrats to Alex Nuijten who won the 500-dollar first prize. I ended up 7th and received a copy of Steven's lates book: PL/SQL for 11gR2 - 2 kilo added to my luggage!
After this a part of the Dutch contingent (Iloon, Learco, Alex and myself) went out for some fine Lebanese food. We closed off the day with a(nother) few drinks at the bar.
Labels:
Location: Woodley Park, DC, USA

Comments

Post a Comment

Popular posts from this blog

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

By
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...
21 comments
Read more

Refresh selected row(s) in an Interactive Grid

By
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...
Post a Comment
Read more

APEX ReadOnly Pages - The easy way

By
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...
Post a Comment
Read more