On Friday, September 27, 2013 19:37:57 Mark wrote:
> I think one can very easily expect a part called "private" to be just that
> and that it should not be included. If one does do that then that person
> deserves the pain when the private api changes. I don't think you should go
> to private.org.k
On Wed, Sep 25, 2013 at 11:21 PM, Sebastian Kügler wrote:
> On Wednesday, September 25, 2013 17:51:41 Mark wrote:
> > Doesn't your naming proposal completely ruin the org.kde.* stuff? Up
> until
> > now i could fairly safely assume that all QML KDE imports where hidden
> > under org.kde.* but tha
On Thursday 26 September 2013 02:23:31 Aleix Pol wrote:
> The question would be then, why is it that there's some API that's only
> needed for internal usage? If it's needed internally, it will be most
> likely needed externally, at some point. The fact that you decide to label
> it as private mak
Hola,
On Thursday, September 26, 2013 02:23:31 Aleix Pol wrote:
> Reducing API to maintain is a good thing, at least for complexity sake. But
> of course there will be always the case where somebody needs (part of) the
> private API.
>
> The question would be then, why is it that there's some API
On Wed, Sep 25, 2013 at 3:51 PM, Sebastian Kügler wrote:
> Hey all,
>
> In Plasma, we've been looking into privatizing parts of the QML API we
> offer.
> With Qt5, we rely less on setContextProperty() and friends, and use imports
> more. That's a technical necessity that makes one problem more ev
On Wednesday, September 25, 2013 17:51:41 Mark wrote:
> Doesn't your naming proposal completely ruin the org.kde.* stuff? Up until
> now i could fairly safely assume that all QML KDE imports where hidden
> under org.kde.* but that isn't the case anymore if you introduce
> private.org.kde.*
That's
> hidden under org.kde.* but that isn't the case anymore if you
> introduce private.org.kde.*
>From my POV, Sebastian's proposal is spot-on for that reason alone - it is
not a (public) 'qml kde import'. It is a private thing.
Cheerio,
Ivan
p.s. and, in all honesty grepping for org.kde will retur
On Wed, Sep 25, 2013 at 3:51 PM, Sebastian Kügler wrote:
> Hey all,
>
> In Plasma, we've been looking into privatizing parts of the QML API we
> offer.
> With Qt5, we rely less on setContextProperty() and friends, and use imports
> more. That's a technical necessity that makes one problem more ev
Hey all,
In Plasma, we've been looking into privatizing parts of the QML API we offer.
With Qt5, we rely less on setContextProperty() and friends, and use imports
more. That's a technical necessity that makes one problem more evident: It's
unclear what QML-facing API is reliable and stable, and
