Total Lines Of Code: 5618 (2003-07-11 20:29)
Summary Period: 2003-04-10 to 2003-06-22
[root]/CS/plugins/mesh/bezier/object
Total Lines Of Code:
5618 (2003-07-11 20:29)
| Author | Changes | Lines of code | Lines per change |
|---|---|---|---|
| Totals | 55 (100.0%) | 5816 (100.0%) | 105.7 |
| jorrit | 42 (76.4%) | 5753 (98.9%) | 136.9 |
| res2002 | 3 (5.5%) | 27 (0.5%) | 9.0 |
| sunshine | 7 (12.7%) | 20 (0.3%) | 2.8 |
| tulebast | 3 (5.5%) | 16 (0.3%) | 5.3 |
Eric Sunshine removed the unused, obsolete, and deprecated top-level <name>
node from the .csplugin files.
0 lines of code changed in:
- Jorrit fixed the bezier mesh so that ForceRelight() with a new
light also works.
- Jorrit fixed the bezier mesh so that removing a pseudo-dynamic
light also works.
25 lines of code changed in:
- Jorrit added iLightingInfo->StaticLightDisconnect() so that a light
can be removed.
- Jorrit implemented iEngine->RemoveLight(). However since none
of the mesh objects correctly implement StaticLightDisconnect()
the function will not actually work even though it is fully
bugfree :-)
21 lines of code changed in:
- Jorrit added iEngine->RemoveLight() to remove a pseudo-dynamic
static lights and also automatically update all lightmaps. In case
of a static light this will not update the lightmaps unless
ForceRelight() is called later.
NOTE! Currently not implemented yet!
- Jorrit Extended iLightingInfo->InitializeDefault() with a new flag
telling the lighting sub-system if the lighting information should
be cleared or not. This allows correct handling when a single light
is added in case of genmesh and bezier curves.
20 lines of code changed in:
Eric Sunshine performed Phase Three of the elimination of the monolithic
scf.cfg:
-*- Eliminated the SCF information which was hardcoded in the .cpp files
of plugin modules, and which duplicated information in the external
.csplugin files.
-*- Plugin modules no longer maintain and export a monolithic class list.
Now, each factory implemented by the code is exported automatically.
-*- Added a new <implementation> child node to the <class> node in
.csplugin files. The value of this node is the name of the C++ class
which implements the SCF class. For instance, C++ class csVFS
implements crystalspace.kernel.vfs.
-*- Eliminated the following SCF macros which were related to exporting
SCF information from .cpp code and/or registering classes manually:
SCF_EXPORT_CLASS_TABLE
SCF_EXPORT_CLASS
SCF_EXPORT_CLASS_DEP
SCF_EXPORT_CLASS_TABLE_END
SCF_REGISTER_STATIC_CLASS_DEP
-*- Eliminated the following methods from iSCF:
RegisterStaticClass
RegisterClassList
-*- Plugin modules are now initialized/shutdown lazily as classes are
requested from them. The first time a class is requested, the plugin
is initialized. The plugin is shutdown after the last class instance
has been destroyed.
-*- Fixed bug in scf.h where SCF_PRINT_CALL_ADDRESS was not being enabled
for gcc 3.x.
-*- Fixed bug in win32.jam where GenerateExportDefs rule failed to ensure
that directory containing output file existed before creating file.
Also fixed bug where it failed to set up a dependency between the
input and output files.
-*- Still To-Do:
- Remove references to scf.cfg and scfreg from documentation. Also
document new .csplugin resources.
- Add platform-specific function to scan and locate plugins
automatically rather than using the ad-hoc approach inherited from
scanning for .scf files.
- Add platform-specific function to query a plugin's meta-information.
This should be used by SCF to do the raw extraction. Provide and
finalize API for higher-level clients to access meta-information.
- Augment static linking to work with the new facility. (Removal of
the hardcoded SCF information, has now broken static linking. It
worked until this time, even with all of the preceding changes.)
1 lines of code changed in:
Replaced NULL with 0.
66 lines of code changed in:
Eric Sunshine performed Phase One of the elimination of the monolithic
scf.cfg:
-*- Plugin modules are now self-describing. This information can be
queried at run-time without having to actually load the module.
-*- The plugin maintainer now manages the plugin's meta-information in an
external .csplugin file, rather than hard-coding the information into
the plugin's source code. The mechanism by which the meta-information
is bound to the plugin is platform-dependent. Presently, all
platforms simply lay down the meta-information in a plain text file
alongside the plugin itself; with the same basename and extension
.csplugin. This may change in the future. For example, on MacOS/X,
the meta-information will probably be encapsulated within the plugin's
bundle wrapper.
-*- Plugin meta-information is now maintained in XML format. Here is an
example:
<?xml version="1.0"?>
<!-- gl3d.csplugin -->
<plugin>
<name>gl3d</name>
<scf>
<classes>
<class>
<name>crystalspace.graphics3d.opengl</name>
<description>OpenGL 3D graphics driver</description>
<requires>
<class>crystalspace.font.server.</class>
</requires>
</class>
</classes>
</scf>
</plugin>
-*- Since meta-information is now extensible, maintainers can choose to
publish supplementary information about plugins (in addition to the
SCF information already published). For example, image loading
plugins could publish "image indendification" information which would
allow the image loading multiplexor to selectively request image
loading plugins on-demand, rather than requesting all plugins
unconditionally, even if they are not needed. Here is an example of a
possible meta-information table for the PNG loader:
<?xml version="1.0"?>
<!-- cspngimg.csplugin -->
<plugin>
<name>cspngimg</name>
<scf>...</scf>
<imageloader>
<imagetype>
<class>crystalspace.graphic.image.io.png</class>
<identify>
<mimetype>image/png</mimetype>
<extension>png</extension>
<extension>PNG</extension>
<scan length="4" bytes="\0x89PNG"/>
</identify>
</imagetype>
</imageloader>
</plugin>
In this example, the PNG loader meta-information tells the multiplexor
several different ways to identify a PNG image: by checking file
extension, if available; by checking MIME type, if available; by
checking for the magic-string "\0x89PNG" in the raw image data. If
the multiplexor identifies the image as PNG, only then will it
actually request the PNG loader.
-*- Added the --meta-file directive to msvcgen.pl to allow specification
of the meta-information file for a module. The value of this option
is interpolated into template files via the new %metafile% variable.
msvcgen.mak now utilizes this flag with the value of the new
INC.PROJECT makefile variable. Augmented the MSVC6 and MSVC7 plugin
template files (plugin.tpl) to make use of %metafile%.
-*- Changed the file extension for plugins on MacOS/X from .csplugin to
.csbundle to avoid conflict with new meta-information resource which
uses the extension .csplugin.
-*- Still To-Do:
- Augment SCF to utilize the new meta-information resources, and to
understand the new XML format. Presently, these resources are
ignored at run-time.
- Add platform-specific function to scan and locate plugins
automatically, rather than relying upon a monolithic registry such
as scf.cfg.
- Add platform-specific function to query a plugin's meta-information.
- Eliminate the monolithic scf.cfg.
- Augment static linking to work with the new facility.
- Eliminate the hard-coded SCF registration information in each
plugin's source code.
15 lines of code changed in:
Jorrit did various changes related to portal management:
- Moved iPortal definition from imesh/thing/portal.h to
iengine/portal.h. The reason is that portals are now an engine
concept and not only for things. The only portal implementation
is currently still in thing though.
- Added the ability to get the portal vertices from iPortal.
- Added iMeshObject->GetPortalCount() and iMeshObject->GetPortal().
- Also added default implementations of those to csMeshObject
(supporting no portals).
- At two places in the engine (GetNearbyObjects() and PlaceMesh())
this new function is used instead of first querying for
iThingState. This makes those functions a bit faster and is (in
theory) also more general (in the sense of being able to add
portals to any mesh object). However later on most functions
still query for iThingState so this promise of more generality
is not fulfilled yet.
2 lines of code changed in:
- Jorrit added iObjectModel->GetPolygonMeshShadows() and
SetPolygonMeshShadows(). This will be used by the shadow manager
in the new renderer. Implemented this in csObjectModel and also
fixed all mesh objects.
- Jorrit extended the loader so you can now specify <shadows/>
in a <polymesh> to indicate that the polymesh is for shadows (this
is in addition to <viscull/> and <colldet/>).
1 lines of code changed in:
- fixed the iPolygonMesh issue for the ball plugin.
- changed the Sprite3d and Genmesh objects to emit a notification
if iPolygonMesh is queried.
- changed the sequence operations working with sequences in the
'normal' and engine sequence manager to not store references on
sequences. That makes loops etc. possible without causing circular
references. Also updated the interface docs to reflect this change.
- fixed a few cases where iPolygonMesh was queried from a mesh
object to use iObjectModel->"GetPolygonMeshColldet().
- improved the wording on the paragraph about the iPolygonMesh
changes in the api mod documentation a bit.
2 lines of code changed in:
- cured the Bezier plugin from leaks caused by the
'embedded iPolygonMesh syndrome'.
25 lines of code changed in:
Eric Sunshine eliminated numerous compilation warnings throughout the
project.
1 lines of code changed in:
Eric Sunshine made the following changes:
-*- Modified configure.ac so that it emits a SRCDIR property to
config.mak. This value represents the --srcdir argument given to the
configure script (or "." if --srcdir is omitted). This points at the
directory containing the CS source code (which may differ from the
build directory, which is typically the current working directory).
-*- Modified makefiles and build scripts throughout the project so that
they respect $(SRCDIR). This allows the project to be built in a
directory other than the source directory, thus it is possible to
place the source directory on a readonly filesystem (such as a
CD-ROM), or to share a single NFS-mounted source directory among
different builds, where each build inhabits its own directory. For
example, if CS resides at /home/CS and you wish to build the project
in /home/build:
% cd /home/build
% ../CS/configure
% make -k all
% make install
(Note that the Jam-base build system already supports this build
paradigm.)
-*- Modified configure.ac so that it emits EXTENSIVE_MEMDEBUG to
config.mak since this variable is used by Makefile.in for the
`showconfig' target.
-*- Modified configure.ac so that it emits MONITOR_MAKEFILE_CACHE when the
value is either "yes" or "no", instead of emitting it only when the
value is "yes". This was necessary because CS/mk/cache.mak prints the
value of this variable as part of $(SYSMODIFIER).
3 lines of code changed in:
Fixed another compile error in bezier mesh.
1 lines of code changed in:
changed all instances of csFrustum::Intersect() to return csPtr<csFrustum> rather than csFrustum*;
csFrustumContext, csFrustumView, csBezierLightPatch, csLightPath now using smart pointers;
added csFrustumContext::SetNewShadow and ::SetNewFrustum methods;
csShadowBlock using csRefArray instead of deprecated csVector;
removed some unnecessary includes of csvector.h;
removed tabs from some files.
16 lines of code changed in:
- Added the following functions to iObjectModel:
- GetPolygonMeshBase: Get a polygon mesh representing the
basic geometry of the object.
- SetPolygonMeshColldet: Set a polygon mesh representing the
geometry of the object. This mesh is useful for collision
detection. This can be used to replace the default polygon mesh
returned by GetPolygonMeshColldet() with one that has less
detail or even to support polygon mesh for mesh objects that
otherwise don't support it. The object model will keep a
reference to the given polymesh.
- SetPolygonMeshViscull: Similar to SetPolygonMeshColldet() but
now for visibility culling (occluder writing).
- Added csObjectModel helper class to csgeom to help implement object
models for mesh object plugins.
- Fixed all mesh object implementations to use the new csObjectModel.
9 lines of code changed in:
- Added csColliderHelper::InitializeCollisionWrapper() which initializes
collision detection for a mesh and all children.
- Added iMeshObjectFactory->GetObjectModel(). This is an optional
method which factories can implement similar to the GetObjectModel()
in iMeshObject. If the factory contains the geometry for a model
then it is prefered that the factory has the object model. This
allows for better sharing of similar data between instances using
the same factory.
- Genmesh now implements GetObjectModel() in the factory.
- Spr3d now implements GetObjectModel() in the factory.
- InitializeCollisionWrapper() will now actually check if the parent
factory supports GetObjectModel() and if so it will share the
collider.
1 lines of code changed in:
Added Jamfiles for the new bezier mesh plugin.
10 lines of code changed in:
- Renamed PolyMeshHelper class in bezier mesh plugin so that it
doesn't conflict with PolyMeshHelper in thing plugin when doing
a static compile.
11 lines of code changed in:
Thing changes:
- Removed obsolete csThingBBox bounding box in csThing.
- Split bezier curves in seperate mesh object plugin (bezier
plugin).
- Greatly cleaned up the csThingStatic stuff and moved all static
stuff to that.
- Updated API modification document.
- Also updated various other parts in the documentation for these
changes.
- Fixed map2cs to export curves using the new bezier plugin.
- Changed the way thing factories and objects work. A thing factory
and a mesh object no longer are the same object. So first you
have to make a factory and then the object. This also allows
sharing of factories between objects.
- As a consequence of all these changes the lightmap format has
changed again.
- Doing a HardTransform() on a thing mesh object will automatically
cause the factory of that thing to be cloned so that other
things sharing that factory will not be transformed.
Doing a HardTransform() on a thing factory will have an
effect on all instances created from that.
- Used csBlockAllocator<T> for a lot of polygon objects in the
thing mesh plugin. This speeds up loading/unloading and also
improves memory usage.
- Merged csPolyTexLightMap into csPolyTexture. This improved
both speed, memory usage, and source code readability.
- Thing now uses ClipBSphere() instead of ClipBBox(). This is
faster.
5586 lines of code changed in:
Generated by StatCvs v0.2-dev