====== Project registry (GS) ======

{{page>01_user_documentation:06_graph:03_graphs:10_registry&noheader}}

When serialized, the registry is stored in a XML file. With the extension .gs.

======  ======


It's minimal content is: 

<code xml>
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<project xmlns="http://grogra.de/registry" graph="graph.xml"/>
</code>

The first line describes the xml format. Then the second line is the main tag of the file: ''<project/>''. All the content of the **project registry** has to be inserted under this tag. The tag also defines the name of the **graph** file it describes. 

===== Example =====


An actual registry file of a project looks like:

<code xml>
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<project xmlns="http://grogra.de/registry" graph="graph.xml">
<!-- The list of required groimp plugin for running the project -->
 <import plugin="de.grogra.imp" version="2.1.5"/>
 <import plugin="de.grogra.pf" version="2.1.5"/>

<!-- All the registry items required to be loaded --> 
<registry>
<!-- List of the projects objects (Here we only have one file, but shaders, images, ... would be listed here as well) -->
 <ref name="project">
   <ref name="objects">
    <ref name="files">
     <de.grogra.pf.ui.registry.SourceFile mimeType="text/x-grogra-rgg" name="Model.rgg" systemId="pfs:Model.rgg"/>
     </ref>
    </ref>
   </ref>
   
   <!-- A list of the layout used to reload the project in the same workbench layout --> 
   <ref name="workbench">
   <ref name="state">
    <de.grogra.pf.ui.registry.Layout name="layout">
    ...
    </de.grogra.pf.ui.registry.Layout>
   </ref>
  </ref>
   
</registry>

</project
</code>