[prev in list] [next in list] [prev in thread] [next in thread]
List: koffice-devel
Subject: Re: flake/canvasController
From: Pierre Stirnweiss <pstirnweiss () googlemail ! com>
Date: 2010-09-19 12:43:30
Message-ID: AANLkTinrC6OSqBo1cKcZRcOQdavavPrNGk4WtKPVjT3H () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
I also think that it would indeed be good. We are here in a bit of a
particular case: some of our core developers are developing something as
outside users. In this case things get a bit confusing.
However, let's take a complete outsider company, who would want to develop
an application (closed source at least temporary) based on our libs. If they
would come asking (with a patch) to change our core API, we probably would
ask them for some example usecases. Which means, not necessary their app but
at least a good show case of how our classes would be used and why the
change in API would be necessary.
Pierre
On Sun, Sep 19, 2010 at 1:10 PM, Boudewijn Rempt <boud@valdyas.org> wrote:
> On Sunday 19 September 2010, Thorsten Zachmann wrote:
> > On Friday 17 September 2010 16:10:59 Inge Wallin wrote:
> >
> > > The patch by boud was a direct application of this: A need to use
> > > QGraphicsView as a base for the canvas controller was identified, a
> design
> > > and implementation was proposed that satisfied that need, it was
> > > discussed, Ok'ed and committed.
> > >
> > > It is true that not all of the feature is open source yet and therefore
> not
> > > visible. In this case I am fairly certain that it will be, but that is
> a
> > > little beside the point. The point is that we are letting our package
> be
> > > used as a platform, and we have decided to not only allow that but
> > > actively encourage it.
> >
> > I think it would be good to have a test app in svn as long as there is no
> > other usage of the code so that it is visible how the design works. It
> should
> > show how the design is used. With that everybody can have a look at the
> design
> > and no code needs to be made public which cannot be made public at the
> moment.
>
> I can do that, no problem. It will be different from the code that hasn't
> been released yet, since I don't think it's a good idea to base this test
> app on libmeegotouch -- but it would still show that the design Marijn and
> me came up with makes pretty cool things possible.
>
> --
> Boudewijn Rempt | http://www.valdyas.org
> Ceterum censeo lapsum particulorum probae delendum esse
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@kde.org
> https://mail.kde.org/mailman/listinfo/koffice-devel
>
[Attachment #5 (text/html)]
I also think that it would indeed be good. We are here in a bit of a particular case: some of \
our core developers are developing something as outside users. In this case things get a bit \
confusing.<br>However, let's take a complete outsider company, who would want to develop an \
application (closed source at least temporary) based on our libs. If they would come asking \
(with a patch) to change our core API, we probably would ask them for some example usecases. \
Which means, not necessary their app but at least a good show case of how our classes would be \
used and why the change in API would be necessary.<br> <br>Pierre<br><br><br><div \
class="gmail_quote">On Sun, Sep 19, 2010 at 1:10 PM, Boudewijn Rempt <span dir="ltr"><<a \
href="mailto:boud@valdyas.org">boud@valdyas.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, \
204); padding-left: 1ex;"> <div class="im">On Sunday 19 September 2010, Thorsten Zachmann \
wrote:<br> > On Friday 17 September 2010 16:10:59 Inge Wallin wrote:<br>
><br>
> > The patch by boud was a direct application of this: A need to use<br>
> > QGraphicsView as a base for the canvas controller was identified, a design<br>
> > and implementation was proposed that satisfied that need, it was<br>
> > discussed, Ok'ed and committed.<br>
> ><br>
> > It is true that not all of the feature is open source yet and therefore not<br>
> > visible. In this case I am fairly certain that it will be, but that is a<br>
> > little beside the point. The point is that we are letting our package be<br>
> > used as a platform, and we have decided to not only allow that but<br>
> > actively encourage it.<br>
><br>
> I think it would be good to have a test app in svn as long as there is no<br>
> other usage of the code so that it is visible how the design works. It should<br>
> show how the design is used. With that everybody can have a look at the design<br>
> and no code needs to be made public which cannot be made public at the moment.<br>
<br>
</div>I can do that, no problem. It will be different from the code that hasn't been \
released yet, since I don't think it's a good idea to base this test app on \
libmeegotouch -- but it would still show that the design Marijn and me came up with makes \
pretty cool things possible.<br>
<div class="im"><br>
--<br>
Boudewijn Rempt | <a href="http://www.valdyas.org" \
target="_blank">http://www.valdyas.org</a><br> Ceterum censeo lapsum particulorum probae \
delendum esse<br> _______________________________________________<br>
</div><div><div></div><div class="h5">koffice-devel mailing list<br>
<a href="mailto:koffice-devel@kde.org">koffice-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/koffice-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/koffice-devel</a><br> \
</div></div></blockquote></div><br>
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic