|
|
DataMuseum.dkPresents historical artifacts from the history of: DKUUG/EUUG Conference tapes |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about DKUUG/EUUG Conference tapes Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - downloadIndex: T i
Length: 3722 (0xe8a)
Types: TextFile
Names: »ideas«
└─⟦52210d11f⟧ Bits:30007239 EUUGD2: TeX 3 1992-12
└─⟦c319c2751⟧ »unix3.0/TeX3.0.tar.Z«
└─⟦036c765ac⟧
└─⟦this⟧ »TeX3.0/TeXcontrib/gnutex/ideas«
User-specify tic marks with
[xy]tics start incr
or
[xy]tics t1,t2,...,tn
(n may be 1 to, say, 20)
----
allow tic marks to be labelled with non-numerics
----
allow input data (and labels) to be an enumeration type (eg. {Male,Female})
----
do proper clipping of functions plotted without autoscaling on, when
values are finite but out-of-range
----
use EEPIC to draw plot lines
------
can I get a frame around the key?
-----
convert ints to longs where necessary throughout the program, as I
have in the LATEX unit, so 16-bit machines like the IBM PC can
properly use the large integers required for the latex terminal type.
-----
consider adding a "width" parameter to the impulses style to get bar graphs.
-rick
-----
I have a problem with \makebox in LaTeX picture mode. The LaTeX book
says that its reference point is the lower-left corner. I figure that
if I use dimensions (0,0) and the default "pos" (which is horiz and
vert centered), the object in my box would be centered on the point.
The following example does not center the second and third circles
correctly:
\setlength{\unitlength}{10pt}
\begin{picture}(50,50)
\put(15,20){\line(1,0){10}}
\put(20,15){\line(0,1){10}}
\put(20,20){\circle{5}} % Centers fine
\put(20,20){\makebox(0,0){\circle{3}}} % Too high
\put(20,20){\makebox(0,0){\circle{.3}}} % Too far left
\end{picture}
This is LATEX VERSION 2.09 <26 Apr 1988>
-----
From: Paul E. McKenney <mckenney@spam.istc.sri.com>
Use dashed and dotted lines to implement line styles
(e.g., plot the first function with solid lines, the
second with dashed lines, the third with dotted lines
the fourth with alternating dot-dash, the fifth with
alternating double-dot-dash, ad nauseum). It should
be possible to implement a general-purpose routine
to do this for any device, given (as arguments)
a pointer to the line-drawing function for that device
(dots could be implemented as very short dashes),
the endpoints of the line, and where in the cycle
the routine should start (so that two adjacent lines
would join smoothly).
-----
From: Paul E. McKenney <mckenney@spam.istc.sri.com>
(For Imagen driver)
Implement key. In my case there is little point in doing
this until the dashed and dotted lines are done.
------
From: Paul E. McKenney <mckenney@spam.istc.sri.com>
Some way of controlling fonts to be used in titles, labels,
etc. This is obviously not a problem in LaTeX, since you
can imbed ``\Huge'' (or whatever) in your strings.
Right now, you get the courier font that comes with the printer,
with the sizes compiled in to the program.
-----
From: Paul E. McKenney <mckenney@spam.istc.sri.com>
``replot'' and other goodies from later versions of gnuplot
----
From: Paul E. McKenney <mckenney@spam.istc.sri.com>
Allow labels to be specified in the datafile as they
are in graph(1). Also have some way of mimicing the
action of the ``-b'' command line argument to graph(1).
In case you don't have a man page handy, if you put a
string (quoted if multi-word) following a datapoint in
graph(1), it will use that string to label that datapoint.
gnutex would also want to implement an optional ``pos''
argument.... The ``-b'' flag says to break the line
after any label. The people here use this to allow
storing several curves on a single file, with the last point
of each curve labelled with an empty label. Thus, they might
have:
1 1
2 4
3 9
....
9 81
10 100 " "
1 1
2 8
3 27
....
9 729
10 1000 " "
1 1
...
in a single file, wanting to get several curves on the plot.
People writing simulation programs seem very fond of this
sort of thing.