[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: QML-using app developers: use private.* imports
From:       Mark <markg85 () gmail ! com>
Date:       2013-09-27 17:37:57
Message-ID: CAPd6JnEN5REQZ5RQt=tsHDtUkwiOhQpTScCutfrwrs7vqhLRyg () mail ! gmail ! com
[Download RAW message or body]

On Wed, Sep 25, 2013 at 11:21 PM, Sebastian Kügler <sebas@kde.org> 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 that isn't the case anymore if you introduce
> > private.org.kde.*
>
> That's exactly the point: we don't want you to find it, much less to rely
> on
> it. It's basically application internal "stuff" you have no business with.
>
> > It looks like you miss a part in the url.. I would say something like
> this:
> > org.kde.public.* = public imports
> > org.kde.private.* = private imports
> >
> > But that would require changing all existing components to reflect this
> > idea..
>
> That, and it would encourage to maybe use it as second class API, and still
> cause us the same problems.
>

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.

Another thing, why do you even need a private import location? Can't you
simply do local privates?

That would mean something like:
import "../private" as Private

or something along those lines. I don't get why it has to be in a global
namespace.

[Attachment #3 (text/html)]

<div dir="ltr">On Wed, Sep 25, 2013 at 11:21 PM, Sebastian Kügler <span \
dir="ltr">&lt;<a href="mailto:sebas@kde.org" \
target="_blank">sebas@kde.org</a>&gt;</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> &gt; Doesn&#39;t your naming proposal completely ruin the org.kde.* \
stuff? Up until<br> &gt; now i could fairly safely assume that all QML KDE imports \
where hidden<br> &gt; under org.kde.* but that isn&#39;t the case anymore if you \
introduce<br> &gt; private.org.kde.*<br>
<br>
</div>That&#39;s exactly the point: we don&#39;t want you to find it, much less to \
rely on<br> it. It&#39;s basically application internal &quot;stuff&quot; you have no \
business with.<br> <div class="im"><br>
&gt; It looks like you miss a part in the url.. I would say something like this:<br>
&gt; org.kde.public.* = public imports<br>
&gt; org.kde.private.* = private imports<br>
&gt;<br>
&gt; But that would require changing all existing components to reflect this<br>
&gt; 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 &quot;private&quot; 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&#39;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&#39;t you simply do local privates?</div><div><br></div><div>That would mean \
something like:</div><div>import &quot;../private&quot; as Private</div>

<div><br></div><div>or something along those lines. I don&#39;t get why it has to be \
in a global namespace. </div></div></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]