Before joining this discussion take a look at FuutConfiguration topic.

Do You think, it is better to separate batch processing configuration and GUI application configuration into separate parts of configuration? I believe it would be more convinient to have one configuration file (as You pointed out on the wiki) and some property of this would tell if FUUT-je to be ran as a GUI app or in batch mode. I think it is possible to create such structure that will represent/encapsulate equally well properties of both configurations. -- AntonLitvinenko - 06 Jul 2004

I think it is better, as I said in the wiki, to combine batch and GUI processing. Actually, Fuutje is not aware at all whether it is running batch or GUI. It depends on the plugins you are loading. You can even do batch in the GUI. It is like a movie you are showing then. -- GhicaVanEmdeBoas - 07 Jul 2004

Combining GUI FUUTje and headless FUUTje (running in batch mode) doesn't mean we should not separate configuration for those! I think final result we would like to achieve is that by configuring build script we can create distribution of headless FUUT or GUI versioned FUUT. It would be good not to leave too much configuration for a user. -- MarkKofman - 07 Jul 2004

One file vs many configuration files.  Sure one file is better, however I don't think it is reasonable sometimes. E.g. we will need to maintain 2 similar configuration files both for GUI FUUTje and for headless. It will make sence to break up the file into units logicaly and to reuse them. -- MarkKofman - 07 Jul 2004

I have already tried Jfig, XmlDigester^? and Castor tools for managing the XML configuration of projects. I think, it is a good idea to use FUUT-je facilities to manage its configuration, since if i am not mistaken this will let us to have configuration in a object-oriented style (like castor with its mapping files and marshalling/unmarshalling functionality). On the other hand Jfig is very simple and is very similar to java "properties configuration" in style. XmlDigester^? is capable of processing configuration in both object-oriented and properties style and it is quite easy to parse XMLs with it. But neither of these libraries have a tool for editing the configuration. So,in my opinion, it would be cool to generate such GUI tool by FUUT-je. -- AntonLitvinenko - 06 Jul 2004

You will find that Fuut-je is the easiest to use of all these tools, once you understand how a model maps onto the XML. Just do the tutorial, and look at the XML that is saved if you run the generated application and enter some data in it. -- GhicaVanEmdeBoas - 07 Jul 2004

Ghica, I guess you are a bit biased ;) Some points which in my opinion should influence our decision:

• Using FUUTje for configuration would be "politicaly correct" :)
• Using a tool like Jfig can add additional features specific to managing configuration files and not only XML parsing
• By using tool meant specially for convinient XML parsing we could gain some good ideas and probably later implement them in the FUUTje

-- MarkKofman - 07 Jul 2004