pspp-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Pspp-cvs] pspp TODO


From: Ben Pfaff
Subject: [Pspp-cvs] pspp TODO
Date: Sun, 16 Apr 2006 01:11:45 +0000

CVSROOT:        /cvsroot/pspp
Module name:    pspp
Branch:         
Changes by:     Ben Pfaff <address@hidden>      06/04/16 01:11:44

Modified files:
        .              : TODO 

Log message:
        Update TODO.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/pspp/pspp/TODO.diff?tr1=1.33&tr2=1.34&r1=text&r2=text

Patches:
Index: pspp/TODO
diff -u pspp/TODO:1.33 pspp/TODO:1.34
--- pspp/TODO:1.33      Sat Mar  4 12:38:35 2006
+++ pspp/TODO   Sun Apr 16 01:11:44 2006
@@ -1,4 +1,4 @@
-Time-stamp: <2006-02-17 22:06:31 blp>
+Time-stamp: <2006-04-15 18:11:46 blp>
 
 Get rid of need for GNU diff in `make check'.
 
@@ -27,9 +27,6 @@
 
 In debug mode hash table code should verify that collisions are reasonably low.
 
-Use AFM files instead of Groff font files, and include AFMs for our default
-fonts with the distribution.
-
 Storage of value labels on disk is inefficient.  Invent new data structure.
 
 Add an output flag which would cause a page break if a table segment could fit
@@ -39,35 +36,9 @@
 
 Cell footnotes.
 
-PostScript driver should emit thin lines, then thick lines, to optimize time
-and space.
-
 Should be able to bottom-justify cells.  It'll be expensive, though, by
 requiring an extra metrics call.
 
-Perhaps instead of the current lines we should define the following line types:
-null, thin, thick, double.  It might look pretty classy.
-
-Perhaps thick table borders that are cut off by a page break should decay to
-thin borders.  (i.e., on a thick bordered table that's longer than one page,
-but narrow, the bottom border would be thin on the first page, and the top and
-bottom borders on middle pages.)
-
-Support multi-line titles on tables. (For the first page only, presumably.)
-
-In addition to searching the source directory, we should search the current
-directory (for data files).  (Yuck!)
-
-Fix line-too-long problems in PostScript code, instead of covering them up.
-setlinecap is *not* a proper solution.
-
-Fix som_columns().
-
-Improve interactivity of output by allowing a `commit' function for a page.
-This will also allow for infinite-length pages.
-
-Implement thin single lines, should be pretty easy now.
-
 SELECT IF should be moved before other transformations whenever possible.  It
 should only be impossible when one of the variables referred to in SELECT IF is
 created or modified by a previous transformation.
@@ -105,12 +76,6 @@
 for instance through a wide PRINT request--try time-date.stat with a narrow
 ascii page or with the postscript driver on letter size paper.)
 
-NULs in input files break the products we're replacing: although it will input
-them properly and display them properly as AHEX format, it truncates them in A
-format.  Also, string-manipulation functions such as CONCAT truncate their
-results after the first NUL.  This should simplify the result of PSPP design.
-Perhaps those ugly a_string, b_string, ..., can all be eliminated.
-
 From Moshe Braner <address@hidden>: An idea regarding MATCH
 FILES, again getting BEYOND the state of SPSS: it always bothered me that if I
 have a large data file and I want to match it to a small lookup table, via




reply via email to

[Prev in Thread] Current Thread [Next in Thread]