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

List:       calligra-devel
Subject:    Re: a new library
From:       Pierre Stirnweiss <pstirnweiss () googlemail ! com>
Date:       2012-12-19 12:40:46
Message-ID: CAOjaSmjBQYSewRykWhwUxFSHEaEYsKCeeW8Wwuvaizqi27fWtA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Wed, Dec 19, 2012 at 1:19 PM, C. Boemann <cbo@boemann.dk> wrote:

> On Wednesday 19 December 2012 13:11:51 Jaroslaw Staniek wrote:
> > On 19 December 2012 12:59, C. Boemann <cbo@boemann.dk> wrote:
> > > Yes i'm not attached to alpine in any way. I couldn't come up with a
> > > generic name that describes the library very well ( and no flaketools
> > > doesn't unless we wan to have many such similarly named libraries) and
> > > so when i wrote the mail that was just a codename that sprung to mind.
> >
> > After re-reading your initial post, how about: basictools or
> generictools?
> but since it may grow to hold shapes and dockers too i would find something
> named tools misleading
> _______________________________________________
> calligra-devel mailing list
> calligra-devel@kde.org
> https://mail.kde.org/mailman/listinfo/calligra-devel
>

basicflakes then? However, I think we are putting the cart before the
horses there. Shouldn't we first agree on a structure before discussing
labels?

Pierre

[Attachment #5 (text/html)]

<br><br><div class="gmail_quote">On Wed, Dec 19, 2012 at 1:19 PM, C. Boemann <span \
dir="ltr">&lt;<a href="mailto:cbo@boemann.dk" \
target="_blank">cbo@boemann.dk</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">

<div class="im">On Wednesday 19 December 2012 13:11:51 Jaroslaw Staniek wrote:<br>
&gt; On 19 December 2012 12:59, C. Boemann &lt;<a \
href="mailto:cbo@boemann.dk">cbo@boemann.dk</a>&gt; wrote:<br> &gt; &gt; Yes i&#39;m \
not attached to alpine in any way. I couldn&#39;t come up with a<br> &gt; &gt; \
generic name that describes the library very well ( and no flaketools<br> &gt; &gt; \
doesn&#39;t unless we wan to have many such similarly named libraries) and<br> &gt; \
&gt; so when i wrote the mail that was just a codename that sprung to mind.<br> \
&gt;<br> &gt; After re-reading your initial post, how about: basictools or \
generictools?<br> </div>but since it may grow to hold shapes and dockers too i would \
find something<br> named tools misleading<br>
<div class="HOEnZb"><div \
class="h5">_______________________________________________<br> calligra-devel mailing \
list<br> <a href="mailto:calligra-devel@kde.org">calligra-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/calligra-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/calligra-devel</a><br> \
</div></div></blockquote></div><br>basicflakes then? However, I think we are putting \
the cart before the horses there. Shouldn&#39;t we first agree on a structure before \
discussing labels?<br><br>Pierre<br>



_______________________________________________
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel


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