Remove obsolete documentation texts.

Those are so insanely obsolete, it hurts our eyes.

git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@21568 57a11ea4-9604-0410-9ed3-97b8803252fd
This commit is contained in:
Christian Stimming
2011-11-14 19:43:20 +00:00
parent 0992192e39
commit 411261ae17
10 changed files with 10 additions and 480 deletions
+1 -3
View File
@@ -22,7 +22,6 @@ tips_DATA = tip_of_the_day.list
EXTRA_DIST = \
${doc_DATA} \
misc-notes.txt \
README.build-system \
README.HBCI \
README.OFX \
@@ -30,10 +29,9 @@ EXTRA_DIST = \
TRANSLATION_HOWTO \
build-aix.txt \
build-solaris.txt \
generic_objects.txt \
gnome-hackers.txt \
gnucash.1.in \
gtkrc-2.0.gnucash \
misc-notes.txt \
tip_of_the_day.list.in
## We borrow guile's convention and use @-...-@ as the substitution
-14
View File
@@ -1,14 +0,0 @@
This document attempts to summerize discussion on gnucash-devel about
generic objects in the engine. This discussion took place between
2001-11-17 and ... (in case you want to find the archives) and the
subject was "GncBusiness v. GNCSession".
One part of the problem, explained:
> > That is the whole point. The problem is that there is no generic
> > hooks into the GNCSession to store the GNCEntityTable for each
> > object-type; there is no hook in the GNCBook to store the object
> > tables (list of existing Customers, Vendors, Invoices, etc); there
> > is no hook in the Backend structure to load or save these objects;
> > there is no hook in the Query structure to search these objects.
-34
View File
@@ -1,34 +0,0 @@
-*-text-*-
This file is intended to contain information for those interested in
working on the GNOME bits of GnuCash.
Memory Management (care with reference counting):
-------------------------------------------------
I was unsure about when you're supposed to _unref widgets, etc., and
getting this right is critical to avoiding memory leaks on the one
hand and dangling pointers on the other. So I asked on the gtk list,
and here was the result:
On 16 Aug 1999, Rob Browning wrote:
>
> I've been poking around the gtk web site and in the docs for
> information on when you're supposed to call gtk_widget_unref. I want
> to make sure I'm handling this right so I don't introduce memory
> leaks, but so far I haven't found anything describing the rules.
> Actually I'd like to know what the guidelines are for all the *_unref
> functions...
>
Read gtk+/docs/refcounting.txt (or something like that).
Also I think some babble about object finalization at
http://pobox.com/~hp/gnome-app-devel.html (follow link to sample
chapters) might be helpful.
Basically you have to unref a widget you never use, but if you put it
in a container the container "assumes" the initial refcount of 1 and
the widget will be deleted along with the container.
Havoc