Skip to main content

Using Static Files in APEX has never been easier !

By
Almost every APEX Developer knows that JavaScript and CSS belongs in separate files and (in 99% of the use cases) not somewhere in your Page properties. If you have this code in separate files it is easier to use them in a Version Control System (SVN or Git) - if the files are outside of APEX. And the code you store in these files can be reused, in contrast to the stuff you store on Page level.
In a lot of environments it is harder to use external files, because deployment of these files to the appropriate location on a webserver requires special privileges that not everybody has. In those cases storing these files as Static Application Files or Static Workspace Files might be a better solution.
It makes deployment easier, because these files will be exported and imported as part of the application. You can't accidentally forget about them. But working with these files is quite a pain. When you need to edit something you have to download that file, make the changes, upload it again and refresh the page to see the result (either positive or negative). One tool that overcomes that repeated cycle in APEX Nitro. Nitro uses JavaScript (node) behind to seems to facilitate the upload / refresh part of the development cycle. Pretty cool. But it is another tool that runs outside your browser and it requires the installation of node. No big deal but still.

Just recently I stumbled upon a tweet of the guys from FOEX telling about a new initiative FOEX Open Source (a.k.a. FOS). And they started this initiative by releasing a browser extension - for Firefox and Chrome - that facilities editing of Static JavaScript and CSS Files straight in the browser. Big advantage: No more uploading, changing, uploading cycle anymore. Just change, save and refresh!

When you install the browser extension, a little Select List appears in the page where you can see your Static Application (or Workspace) Files. You can just select one of your files there and a built-in editor appears with all the nice Visual Studio Code features we all know and love.
So you have syntax highlighting and can edit multiple files at the same time in different tabs - either behind each other or next to each other (left to right or top to bottom).
And it's not just that you van Edit and Save the file, there is also a "Minify" option. So you can even do that directly from with APEX! That is really cool.
And to top that all off, you can also create (or edit) Less files and compile these to CSS (and minify them) in one go. 
So no more excuses for not using files anymore! It will never get easier than this ....
You can download the extension from the webstores for Chrome and Firefox.






Comments

Veerendra P said…
Hi Roel,
I imported the chrome extension. When I open the file, edit and save, it always hangs for for me. After some time I get the error
saying cannot save because the session may have expired.

I am using APEX 19.1, hosted on AWS using standalone ORDS.

Any suggestions please?
10:29 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