General ideas for features / improvements in the next version? Bugs always get fixed, so I'm just thinking more the bigger ticket (by tiny standards) features.
Many of these are captured in the RFEs - which is great! - but I wanted to see how people felt about priortiy / importance / group usefulness.
I would start the list with:
1. White space handling consistent withe the XML spec.
2. Improved memory usage (fewer allocations, string pooling) intended to be friendlier to CE/Palm class devices.
3. Print to memory buffer (especially non-STL). Popular request on the forums.
4. Output format conrtol. Print() always "pretty prints". Add methods to control whitespace, etc.?
Note there is no plan or timeline for a next version - just collecting ideas.
lee
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Something I think might be useful is to include basic "visitor" support. I'll try to spec this out soon, but it would make traversal over a tree much easier, e.g. to write the contents of the tree to a file could be:
General ideas for features / improvements in the next version? Bugs always get fixed, so I'm just thinking more the bigger ticket (by tiny standards) features.
Many of these are captured in the RFEs - which is great! - but I wanted to see how people felt about priortiy / importance / group usefulness.
I would start the list with:
1. White space handling consistent withe the XML spec.
2. Improved memory usage (fewer allocations, string pooling) intended to be friendlier to CE/Palm class devices.
3. Print to memory buffer (especially non-STL). Popular request on the forums.
4. Output format conrtol. Print() always "pretty prints". Add methods to control whitespace, etc.?
Note there is no plan or timeline for a next version - just collecting ideas.
lee
Looks great so far :)
Something I think might be useful is to include basic "visitor" support. I'll try to spec this out soon, but it would make traversal over a tree much easier, e.g. to write the contents of the tree to a file could be:
options=TIX_INDENT;
TiFileWriter writer("foo.xml", options)
doc.Visit(writer)
writer.Close()
Similarly, to write the contents to a string (non-STL)
TiStringWriter writer(options)
doc.Visit(writer)
const char* s=writer.GetString()
The visitor pattern is well known and quite powerful, especially with C++ templates.
WDYT?
Will think about more ideas...
The Visit() idea would cover a bunch of feature requests regarding custom file I/O and (very) custom output actually.
lee