We have until mid January 2004 to make the necessary code changes that create a more "cvs friendly" file by moving some of the options to the .kdevses file.
\bug bugs in <a href="http://bugs.kde.org/buglist.cgi?product=tdevelop&component=autoproject&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&order=Bug+Number"> autoproject component at Bugzilla database</a>
\bug Lower Automake Manager view does not update it's view when adding a subproject (and targets, etc to the new subproject)
\bug If removing the Active Target, update the .tdevelop file, too!
\bug If removing the Active Target, update the .kdevelop file, too!
@ -96,7 +96,7 @@ There are quite a lot of default configuration subdirectories in <filename class
<listitem id="app-files-default-appwizard">
<para><filename class="directory">kdevappwizard/</filename> — contains files used by the &appwizard; part:</para>
<itemizedlist>
<listitem><para><filename class="directory">importfiles/</filename> — contains <filename>.tdevelop</filename> project files which control the initialization of a new project.</para></listitem>
<listitem><para><filename class="directory">importfiles/</filename> — contains <filename>.kdevelop</filename> project files which control the initialization of a new project.</para></listitem>
<listitem><para><filename class="directory">imports/</filename> — contains templates to set up project specific <filename>.desktop</filename> files.</para></listitem>
<listitem><para><filename class="directory">template-common/</filename> — contains various files commonly included in the project source directories.</para></listitem>
<listitem><para><filename class="directory">templates/</filename> — contains configuration files which describe the information to be included in a given project source directory.</para></listitem>
@ -399,10 +399,10 @@ There are two groups of &tdevelop; configuration files in the <filename class="d
<title>Project Dependent Configuration</title>
<para>
Most project dependend configuration is kept in the <filename><project-name>.tdevelop</filename> and <filename><project-name>.kdevses</filename> &tdevelop; project configuration files rather than in separate files as the other, more global, configuration settings. In short, those files are meant for:
Most project dependend configuration is kept in the <filename><project-name>.kdevelop</filename> and <filename><project-name>.kdevses</filename> &tdevelop; project configuration files rather than in separate files as the other, more global, configuration settings. In short, those files are meant for:
</para>
<simplelist>
<member><filename><project-name>.tdevelop</filename> — global project configuration information.</member>
<member><filename><project-name>.kdevelop</filename> — global project configuration information.</member>
<member><filename><project-name>.kdevses</filename> — configuration information needed to restore the specific behaviours of the running session.</member>
</simplelist>
<para>
@ -412,7 +412,7 @@ Both are &XML; coded files. They can be viewed and (cautiously) altered using an
<sect2>
<title>Persistent Code Store Files</title>
<para>There is a third project dependend configuration file, the <filename><project-name>.tdevelop.pcs</filename> Persistant Code Store. This is a binary coded file holding an internal parser cache for the most part in order to speed up the loading sequence of the project. Additionally, this Persistant Code Store keeps information use by the <guilabel>Code Completion</guilabel> facility of &tdevelop;.
<para>There is a third project dependend configuration file, the <filename><project-name>.kdevelop.pcs</filename> Persistant Code Store. This is a binary coded file holding an internal parser cache for the most part in order to speed up the loading sequence of the project. Additionally, this Persistant Code Store keeps information use by the <guilabel>Code Completion</guilabel> facility of &tdevelop;.
