A few years ago it was deemed state-of-the-art to store any kind of extra resources (images, css/js-files) directly on the webserver.
Of course this was just the best-practice, left with many who were not able to follow because of company restrictions: no access to web server, not allowed to store files, too many regulations, and so on.
Luckily APEX 5++ gave us nicely working Static Application Files and Static Workspace Files. Now everyone is using those to store extra files.
Quick note: I finally managed to get the APEX Developer Addon signed by Mozilla and therefor working again in Firefox 43 upwards.
Please re-download and install, version of the Addon in Firefox is now 2.0.0.49. No changes for Chrome.
Apologies for the inconvenience and thanks for all those mails I got.
After the APEX Developer Addon broke in Chrome 27, I had to change the underlying architecture and do a rewrite of the Addon basis.
Some nice guys helped me Beta-Test that over the last week. Now it should be good to go.
With Chrome Version 27 a security bug in the browser was fixed which caused the APEX Developer Addon to break.
Thanks to all sending me a reply about that, i’m currently working on a fix and hope to be able to provide that soon.
In the meantime please stay calm and use Firefox instead.
P.S.: no, the APEX Developer Addon didn’t exploit a security hole. It is just an unhappy coincidence that fixing one security problem broke our extension.
I just released a new Version of the ApexLib APEX Developer Addon, a great tool that brings more features and functionality to your APEX Application Builder without installing anything in your Database.
It is a simple Addon for Firefox and Chrome Browsers, and can be installed in a few easy steps.
It’s been a long while since i blogged about a Tool i started to write which would replace the original APEX XLIFF Export and produce XLIFF 1.2 compliant Files instead.
The Benefit is breathtaking, suddenly your Translators are able to know what they are translating – that means where the text they are working on is used. e.g. on the Action-Button in Region XY on Page 234.
This can help your Translators delivering better and more meaningful Translations.
One of the many good things about Oracle APEX is the builtin capability to create multilingual Applications. It gives you a set of tools to translate your Application and provide it in multiple languages at the same time.
One of the Key Components of this Translation Mechanism is the creation of an XLIFF File. This File contains all text strings of your Application (that is all your UI Strings, not your Data) and from which to which language it should be translated.
A couple of days ago i got an emergency call from someone who attended my presentation at DOAG 2010 about APEX Translations.
Apparently they deleted (by accident) their APEX Translations (which reside in WWV_FLOW_TRANSLATABLE_TEXT$) and have neither a DB-Backup of this table nor a Backup of the XLIFF Files. Continue reading
One nagging thing about APEX occurs often to me. It’s the inability to customize the Workspace Login Page.
In APEX Instances within corporations you may want to display your own Logo or some custom text explaining your developers what to do and what not.
Do you know this: You just wanted to try something out and after a couple hours playing around with APEX you already have a pretty good application.
Problem is, you experimented on a demo-workspace or on apex.oracle.com and now want to move everything to your own personal development workspace.