Thu Apr 9 14:44:58 CEST 2009 Tobias Rautenkranz <tobias@rautenkranz.ch>

* Minor corrections.

--- old-doc/introduction.docbook 2014-10-01 16:51:47.000000000 +0200

+++ new-doc/introduction.docbook 2014-10-01 16:51:47.000000000 +0200

@@ -26,6 +26,9 @@

Pentium M 1.7GHz. (Compilation ~20 seconds)</para></listitem>

<listitem><para>Needs to be recompiled when the Smoke library is updated.</para></listitem>

<listitem><para>Saving a core image is not supported.</para></listitem>

+ <listitem><para>Does not recover well from errors

+ <footnote><para>Thus you often need to restart the Lisp process

+ during interactive developement.</para></footnote>.</para></listitem>

</itemizedlist>

</section>

<section><title>Installation</title>

@@ -50,7 +53,11 @@

<section><title>Supported Platforms</title>

<para>

- SBCL on Linux x86 in works; CMUCL and CLisp currently do not.

+ <ulink url="http://www.sbcl.org">SBCL</ulink> on Linux x86 in works;

+ <ulink url="http://www.cons.org/cmucl/">CMUCL</ulink>

+ <footnote><para>Compiles and loads, still some unit test failtures</para></footnote>

+ and

+ <ulink url="http://clisp.cons.org/">CLISP</ulink> currently do not.

It should be possible to get it to work (with SBCL) on

other platforms. Contact me if you have any questions.

</para>

--- old-doc/kde.docbook 2014-10-01 16:51:47.000000000 +0200

+++ new-doc/kde.docbook 2014-10-01 16:51:47.000000000 +0200

@@ -4,7 +4,7 @@

<chapter id="kde">

<title>KDE</title>

<para>

-Besiedes the <package>:kde</package> package there

+Besides the <package>:kde</package> package there

is <package>:kde.tests</package> for the unit tests and

<package>:kde.examples</package> containing the examples.

</para>

@@ -54,7 +54,7 @@

</para>

</blockquote>

The sources can be found in the

- <filename><ulink url="../kde.examples/src/mandelbrot/">src/mandelbrot/</ulink></filename>

+ <filename><ulink url="http://tobias.rautenkranz.ch/darcsweb/darcsweb.cgi?r=cl-smoke/kde.examples;a=tree;f=/src/mandelbrot">src/mandelbrot/</ulink></filename>

directory of the <package>:kde.examples</package> package

</para>

--- old-doc/qt.docbook 2014-10-01 16:51:47.000000000 +0200

+++ new-doc/qt.docbook 2014-10-01 16:51:47.000000000 +0200

@@ -4,7 +4,7 @@

<chapter id="qt">

<title>Qt</title>

<para>

-Besieds the <package>:qt</package> there are these packages: with

+Besides the <package>:qt</package> there are these packages: with

<itemizedlist>

<listitem><para>

<package>:qt.uitools</package>

@@ -18,7 +18,7 @@

QtWebKit</ulink>

</para></listitem>

</itemizedlist>

-which provied bindings for their Qt module.

+which provide bindings for their Qt module.

Additionally there is the <package>:qt.tests</package> system, containing

the unit tests and <package>:qt.examples</package> for various examples.

</para>

--- old-doc/smoke.docbook 2014-10-01 16:51:47.000000000 +0200

+++ new-doc/smoke.docbook 2014-10-01 16:51:47.000000000 +0200

@@ -91,11 +91,22 @@

You should be able to use C++ Class instances like normal Lisp object.

</para>

<para>

-C++ classes are automaticly deleted when their lisp object gets garbage collected;

+C++ classes are automatically deleted when their lisp object gets garbage collected;

except when they (QObjects) have a parent and thus the parent is responsible for

their deletion. When a <classname>qt:object</classname> has a parent, a strong

reference is kept to prevent its garbage collection until the parent is deleted.

</para>

+<para>

+Not that an instance may depend on an other one.

+It is a bad idea to do something like this:

+<programlisting>

+(defvar *meta* (cxx:meta-object (make-instance 'qt:object)))

+</programlisting>

+<code>*meta*</code> references a <classname>qt:meta-class</classname>

+that can become invalid at any time, since the <classname>qt:object</classname> instance can

+be garbage collected, and then the <code>QMetaObject</code> instance is deleted along

+with the <code>QObject</code>.

+</para>

</section>

</chapter>