I am currently looking at 2 examples:

  • Simple DOM model - I assume I can load my data into QDomDocument and then move from there.... this will give me out of the box the "export to xml" feature.. .which is nice... but somewhat over killl..
  • Simple Tree Model Example - it's more or less what I am looking for... but it implies that my code will be much more... "heavier", instead of the light code I wrote originally. It feels like I am re-designing my code to work with MVC, and IMHO that breaks the idea that the data should not be restricted by the view, or model. I assume "blah... shut up and code..."


One implies re-writing my model to be tied with DOM, which as I said has it's benefits. The other screams at me "use QObject and get rid of it!". I was wondering what other developers have done. Is there another option?