[prev in list] [next in list] [prev in thread] [next in thread]
List: koffice-devel
Subject: Re: Google Online document Plugin for KOffice
From: Mani N C <maninc () gmail ! com>
Date: 2010-07-06 12:50:31
Message-ID: AANLkTilQCnREdd6XIkKGrXB2fbnKq2sDZhnIsZyVpmTb () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
I was travelling and couldn't access my mail.
Let me add my 2 cents,
I personally don't mind to put my code inside trunk or outside, if it goes
with the application.
I just have one question, Does plugin code in Kofficeplugin will remain
there forever or After sometime should it be moved to trunk/plugin again ?
Only thing i'm worried about is, I don't want my work to go wasted since it
is inside the source repo. I would be really happy If this will also go with
the official koffice package, even from kofficeplugin.
@ Dr.Robert Marmorstein: Yes, I would like to look in to your code. I
couldn't find it in KOffice repo. Could you please send me the link to it?
--Mani
On Tue, Jul 6, 2010 at 12:50 PM, Thomas Zander <zander@kde.org> wrote:
> On Tuesday 6. July 2010 09.08.59 Pierre Stirnweiss wrote:
> > Just a quick one to say, both are not mutually exclusive. Indeed, I think
> > it is even possible to have both a kofficeplugins repo for people who
> want
> > to develop plugins without the constraints of the official repo, but
> still
> > want an easy install, and a plugins/staging subdirectory in our repo for
> > people who prefer to develop inside the official repo (but with all the
> > constraints attached).
>
> Thats a very good point, thanks for adding that.
>
> I have the feeling that some are responding a bit briskly because they
> might
> have assumed there was a secondary reason to my suggestion. The intention
> to
> move existing code from koffice to the kofficeplugins dir.
> Naturally this will never happen without consent of the maintainer of that
> plugin. So if that worry was a reason for objecting, then please don't
> worry.
>
> For new plugin developers the option should be there for both locations,
> with
> the differences made clear.
> And both are part of the koffice community. Which is a huge win over todays
> status quo.
> --
> Thomas Zander
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@kde.org
> https://mail.kde.org/mailman/listinfo/koffice-devel
>
--
N C Manikanda Prasad
[Attachment #5 (text/html)]
<div>I was travelling and couldn't access my mail. </div><div>Let me add my 2 \
cents,</div><div><br></div><div>I personally don't mind to put my code inside \
trunk or outside, if it goes with the application. </div><div>
I just have one question, Does plugin code in Kofficeplugin will remain there forever \
or After sometime should it be moved to trunk/plugin again ? </div><div>Only thing \
i'm worried about is, I don't want my work to go wasted since it is inside \
the source repo. I would be really happy If this will also go with the official \
koffice package, even from kofficeplugin. </div>
<div><br></div><div>@ Dr.Robert Marmorstein: Yes, I would like to look in to your \
code. I couldn't find it in KOffice repo. Could you please send me the link to \
it?</div><div><br></div><div>--Mani</div><br><div class="gmail_quote">
On Tue, Jul 6, 2010 at 12:50 PM, Thomas Zander <span dir="ltr"><<a \
href="mailto:zander@kde.org">zander@kde.org</a>></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 Tuesday 6. July 2010 09.08.59 Pierre Stirnweiss wrote:<br>
> Just a quick one to say, both are not mutually exclusive. Indeed, I think<br>
> it is even possible to have both a kofficeplugins repo for people who want<br>
> to develop plugins without the constraints of the official repo, but still<br>
> want an easy install, and a plugins/staging subdirectory in our repo for<br>
> people who prefer to develop inside the official repo (but with all the<br>
> constraints attached).<br>
<br>
</div>Thats a very good point, thanks for adding that.<br>
<br>
I have the feeling that some are responding a bit briskly because they might<br>
have assumed there was a secondary reason to my suggestion. The intention to<br>
move existing code from koffice to the kofficeplugins dir.<br>
Naturally this will never happen without consent of the maintainer of that<br>
plugin. So if that worry was a reason for objecting, then please don't worry.<br>
<br>
For new plugin developers the option should be there for both locations, with<br>
the differences made clear.<br>
And both are part of the koffice community. Which is a huge win over todays<br>
status quo.<br>
<font color="#888888">--<br>
</font><div><div></div><div class="h5">Thomas Zander<br>
_______________________________________________<br>
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><br clear="all"><br>-- <br>N C Manikanda \
Prasad<br><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