<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/apexlib/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/apexlib/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Sun, 29 Nov 2009 22:25:08 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/apexlib/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>corrections in integration script</title><link>https://sourceforge.net/p/apexlib/feature-requests/104/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I have installed Apexlib with the ApexLib_integrate_into_application.sql.  Browser validation is turned off by default, however I could not find any documentation on how to enable it.  I hunted through the manual process and came accross it by accident by opening all the application items, process, regions, etc in my application.  In the manual installation it is turned on by default.  I am a novice but it would be nice if it was turned on by default as I have spent all day just trying to find this:&lt;/p&gt;
&lt;p&gt;ApexLib_Browser.initValidation&lt;br /&gt;
( pShowRequiredWarning =&amp;amp;gt; TRUE&lt;br /&gt;
);&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Blackstone&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Peter Raganitsch</dc:creator><pubDate>Sun, 29 Nov 2009 22:25:08 -0000</pubDate><guid>https://sourceforge.net7406e32793b08586556dcfbaa25d64901d22e877</guid></item><item><title>create static LOVs APEXLIB_BOOLEAN_1_0 and Y_N</title><link>https://sourceforge.net/p/apexlib/feature-requests/103/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Create the Static LOVs APEXLIB_BOOLEAN_1_0 and _Y_N in the integration script.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Peter Raganitsch</dc:creator><pubDate>Sun, 22 Nov 2009 21:24:30 -0000</pubDate><guid>https://sourceforge.netfcf870b6bf31a5b5f9caa2cb3bb66a63cb30f6da</guid></item><item><title>automated apexlib integration</title><link>https://sourceforge.net/p/apexlib/feature-requests/102/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;To make apexlib integration into user applications even more easy it would be great to have a script which does the actions described in document "Howto Integrate", Section "Integration into your Application".&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Peter Raganitsch</dc:creator><pubDate>Wed, 22 Apr 2009 17:13:34 -0000</pubDate><guid>https://sourceforge.nete9b1b9dba7f7e5bed54c61c3b78e5e33fc91d277</guid></item><item><title>German ApexLib Error Messages</title><link>https://sourceforge.net/p/apexlib/feature-requests/101/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Documentation howto_integrate.html, Section 8, describes how the error messages raised by ApexLib can be translated to other languages than english.&lt;/p&gt;
&lt;p&gt;It would be much more convenient if ApexLib was distributed with language files which contain these text messages. &lt;br /&gt;
This approach would be similiar to the apex installation itself, where other languages have to be loaded additionally to the default language english.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Peter Raganitsch</dc:creator><pubDate>Thu, 11 Sep 2008 15:46:59 -0000</pubDate><guid>https://sourceforge.net19820ae0896f4f654f48c4aa533653e696a3d241</guid></item><item><title>Add trim for page items and tabular form columns</title><link>https://sourceforge.net/p/apexlib/feature-requests/100/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Add an automatic TRIM to remove leading and trailing blanks of page items and tabular form columns.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Patrick Wolf</dc:creator><pubDate>Sun, 08 Jun 2008 13:55:23 -0000</pubDate><guid>https://sourceforge.net3ed85e437d17bff3e6b8e23677ee762d617ca42d</guid></item><item><title>Merge changes into 1.7 codebase</title><link>https://sourceforge.net/p/apexlib/feature-requests/99/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Merge different changes into the 1.7 codebase&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Patrick Wolf</dc:creator><pubDate>Sun, 08 Jun 2008 11:40:30 -0000</pubDate><guid>https://sourceforge.net1447121f723273fa23148a78b0c09814cb4031e7</guid></item><item><title>Add cascading support for shuttle</title><link>https://sourceforge.net/p/apexlib/feature-requests/98/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Add cascading support for shuttle.&lt;/p&gt;
&lt;p&gt;Code contribution from Kathryn&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Patrick Wolf</dc:creator><pubDate>Fri, 09 May 2008 18:54:37 -0000</pubDate><guid>https://sourceforge.netc81aa44f34e026b43100a05cb9935e63e3e08ba4</guid></item><item><title>Add version check for drop in replacement</title><link>https://sourceforge.net/p/apexlib/feature-requests/97/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The drop in replacement functions V, NV and DV are always dangerous when a new APEX version is installed, because they still point to the old schema name which causes problems when the application is executed.&lt;/p&gt;
&lt;p&gt;Some kind of version check should be added to verify if a new APEX version has been installed.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Patrick Wolf</dc:creator><pubDate>Wed, 12 Mar 2008 13:16:56 -0000</pubDate><guid>https://sourceforge.net726af25278490e8f7429d5d7448c3656e0c57b4b</guid></item><item><title>Add support for the new item type HIDDEN_PROTECTED</title><link>https://sourceforge.net/p/apexlib/feature-requests/96/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Add support for the new item type HIDDEN_PROTECTED which has been added to Oracle APEX 3.1&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Patrick Wolf</dc:creator><pubDate>Fri, 11 Jan 2008 23:35:53 -0000</pubDate><guid>https://sourceforge.netb6cc1eb03e2ba4e2ebb62c384586c63432d39f6f</guid></item><item><title>Configurable temporary tablespace</title><link>https://sourceforge.net/p/apexlib/feature-requests/95/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi Patrick,&lt;/p&gt;
&lt;p&gt;I found that in bigger databases there might exist more than one temporary tablespace or maybe the temporary tablespace is not named TEMP. I would recommend to allow a selection for the temporary tablespace when creating the user for APEXLIB. This requires changes on the file "ApexLib_create_apexlib_schema.sql"&lt;/p&gt;
&lt;p&gt;Just add the followings lines below the line 58 (DEFINE apexlib_tablespace = "&amp;amp;apexlib_tablespace"):&lt;br /&gt;
PROMPT .&lt;br /&gt;
PROMPT . Enter temporary tablespace for &amp;amp;apexlib_schema_name schema.&lt;br /&gt;
PROMPT . eg: TEMP or any other existing temporary tablespace.&lt;br /&gt;
PROMPT .&lt;br /&gt;
DEFINE apexlib_temp_tablespace = "&amp;amp;apexlib_temp_tablespace"&lt;/p&gt;
&lt;p&gt;Change the line 73 (old line 68) from "TEMPORARY TABLESPACE TEMP" into "TEMPORARY TABLESPACE &amp;amp;apexlib_temp_tablespace".&lt;/p&gt;
&lt;p&gt;Cheers,&lt;br /&gt;
Frank&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Frank Puechl</dc:creator><pubDate>Thu, 10 Jan 2008 08:41:50 -0000</pubDate><guid>https://sourceforge.net9e4654ec1ae71e0cd4e3c4deb36ad6d066218f7d</guid></item></channel></rss>