Since Version 4.1 of Oracle APEX – with it’s changed Error Handling – ApexLib didn’t work anymore. The changes in Oracle APEX 4.1 lead to compilation errors in APEXLIB_ERROR-Package.
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.
Oracle APEX 4.0 brought us a “Search Application” functionality which helps really a lot.
Not only can you search there for strings in your application code, you also can enter an page-id and jump directly to the page.
This is so good, that i thought i go a little further and improve it even more. Continue reading
Sounds easy, but standard Page Item Buttons always submit the Page, which isn’t what i wanted.
So i created this little Plugin…. Continue reading
Sometimes you want a user to enter an address which later on can be used to display it on a map. Now you want to make sure, that the user sees what the the map will look like and where his entered address is shown on the map.
This comes in very handy for those users who always seems to forget to enter the whole address.
When that little box on that web form you need to fill in is simply too small to show all your information at once, you wish to make the box bigger.
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