Skip to main content

Rumors about APEX 4.0 release date on OGh APEX Day

By
Yesterday the OGh (Dutch Oracle User Group) organized a full day about APEX. There was a very good turn-up of about 150 attendees and about 10 sessions to choose from.
A couple of attendees already blogged about it like Rob, Michel and Dimitri. I agree what they already have written so I won't repeat it.

There also was a rumor - that I heard of before, so it might be true - that APEX 4.0 is planned to be released just before/after or even during ODTUG... So around the end of June we will experience if the source of the rumor is a reliable source or not...
Labels:
Location: Het Rond, Zeist, The Netherlands

Comments

Patrick Wolf said…
Rumors, rumors, rumors... :-)
1:38 pm
Pat Miller said…
Are any html 5 features being built in to Apex 4?

Pat Miller
3:10 pm
Patrick Wolf said…
Hi Pat,

what HTML 5 feature would you like to see.

Regards
Patrick
11:02 am
Pat Miller said…
Some of the features I have read about like:
Vector graphics -- svg enhanced
Web workers --background processing of more complex scripts
Embedded videos

Pat
4:31 pm
Unknown said…
I think the more useful features of HTML 5 for APEX are multiple file upload and local storage, perhaps to cache navigation elements and lists of values. I agree that web workers would be useful as the ajax events get more complex. APEX doesn't really need to do anything to support video in HTML 5.

Tyler
4:14 pm
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