> On 9 May 2025, at 15:01, Giuseppe D'Angelo via Development
> <development@qt-project.org> wrote:
>
> Hi,
>
> QGenericItemModel is a new API (TP?) in 6.10:
> https://doc-snapshots.qt.io/qt6-dev/qgenericitemmodel.html
>
> In a nutshell, it's an adaptor that wraps a range and exposes it through the
> QAIM API. This allows to expose e.g. a std::vector<X> to the model/view
> framework without writing boilerplate.
>
> The only issue I have is with the name. It doesn't really *say* anything
> about what it does. We also end up with having "Abstract" and "Generic"
> classes (confusion). I'd like not to repeat the precedent of
> "QStandardItemModel" (there's nothing _standard_ about it).
>
> So, well before 6.10 freezes, can we discuss the possibility of renaming the
> class?
>
> Thanks,
> --
> Giuseppe D'Angelo
We can discuss the possibility of renaming, and you can even propose better
names :)
It’s not abstract, but it’s also not specific.
Our future AI overlord says:
A good word for something that is not abstract but can still apply broadly to
anything that meets certain criteria or models a concept is:
“Generic”
Other options depending on nuance:
• “Prototype” – if it serves as a typical example or template.
• “Template” – if it is meant to be reused with different specifics.
• “Archetype” – if it’s a fundamental or ideal example of a concept.
• “Parametric” – in technical or design contexts, when something is defined
in terms of parameters.
“Generic” is likely the most fitting if you mean something that is concrete or
instantiated, but still widely applicable due to flexibility or generality.
Volker
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
