<div dir="ltr">On Wed, Sep 25, 2013 at 11:21 PM, Sebastian Kügler <span dir="ltr"><<a href="mailto:sebas@kde.org" target="_blank">sebas@kde.org</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Wednesday, September 25, 2013 17:51:41 Mark wrote:<br>
> Doesn't your naming proposal completely ruin the org.kde.* stuff? Up until<br>
> now i could fairly safely assume that all QML KDE imports where hidden<br>
> under org.kde.* but that isn't the case anymore if you introduce<br>
> private.org.kde.*<br>
<br>
</div>That's exactly the point: we don't want you to find it, much less to rely on<br>
it. It's basically application internal "stuff" you have no business with.<br>
<div class="im"><br>
> It looks like you miss a part in the url.. I would say something like this:<br>
> org.kde.public.* = public imports<br>
> org.kde.private.* = private imports<br>
><br>
> But that would require changing all existing components to reflect this<br>
> idea..<br>
<br>
</div>That, and it would encourage to maybe use it as second class API, and still<br>
cause us the same problems.<br></blockquote><div><br></div><div>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.kde since it breaks consistency. Or to me it looks like it breaks consistency. org.kde.* is the consistent manner so somehow you should figure out a way to add private included in that structure.</div>
<div><br></div><div>Another thing, why do you even need a private import location? Can't you simply do local privates?</div><div><br></div><div>That would mean something like:</div><div>import "../private" as Private</div>
<div><br></div><div>or something along those lines. I don't get why it has to be in a global namespace. </div></div></div></div>