Another minor design question. In TreeModel one finds methods like:
getIterFirst()
getIter(TreePath) // convert a TreePath
returning TreeIters.
In TextBuffer, there are:
getStartIter(),
getEndIter(), and
getIterAtMark(TextMark)
which return TextIters.
Uniformity is important, so yYou can probably guess where I'm heading.
I am chafing at the asymmetry between TextBuffer and TreeModel's
"iterator" retrieving methods. I am therefore considering presenting our
public API as:
getIterStart(),
getIterEnd(), and
getIter(TextMark)
instead. The completion space at getIter<COMPLETE> looks a lot better.
AfC
Sydney
|