Penguin
Recent Changes
Annotated edit history of t3d(1) version 1, including all changes. View license author blame.
Rev Author # Line
1 perry 1 t3d
2 !!!t3d
3 NAME
4 SYNOPSIS
5 DESCRIPTION
6 OPTIONS
7 AUTHOR
8 ACKNOWLEDGEMENT
9 COPYING
10 DISCLAIMER
11 KNOWN BUGS
12 ----
13 !!NAME
14
15
16 t3d - clock using flying balls to display the time
17 !!SYNOPSIS
18
19
20 t3d [[ ''options'' ]...
21 !!DESCRIPTION
22
23
24 Time 3D is a clock. It uses flying balls to display the
25 time. This balls move and wobble around to give you the
26 impression your graphic workstation with its many XStones is
27 doing something.
28
29
30 t3d uses mouse and keyboard to let you fly through the
31 balls. Hit __S__ to speed up, __A__ to slow down,
32 __Z__ to zoom in and __X__ to zoom out. Use the
33 __left mouse button__ to rotate to the left and the
34 __right mouse button__ to rotate the view to the right.
35 Use the __middle mouse button__ to change the optical
36 axis and the moving direction. __0__ (zero) will stop
37 you. __Q__ quits.
38 !!OPTIONS
39
40
41 __-move__ ''factor''
42
43
44 Modifies the direction move of t3d. The clock looks 30
45 degrees* ''factor'' to the left and to the right
46 periodically.
47
48
49 __-wobble__ ''factor''
50
51
52 Modifies the wobbling (sounds nice :-) of t3d by multiplying
53 the default deformation of the clock with
54 ''factor.''
55
56
57 __-minutes__
58
59
60 Shows one small ball for every minute, instead of one for
61 every 2.5 minutes.
62
63
64 __-mag__ ''factor''
65
66
67 Changes the magnification of t3d. By default, t3d draws a
68 200x200 image. A .I factor of 2 means, it will use a 400x400
69 image.
70
71
72 __-cycle__ ''period''
73
74
75 Sets the moving cycle to ''period'' seconds. By default,
76 this value is 10 seconds.
77
78
79 __-wait__ ''microsec''
80
81
82 Inserts a wait after drawing one view of the clock. By
83 default, t3d waits 40 ms after each drawing. This helps you
84 to keep the performance loss small.
85
86
87 __-fast__ ''precalc_radius''
88
89
90 t3d uses bitmap copy to draw precalculated balls. You can
91 specify the radius in pixels up to which t3d should
92 precalculate balls. t3d will set a useful range by itself
93 using the magnification when it is started.
94
95
96 __-colcycle__
97
98
99 Draws cyclic the color scale used for the balls in the
100 background instead of the normal black.
101
102
103 __-rgb__ ''red green blue''
104
105
106 Selects the color in RGB color space of the lightning spot
107 on the balls. All the other colors used for balls or
108 __-colcycle__ are less intensive colors of the same hue
109 and saturation. All values in range of 0 to 1.
110
111
112 __-hsv__ ''hue saturation value''
113
114
115 Selects the color in HSV color space. ''hue'' is in
116 degrees from 0 to 360, all other values in range from 0 to
117 1. It gives nice but rather unpredictable results, if you
118 use a saturation of e.g. 2. Try it at your own
119 risk.
120
121
122 __-hsvcycle__ ''speed''
123
124
125 Rotates the hue axis every 10 seconds*
126 ''speed.''
127
128
129 __-help__
130
131
132 Prints a short usage message.
133 !!AUTHOR
134
135
136 Bernd Paysan
137
138
139 Email: bernd.paysan@gmx.de
140
141
142 Hacked on by jwz@jwz.org for xscreensaver.
143 !!ACKNOWLEDGEMENT
144
145
146 Acknowledgement to Georg Acher, who wrote the initial
147 program displaying balls.
148 !!COPYING
149
150
151 Copy, modify, and distribute T3D either under GPL version 2
152 or newer, or under the standard MIT/X license
153 notice.
154 !!DISCLAIMER
155
156
157 T3D is not related to T3D(tm), the massive parallel
158 Alpha--based supercomputer from Cray Research. T3D's name
159 was invented in 1991, years before the project at Cray
160 Research started. There is no relation from T3D to Cray's
161 T3D, even the balls surrounding T3D on some posters weren't
162 an inspiration for T3D. I don't know anything about the
163 other way round.
164
165
166 The programming style of T3D isn't intented as example of
167 good style, but as example of how a fast prototyped demo may
168 look like. T3D wasn't created to be useful, it was created
169 to be nice.
170 !!KNOWN BUGS
171
172
173 There are no known bugs in T3D. Maybe there are bugs in X.
174 Slight changes in the T3D sources are known to show these
175 bugs, e.g. if you remove the (int) casting at the XFillArc
176 x,y,w,h-coordinates...
177 ----
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.