source: trunk/third/xscreensaver/hacks/t3d.man @ 12808

Revision 12808, 3.6 KB checked in by danw, 26 years ago (diff)
This commit was generated by cvs2svn to compensate for changes in r12807, which included commits to RCS files with non-trunk default branches.
Line 
1.TH t3d 1 "Version 1.1" "Time 3D"
2.SH NAME
3t3d \- clock using flying balls to display the time
4.SH SYNOPSIS
5t3d [ \f2 options\f1 ]...
6.SH DESCRIPTION
7.PP
8Time 3D is a clock. It uses flying balls to display the time. This
9balls move and wobble around to give you the impression your
10graphic workstation with its many XStones is doing something.
11.PP
12t3d uses mouse and keyboard to let you fly through the balls. Hit
13.B S
14to speed up,
15.B A
16to slow down,
17.B Z
18to zoom in and
19.B X
20to zoom out.
21Use the
22.B left mouse button
23to rotate to the left and the
24.B right mouse button
25to rotate the view to the right. Use the
26.B middle mouse button
27to change the optical axis and the moving direction.
28.B 0
29(zero) will stop you.
30.B Q
31quits.
32.PP
33.SH OPTIONS
34.TP
35.BI "-move " "factor"
36Modifies the direction move of t3d. The clock looks 30 degrees*
37.I factor
38to the left and to the right periodically.
39.TP
40.BI "-wobble " "factor"
41Modifies the wobbling (sounds nice :-) of t3d by multiplying the
42default deformation of the clock with
43.I factor.
44.TP
45.B -minutes
46Shows one small ball for every minute, instead of one for every 2.5 minutes.
47.TP
48.BI "-mag " "factor"
49Changes the magnification of t3d. By default, t3d draws a 200x200 image.
50A .I factor
51of 2 means, it will use a 400x400 image.
52.TP
53.BI "-cycle " "period"
54Sets the moving cycle to
55.I period
56seconds. By default, this value is 10 seconds.
57.TP
58.BI "-wait " "microsec"
59Inserts a wait after drawing one view of the clock. By default, t3d waits
6040 ms after each drawing. This helps you to keep the performance loss
61small.
62.TP
63.BI "-fast " "precalc_radius"
64t3d uses bitmap copy to draw precalculated balls. You can specify the radius
65in pixels up to which t3d should precalculate balls. t3d will set a useful
66range by itself using the magnification when it is started.
67.TP
68.B -colcycle
69Draws cyclic the color scale used for the balls in the background instead
70of the normal black.
71.TP
72.BI "-rgb " "red green blue"
73Selects the color in RGB color space of the lightning spot on the balls.
74All the other colors used for balls or
75.B -colcycle
76are less intensive colors of the same hue and saturation. All values
77in range of 0 to 1.
78.TP
79.BI "-hsv " "hue saturation value"
80Selects the color in HSV color space.
81.I hue
82is in degrees from 0 to 360, all other values in range from 0 to 1. It gives
83nice but rather unpredictable results, if you use a saturation of e.g. 2.
84Try it at your own risk.
85.TP
86.BI "-hsvcycle " "speed"
87Rotates the hue axis every 10 seconds*
88.I speed.
89.TP
90.B -help
91Prints a short usage message.
92
93.PP
94.SH AUTHOR
95.PP
96Bernd Paysan
97
98Email: bernd.paysan@gmx.de
99
100Hacked on by jwz@jwz.org for xscreensaver.
101
102.SH ACKNOWLEDGEMENT
103.PP
104Acknowledgement to Georg Acher, who wrote the initial program displaying
105balls.
106
107.SH COPYING
108.PP
109Copy, modify, and distribute T3D either under GPL version 2 or newer, or
110under the standard MIT/X license notice.
111
112.SH DISCLAIMER
113.PP
114T3D is not related to T3D(tm), the massive parallel Alpha--based
115supercomputer from Cray Research. T3D's name was invented in 1991,
116years before the project at Cray Research started. There is no
117relation from T3D to Cray's T3D, even the balls surrounding T3D on
118some posters weren't an inspiration for T3D. I don't know anything
119about the other way round.
120
121The programming style of T3D isn't intented as example of good style,
122but as example of how a fast prototyped demo may look like. T3D wasn't
123created to be useful, it was created to be nice.
124
125.SH KNOWN BUGS
126.PP
127There are no known bugs in T3D. Maybe there are bugs in X. Slight
128changes in the T3D sources are known to show these bugs, e.g. if
129you remove the (int) casting at the XFillArc x,y,w,h-coordinates...
Note: See TracBrowser for help on using the repository browser.