Guillaume and chakie asked me to
clarify my whingeing about the QT API in my previous entry.
Here’s what I told
Guillaume. He said that most of these points weren’t
significant, not really to my satisfaction. I’d post his
comments, but it was a person-to-person email thread.
> > I suppose you’re mostly thinking of the containers here,
as the widgets API is quite orthogonal IMHO. :-)
Orthogonal is maybe not the best word. In particular I
- Duplication of menu APIs.
- The confusing way that the constructors are overriden
that argument position is more important than argument
- The way that add-to-parent is implicit in the
of the widget.
- The way that add-to-parent means different things
depending on the type of the child, again implicitly. e.g.
Layouts are not children in the same way that widgets
are.>> Can you show me an example of what you think is
“inadequate functionality” ?
- The QTable has a tiny, inadequate, API.
- There is no Document/View
- I do not find the choice of QLayouts very useful,
but maybe I need to go beyond QGridLayout.
Of course my dislike of pre-processor and non-standard
containers is well known. We had a clear and sensible
discussion of these issues in <a