1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
|
===========================================================================
NEWS for 3Dwm -- http://www.3dwm.org
Copyright (c) 2000, 2001 Niklas Elmqvist. All rights reserved.
File created 2000-09-20 by Niklas Elmqvist <elm@3dwm.org>.
File History:
2001-08-28 Changes for 3Dwm 0.3.1 added.
2001-08-22 Changes for 3Dwm 0.3.0 added.
2001-06-10 Changes for 3Dwm 0.2.4 added.
2001-05-06 Changes for 3Dwm 0.2.3 added.
2000-11-03 Changes for 3Dwm 0.2.2 added.
2000-09-20 File created for 3Dwm version 0.2.1.
===========================================================================
3Dwm 0.3.1 -- August 28th, 2001.
--------------------------------
Changes since 3Dwm 0.3.0:
o Solid modeling code completed. All children of an appearance
container will be properly invalidated if the appearance
characteristics are changed.
o VNC interaction improved so that the VNC mouse cursor moves in
sync with the real pointer, and both button presses and releases
(*both* for keys and for mouse buttons) are supported instead of
triggering an atomic "press and release". This improvement
enables dragging and various key combinations.
o VNC desktops no longer need to be a multiple of two to be usable
inside 3Dwm (this limitation was due to the fact that OpenGL
demands textures to be 2-multiples). This means that it is
finally possible to run Windows and MacOS VNC desktops inside
3Dwm without having to hack the code to grab a small part of the
screen. Unfortunately, desktop scaling has yet to be properly
implemented, so interacting with a desktop that is *not* a
multiple of two is difficult.
o Documentation translation updates for French and Spanish done by
Jean-Franois Quenault (jfquenault@wanadoo.fr) and Victor Ferrer
(victorf2@jazzfree.com), respectively.
o Various bugfixes.
3Dwm 0.3.0 -- August 22nd, 2001.
--------------------------------
Changes since 3Dwm 0.2.4:
o Solid modeling functionality added to the display server. Using
solid modeling, it is possible to use boolean set operators to
combine geometrical entities in various ways. CSG (constructive
solid geometry) trees can be built and evaluated in real-time and
with excellent performance. It is even possible to animate them.
o VNC support is now complete. You can seamlessly now run your
normal X11 applications inside 3Dwm! A special desktop interface
has been created so that you can connect to a VNC desktop and
handle *both* input to the desktop as well as the graphical
output. Rudimentary focus management has been implemented.
o 3D primitives and factory kit created. This makes it easy to
effortlessly create 3D primitives such as spheres, cuboids,
cones, cylinders and planes in 3Dwm clients.
o "tdwm-clock", the first real 3Dwm application, has been added to
the distribution. The clock application makes use of the new
solid modeling functionality to display an analog clock in full
3D.
o Partial C++ SAX (Simple API for XML) implementation added to
Celsius. Uses expat (http://expat.sourceforge.net) as a backend
and conforms mostly to David Megginson's original Java SAX that
can be found on http://www.megginson.com/SAX/.
o Configuration file support implemented in the display server.
Configuration files are written in XML (and are parsed by the SAX
parser) and contain a number of run-time options to configure the
display server.
o Event mapping language implemented. This is handled by the Zorn
subsystem that contains an interpreter for a simple prepositional
logic language. Input events are now mapped to system commands in
the new event manager using the Zorn interpreter.
o Basic mapping files for mouse and keyboard as well as a 3DOF
headtracker has been implemented (headtracker needs the Itrax
driver compiled in with the source).
o Support for the Intersense InterTrax 2 headtracker implemented.
You need the itrax kernel module version 0.2+ that can be
downloaded from http://www.mip.informatik.uni-kiel.de/~evers/.
o Pick traversal implemented. The pick traversal is the basic
mechanism for input event propagation in the scene graph.
o Ray picking implemented. Used for letting the user click on the
2D window using his mouse and then sending a ray from the screen
through the scene graph to detect any intersections with graph
nodes. By computing the intersection point with the ray, this
mechanism can be used to communicate with VNC sessions.
o Axis-aligned bounding boxes for all scene graph nodes added. In
the future, high-resolution bounding volumes will be supported as
well.
o Enhanced the 3Dwm texture mapping facilities, added a texture
coordinate generator, refactored all calls related to texturing
and put them in a the new TextureKit.
o Various utilities classes related to operating system services
and file path support have been added to Celsius.
o Logging has been made more verbose. This should make it much
easier to troubleshoot the display server, especially on boot-up.
o Camera navigation has been improved and now uses a "standardized"
combination of mouse and keyboard for easy manipulation (see the
INSTALL file for more information).
o Quaternions for 3D rotations have been added to Celsius and are
used when animating the camera in the server view.
o French translations of the README and INSTALL files contributed
by Jean-Francois Quenault <jfquenault@wanadoo.fr>.
o C++ conformance bugfixes. 3Dwm should now compile cleanly under
gcc 3.0. Unfortunately, there are some serious issues with using
omniORB and gcc 3.0, so avoid 3.0 for the time being.
o Minor fix to the build system to install the generated Nobel
headers correctly. This means that 'make install' should now do
the right thing, making it substantially easier to create
independent 3Dwm applications.
o Various additional bugfixes.
3Dwm 0.2.4 -- June 10th, 2001.
------------------------------
Changes since 3Dwm 0.2.3:
o New build system implemented. The new build system is based on
GNU Automake and GNU Libtool and has improved support for
Autoconf scripts. You can also choose to build 3Dwm in separate
directory. Added some m4 macros to detect different software
components in the configure script. In general, the configuration
and build process should be much smoother and more portable now
than before.
o Logging service implemented. This comes in the shape of a general
logging class in Celsius that is utilized in Polhem for emitting
log messages all through the server. Expect this feature to be
improved and made use of to a much larger extent in future
releases.
o Polhem is now a shared library and there is a new server/
directory off the main directory that contains the server
executable. This executable is the display server itself and
links to all the different libs in the 3Dwm distribution.
o Updated build instructions in README and INSTALL. Added the
AUTHORS file and renamed LICENSE to COPYING according to the GNU
coding standards.
o Italian README file added to the doc/ directory, courtesy of
Marizio Boriani <baux@debian.org>.
o Added time functionality to the Celsius API.
o Various bugfixes.
3Dwm 0.2.3 -- May 6th, 2001.
----------------------------
Changes since 3Dwm 0.2.2:
o Platform abstraction layer implemented. This is an important
addition to the server since it now allows the server to be
easily retargetted to just about any kind of hardware platform,
ranging from wearable computer to CAVE. All the SDL-specific
code has now been moved to a specific SDLPlatform, and the road
is open for the development of additional platforms. The next
step is to put all platforms in shared libs to allow for them to
be selected at server boot.
o 3Dwm can now run in the framebuffer console (only tested on
Linux). This is done using SDL and OSMesa (which means no
3D-acceleration, but that's life), and is contained in a special
SDLfbconPlatform.
o Implemented a new view model where the user's view is decoupled
from the actual scene graph to allow for multiple views as well
as applications indicating to the server their preferable
viewpoint for viewing.
o Added the support/ directory to the source distribution. This is
where client-side support libraries for different programming
languages will be added. Currently, there is support for C++
(Nobel++), and Python (Nobelpy) and Java (jNobel) is on the way.
o Moved image loading from the server-side to the client-side. It
is currently part of the Nobel++ library instead of the server.
The Texture IDL was refactored to accept raw image data instead
of PNG data, like it did before.
o Server-keepalive pinging implemented. The server will now ping
all connected clients in order to be able to detect crashed or
terminated clients and free up any used resources.
o Minor architectural change, the server now uses a backplane for
all communication between components.
o Introductory article on 3Dwm (3Dwm: Next-Generation Graphical
User Interfaces on UNIX Platforms) added to the distribution
(see the doc/articles directory).
o Refactoring of the thread API in Celsius.
o Source code cleanup to make 3Dwm slightly more conformant to the
C++ standard.
o Russian INSTALL and README files added to the doc/ directory,
thanks to Serguei Boldyrev <s_boldyrev@mail.ru>.
o Various bugfixes.
3Dwm 0.2.2 -- November 3rd, 2000.
---------------------------------
Changes since 3Dwm 0.2.1:
o VNC (Virtual Network Computing) support has been added. The 3Dwm
server can now act as a VNC client and receive framebuffer
updates from a remote VNC server (running _any_ VNC-supported
OS, including Windows, X11, and MacOS) and output them to a
texture (try the 'vncclient'). Client input has been
implemented, but not fully activated in the 3Dwm server.
o Full 3D scene graph.
o Big texture support (splits textures into several smaller
textures on 3D-hardware with the 256x256 texture limitation,
notably 3dfx Voodoo 3). Currently deactivated.
o Material support.
o Client connection framework, complete with kit resolution (no
garbage collection of clients, however).
o 'geoclient' and 'texclient' updated.
o Automated testsuite based on Extreme Programming unit tests and
built using CppUnit.
3Dwm 0.2.1 -- September 20th, 2000.
-----------------------------------
Changes since 3Dwm 0.2:
o Distributed texture support has been added (courtesy of Steve
Houston, a new member of the 3Dwm development team). PNG files
can be loaded (using libpng <http://www.libpng.org>) by the
clients and sent to the server for use as textures for objects
in the scene graph (like geometries). A simple texclient has
been added to test this functionality.
o Improved documentation, especially the installation
instructions.
o Full scene graph functionality has been defined, but not fully
implemented.
o The Renderer has been refactored to use the Bridge design
pattern, allowing for the interface and the implementation to
vary interchangably.
|
