Since it is really difficult for a newbie to understand ideas behind the configuration of FUUT, i believe we need a document describing the purpose of each configuration file.

_(Ghica) Here goes..._
There are three kinds of configurations:<br/>
	1 *start-up* - Needed is a list of plugins to load, this list is supplied in a *.ini* file, and a *.properties* file.<br/>
	2 *code-generation* - Needed is a list of templates to use for code generation. If you use the Fuut-je built-in template language, a *cglist* is needed, if you use Velocity templates, a *vlist* is needed. Each time the code generation action is invoked, you are given the possibility to choose a list, and the list is read. This means that you can create lists, or change them without stopping/starting Fuut-je. Very handy when developing templates. <br/>
	3 *batch-processing* - Here a list of operations to be performed must be provided in an *.ftbatch* file.<br/>
-- Main.GhicaVanEmdeBoas - 06 Jul 2004	

Extensions of configuration files stand for: <br>
*cglist* - code generation list <br>
*vlist* - velocity list 


While surfing through the FUUT documentation, i have found descritpions for some configuration files.<br>
_(Ghica - I am reorganizing this list according to purpose)_ <br/>
processing of a fuut model<br>

*conf/fuut2s.ini* - List of FUUT plugins used for ... _the basic Fuut-je configuration_ <br>
*conf/FtSuperTab.ini* - List of FUUT plugins used for ... _This list is an extension of the previous list and can be loaded multpiple times, since you can add new tab-panels, each with its own model to your Fuut-je workspace._ <br>
*conf/fuutbatch.ini* - List of FUUT plugins used during the batch processing of fuut models. _Note that this is an example only. The actual list needed depends on the list of actions you want to execute, as provided by an .ftbatch file._ <br> 

*conf/FtSwingSet.cglist* - A template set used to generate Swing components of generated application (correct?)<br>
_Not exactly. This is the basic set of templates needed to generate a full application with a Swing GUI from a *Fuut-je model*. This set is also used for the generated parts od Fuut-je itself._ <br/>
*conf/EMFStructure.cglist* - A template set used to generate EMF structure of a model (correct?)<br>
_Almost. This is a set of templates that you can use to generate *annotated Java*. This Java you can use to import into EMF and EMF will create an EMF model out of it. This is the easiest way to convert a Fuut-je model into an EMF model._ <br/>
*conf/FtDocOnly.cglist* - A template set used to generate FUUT documentation (correct? _yes_ Javadoc? _no, it is much more compact than Javadoc_ )<br><br/>
*conf/Velo.cglist* - A template set used to generate Velocity templates (correct?) -- _this should be removed from CVS. It was a failed attempt to generate Velocity templates from Fuut-je templates. Not worth the trouble. (Ghica)_

*conf/php.vlist* - ... _this is a set of Velocity templates to generate PHP code and MySQL DDL from a Fuut-je model. It actually works great, and it is very much work in progress. (Ghica)_ <br>
*conf/FtvList.vlist* - ... _should be removed_ <br>

*conf/exampleBatch.ftbatch* - An example file containing the sequence of actions to be taking during a particular batch procedure. _Fuut-je batch processing is very handy to generate code in a build procedure. (Ghica)_

*resources/exampleBatch.properties* - An example file containing the list of configuration properties used during the batch processing of a fuut model (Exactly what properties are defined here?)<br> 
*resources/Ft.properties* - List of configuration properties used for initialization of a swing-based FUUT frontend (correct? Exactly what properties are defined here?) <br/>
_(Ghica) At start-up of Fuut-je you can specify a *properties* file as parameter (default: ft.properties). If you open up one of the files, the parameters defined in it are pretty obvious I think._ <br>
_One execption: <verbatim>"InitialMessage = FtBatch conf/examplebatch.ftbatch"</verbatim> in the exampleBatch.properties indicates the first action to be taken after Fuut-je is started. In this case the FtBatch action, that takes the .ftbatch file as parameter (see the description about batch processing on the gmt site)._

-- Main.AntonLitvinenko - 04 Jul 2004

My suggestion for refactoring the startup configuration processing would be to combine the information in the .ini, .properties and .ftbatch files into *one* XML file. 

Make a model using Fuut-je that can handle this information and generate code for it (see the Fuut-je tutorial). The generated code is capable of reading and writing XML in the desired format, it also has a Swing GUI that you can use to create/edit the XML files. You just have to write a little wrapper to interface this with =FuutTool=, or whichever module you choose to process the configuration information.

-- Main.GhicaVanEmdeBoas - 06 Jul 2004