Where to put QML Bindings for KDE frameworks?

[Kevin Ottens]

On Wednesday 29 January 2014 09:20:09 Martin Klapetek wrote:
> On Tue, Jan 28, 2014 at 7:10 PM, Kevin Ottens <ervin at kde.org> wrote:
> > I don't think we'll get a one size fit all type of solution, that will
> > heavily
> > depend on the nature of the framework. For instance something like KConfig
> > should probably provide it's own imports, it is in the natural order of
> > things
> > as it already provides a core/gui split. KIO is in pretty much the same
> > situation.
> > 
> > But for some others it is less clear... For those ones we'll have to
> > decide if
> > we want to change them toward providing several payloads as well (sounds
> > doable for most except the *addons ones), or if we want the import to be
> > in
> > one of the imports provided by KDeclarative.
> 
> One of the downsides that wasn't mentioned yet (I think) is keeping the
> imports away from their modules can (and possibly will) cause the imports
> to bitrot and get behind the modules. Say that someone makes some changes
> to the framework but forgets/doesn't know about imports in KDeclarative, so
> those stay unupdated and may even break. Can also lead to "not my problem"
> situation when the KDeclarative maintainer will say "that's code from kio,
> talk to kio maintainer" etc.
> 
> So I think it makes sense to keep the code together.

Definitely. My point was that I'm not convinced we'll be able to do that in 
100% of the cases.

Regards.
-- 
Kévin Ottens, http://ervin.ipsquad.net

KDAB - proud supporter of KDE, http://www.kdab.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20140129/70c9ce42/attachment.sig>