Which design pattern to use

Good answer by JSOP (my 5), but as a fan of Design (Patterns) I just must put his answer into a little perspective. First of all I think JSOP is right in just doing what works for you and get the job done. Doing everything 'by the book' might mean not getting anything done at all in the end. I think Design (Patterns) should be seen as general guidelines (not static tools) for how to possibly or partly solve programming problems. For my part you use the Singleton Pattern and make it work for your specific case (it won't, just trying to make a point). Don't be to focused on using one specific pattern. You might need your own adaption of a pattern or you might need multiple patterns combined. Do not worry to much on what name to use and just do what must be done.
My favourite way of programming is actually to just start out and abstract away certain stuff as I go along (which might not work for everyone). Knowing about Design Patterns can help along the way, but are merely guides, not answers.
Of course the danger in 'just getting things done' is that you program certain code multiple times, get spaghetti code etc. But as long as you avoid the so called 'anti-patterns'[^] and use your brains you should be fine. Also remember that having bad implementations of good Design Patterns can be just as harmful, or even more harmful due to 'thought out complexity' than no Design Patterns at all :)

You may find this useful - as you are working in c++:
XML C++ code generators[^]

I'd look at XMLSpy[^] first.

While not a design pattern - using effective tools is a good work pattern :)

Regards
Espen Harlinn

I would say Builder is the way to go. Although, there are a number of ways to tackle this problem that don't necessarily include GoF design patterns.