$Id$
-----------------------------------------------------------------

g4mc/geometry:
==============
  19.12.00:
    TG4GeometryServices: a new class separated from
       TG4GeometryManager; it provides service methods for accessing
       to Geant4 geometry, namely using AliMC volumes and materials
       identifiers.

  9.10.00:
     XML implementation:
     - solids are stores in XML with names of logical volumes
       (as solids names are not unique)
     - the length parameters in XML are multiplied by 2.
     - element poxXYZRot -> transform 
     TG4XMLGeometryGenerator:
       added fVolumeNames - set for remembering logical
       volumes already processed; this ensure that each lv
       is processed only once.          

  28.7.00: new classes:
     TG4XMLGeometryGenerator: class for generation of geometry data 
        files in XML; the XML format is independent from G4 geometry
        object model. The interface TG4VXMLConvertor is used for
	writing XML elements; more than one implementation of XML
	convertor can be used -> more than one dtd geometry descriptions
	can be supported.
     TG4VXMLConvertor: interface for XML convertor that provides
        methods interfaces for converting G4 basic geometry objects
	to XML description
     TG4XMLConvertor: concrete implementation of XML convertor
        generating XML elements according to AGDD.dtd
        (ATLAS Generic Detector Description)
	Only subset of G4 solids are implemented; 
	Not yet implemented: 
	materials, rotation matrices, replicated volumes.

  6.6.00: 
     TG4NameMap moved to g4mc/global;
        as it is used also in TG4PhysicsManager
	for mapping names of particles between
	G4 and TDatabasePDG

  13.4.00:
     TG4NameMap: new class;
        defines a map for associated names;
	it is used in TG4Geometry manager for the map of
	G3 volume names with the modules name; 
	
  28.3.00:
     New subcategory:
     Classes: TG4GeometryManager, TG4GeometryOutputManager,
              TG4VSensitiveDetector, TG4ElementTable