The Oracle APEX Builder Plugin is now also available for Internet Explorer!
For a long time I was looking for a Greasemonkey like add-on for Internet Explorer. I found several of them, like Greasemonkey for IE, Trixie or Turnabout. But the drawback of all of them is that they are not maintained anymore. In most cases development stopped already more than a year ago and the homepages do not mention if they work with Internet Explorer 7 or not.
One of the “drawbacks” of using the ApexLib Framework is, that you have to remember all the “ApexLib Hints” which you have to use to configure the runtime behavior of the framework.
Ok, after some time you are getting used to them, but still, wouldn’t it be much more comfortable to set this properties as you do it for the APEX properties?
On Wednesday I released the first version of the APEX Builder Plugin, on Thursday I added a small enhancement, but on Friday I had an idea how to really increase the productivity of the Oracle APEX IDE.
People who know me, know that I’m restless and just think about that as long as I haven’t implemented it. 🙂 So I spend some hours of my weekend to enhance my APEX Builder Plugin.
So what excited me that much that I spend another weekend doing some programming?
Just updated the APEX Builder Plugin for Greasemonkey to version 1.1
Are you also setting “Export Comments” to YES each time when you export your Oracle APEX application, because you don’t want to loose your developer comments in the case you have to restore from a previous export. How often have you forgotten and have been lucky that you didn’t have to restore?
Last week I blogged about a resizeable textarea which can be integrated into an APEX application. I thought it would be cool to have this resizeable textareas in the APEX Builder, too.
How could that be done?
Do you like the separate APEX error page which is called when APEX raises an error (eg in the MRU/MRD process for tabular forms)? If yes, you don’t have to read further, if your answer is NO you may should read the rest of this posting…
You like the build-in APEX Debugger which you can be activated through the Developers Toolbar?
All links which APEX is generating when rendering the page contain the debug flag too. But when you enter something into a form and press the submit button or any other button, the Debug mode is disabled and you don’t see what APEX is doing to process the data.
It’s time to “hack” the APEX debugger!
On the OTN forum someone was asking today…
Can I determine if I am running a page “normally” or with the developer toolbar visible, ie as a developer? If this were the case, I’d add in a condition on this to ensure it was always available to me when developing but not to end users.
After looking around in the APEX packages I found the global variable Continue reading
If you have read my previous posting about Caution when using PL/SQL functions in SQL statements and a related thread on the OTN forum, you know that using the V or NV function in your SQL-where clause can have a performance impact on your query.
I have created wrapper functions for V and NV which use the DETERMINISTIC optimizer hint, so that the optimizer/query engine just calls them once for the query and not for every row.