KDirModelV2, KDirListerV2 and UDSEntryV2 suggestions

[Mark]

On Thu, Jan 10, 2013 at 11:54 PM, Aaron J. Seigo <aseigo at kde.org> wrote:
> On Thursday, January 10, 2013 19:37:39 you wrote:
>> >> Is there another
>> >> dirmodel fork somewhere that does that? Link please :)
>> >
>> > well, what we ought to do is do a threaded version and then put it
>> > somewhere we can all share it properly :) i'll discuss with Marco what he
>> > thinks and come back with a proposal.
>>
>> you make it sound like it's closed source..? no link to some exotic
>> highly experimental git branch?
>
> hehe.. no, none yet ... reason i want to talk about with Marco is this will
> impact our devel efforts elsewhere in the plasma-mobile code, so we would need
> to factor any changes in there.
>
> and this really seems like the sort of thing that ought to be available in the
> Plasma Components in kde-runtime so that everyone can use it (and hack on it)
> without making copies :)
>
>> > so +1 from me for making KDirModel do its business in an encapsulated
>> > thread.
>> I guess that is the way forward then. But i do wonder, if the
>> KDirModel API stays the same but the internals change completely, is
>> that KF5 material or can it go in 4.xx as well?
>
> imho, probably KF5 because:
>
> a) we want KF5 sooner rather than later, so efforts should focus there.[1]
> b) KDirModel is such a key component with a high complexity and few people who
> know it very well; so it needs lots of testing, and 5.0 would be a better
> target for that kind of development imho
> c) it will give us something to market about 5.0 -> SO MUCH FASTER / MORE
> FLUID DIRECTORY LISTINGS (that's mostly, but only mostly, tongue-in-cheek)
>
> [1] as an aside: we've re-focused effort on libplasma2 in KF5. the new QML
> based containment stuff being worked on has been moved to libplasma2-only and i
> expect other such development in Plasma to continue that way. we're also
> expecting / planning Plasma Active 5 to be focused on moving to Qt5 + KF5.
>
> --
> Aaron J. Seigo
>
> _______________________________________________
> Kde-frameworks-devel mailing list
> Kde-frameworks-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
>

Just wondering a "little" thing about making KDirModel threaded.. How
can you even do that?
KDirModel inherits from QAbstractItemModel and that works just fine.

If you add in threading the KDirModel doesn't inherit from
QAbstractItemModel anymore.. The internal class "KDirModelPrivate"
would inherit from QAbstractItemModel where KDirModel itself would
inherit from probably QObject.

..?
Or would the KDirModel need to inherit from QThread?
Just something i wonder because setModel(QAbstractItemModel * model)
needs a class that's subclassing QAbstractItemModel which KDirModel
isn't doing in the above scenario..

I'm probably missing something obvious here. I hope someone can
explain how that is supposed to be resolved?

Cheers,
Mark