> On 21 May 2025, at 08:47, Volker Hilsheimer via Development
> wrote:
>
>
>
>> On 20 May 2025, at 12:50, Giuseppe D'Angelo
>> wrote:
>>
>> On 20/05/2025 10:26, Richard Gustavsen wrote:
>>> Would it be more convenient to put the range API directly on QRangeModel
>>> instead? E.g:
>>> QRa
> On 20 May 2025, at 12:50, Giuseppe D'Angelo wrote:
>
> On 20/05/2025 10:26, Richard Gustavsen wrote:
>> Would it be more convenient to put the range API directly on QRangeModel
>> instead? E.g:
>> QRangeModel model({1, 2, 3, 4, 5});
>> listView.setModel(&model);
>> model.erase(model.begin())
On 20/05/2025 10:26, Richard Gustavsen wrote:
Would it be more convenient to put the range API directly on QRangeModel
instead? E.g:
QRangeModel model({1, 2, 3, 4, 5});
listView.setModel(&model);
model.erase(model.begin());
model[0] = x;
model.push_back(y);
Yes, this is an important question
>
> I would like to come up with some C++ template class that gives type-safe
> access to the model while also respecting QAIM requirements, but doesn’t
> require any usage of QModelIndex, role values etc. I suspect that “Adaptor”
> will be a good term to use for such a class. Something along t
On Wed, 14 May 2025 at 18:53, Elvis Stansvik wrote:
>
> Den ons 14 maj 2025 12:32Volker Hilsheimer via Development
> skrev:
>>
>> > On 12 May 2025, at 13:29, Kevin Kofler via Development
>> > wrote:
>> >
>> > Volker Hilsheimer via Development wrote:
>> >> I suspect that “Adaptor” will be a goo
Den ons 14 maj 2025 12:32Volker Hilsheimer via Development <
development@qt-project.org> skrev:
> > On 12 May 2025, at 13:29, Kevin Kofler via Development <
> development@qt-project.org> wrote:
> >
> > Volker Hilsheimer via Development wrote:
> >> I suspect that “Adaptor” will be a good term to us
> On 12 May 2025, at 13:29, Kevin Kofler via Development
> wrote:
>
> Volker Hilsheimer via Development wrote:
>> I suspect that “Adaptor” will be a good term to use for such a class.
>
> Is this not more commonly spelled "Adapter"?
>
>Kevin Kofler
Both spellings are permissible, Adap
Volker Hilsheimer via Development wrote:
> I suspect that “Adaptor” will be a good term to use for such a class.
Is this not more commonly spelled "Adapter"?
Kevin Kofler
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
> On 12 May 2025, at 10:41, Giuseppe D'Angelo wrote:
>
> On 12/05/2025 09:53, Volker Hilsheimer wrote:
>> Would a simple
>> QRangeItemModel
>> be clear enough? The “Based” doesn’t seem to add a lot of clarity.
>
> It does what it says, though. But before discussing this further...
>
>
>> Als
On 12/05/2025 09:53, Volker Hilsheimer wrote:
Would a simple
QRangeItemModel
be clear enough? The “Based” doesn’t seem to add a lot of clarity.
It does what it says, though. But before discussing this further...
Also, as discussed at Qt CS (and mentioned in the last point of the notes
ath
Il 09/05/25 17:26, Edward Welbourne ha scritto:
>> The only issue I have is with the name.
> QRangeAdaptorItemModel ?
> Just reading your words back at you ...
Giuseppe D'Angelo (Saturday, May 10, 2025 11:37) replied
> Well, maybe the authors of the class wanted to defend their naming
> choice.
On 2025-05-09, Sune Vuorela wrote:
> It looks like it is built on a range or a collection/container of
> tuples or something like that
I just digged in my personal archives and found from 2016
| class TemplatedMagicModel : public QAbstractTableModel
I'm definitely not saying I'm good at naming
> On 10 May 2025, at 11:37, Giuseppe D'Angelo via Development
> wrote:
>
> Il 09/05/25 17:26, Edward Welbourne ha scritto:
>>> The only issue I have is with the name.
>> QRangeAdaptorItemModel ?
>> Just reading your words back at you ...
>
> Well, maybe the authors of the class wanted to defend
Il 09/05/25 17:26, Edward Welbourne ha scritto:
The only issue I have is with the name.
QRangeAdaptorItemModel ?
Just reading your words back at you ...
Well, maybe the authors of the class wanted to defend their naming
choice. :-)
QRangeAdaptorItemModel or QRangeBasedItemModel work for me.
Giuseppe D'Angelo (9 May 2025 15:01) wrote:
> In a nutshell, it's an adaptor that wraps a range and exposes it
> through the QAIM API.
[snip]
> The only issue I have is with the name.
QRangeAdaptorItemModel ?
Just reading your words back at you ...
Eddy.
--
Development mailing list
Devel
On Friday, 9 May 2025 15:59:35 Central European Summer Time Volker Hilsheimer
via Development wrote:
> Our future AI overlord says:
I tried classnamer.org for about 100 tries, and the best it came up with was
ResponsibleMetadataCollector, so I suggest QResponsibleMetadataItemModel
--
Thiago Ma
On 2025-05-09, Volker Hilsheimer via Development
wrote:
> It’s not abstract, but it’s also not specific.
It looks like it is built on a range or a collection/container of
tuples or something like that
QRangeBasedItemModel ?
QTupleCollectionItemModel ?
QContainerItemModel ?
I'm a bit with Guis
> On 9 May 2025, at 15:01, Giuseppe D'Angelo via Development
> 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
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 to the
model/view framework without writing boilerplate.
19 matches
Mail list logo
