Hello,

(resending since this got bounced back)

On Sat, Jan 3, 2015 at 7:39 AM, Dmitriy Purgin <dpur...@gmail.com> wrote:

> Hello,
>
> Recently I was implementing a directory picker in a Sailfish application
> and it has come to my attention that there are two independent
> FolderListModels for QML: one ships with Qt [1] and another comes from
> nemomobile [2]. They have incompatible API and seem to be developed in
> unawareness of its counterpart. I like Nemo version for its extended
> functionality like permissions, mkpath and rename but the Qt Labs version
> is being shipped by the most prominent Nemo user -- Jolla -- whereas Nemo
> version doesn't even appear in Sailfish repositories.
>
> That being said, I'd like to know whether there's any policy in Nemo
> regarding these situations. Should there be any API merge towards
> Qt.labs.FolderListModel (which for obvious reasons would be the upstream
> version)?
>

in such cases I would say upstream versions are preferred, additional
changes/features should go there. Nemo version doesn't seem to be active
anymore judging by the activity in the repo.

Best regards,


>
> Thanks
>
> Cheers
> Dmitriy
>
> [1]
> https://qt.gitorious.org/qt/qtdeclarative/source/96e4f00db3bfd222146780251013501cfdd8baaa:src/imports/folderlistmodel
> [2] https://github.com/nemomobile/nemo-qml-plugin-folderlistmodel
>



-- 
Valério Valério

Reply via email to