2011/2/2 Mani N C
>
> Hello All,
> I need your comments/Inputs for the possible solutions,
> 1. Write a Wrapper class for KoAbstractApplicationController which would have
> all the slots and signals in it and Child(MainWindow) can create a object of
> the wrapper and connect the signals to it.
>
on kde-core-devel, John Layt and Michael Janssen came up with this git commit
template:
# ---[ You MUST wrap all lines at 72 characters ]--|
#
# ---[ Please see http://techbase.kde.org/Policies/Commit_Policy ]-|
#
# ===[ Subject ]===
> On Feb. 2, 2011, 6:54 p.m., Boudewijn Rempt wrote:
> > I like it, also because it removes another hard-coded dependency on
> > KoCanvasControllerWidget.
On IRC Cyrille suggested to pass the action collection to the constructor. I
will change that and then update the patch.
- Sven
---
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/100508/#review1162
---
Ship it!
I like it, also because it removes another hard-coded
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/100522/
---
(Updated Feb. 2, 2011, 3:02 p.m.)
Review request for Calligra.
Summary (
On Wednesday 02 February 2011, todd rme wrote:
> That is fine once we have an initial "main" release, but in my opinion
> you made a clear commitment to support koffice 2.3 until then. I
> think abandoning koffice 2.3 now would be a P.R. disaster. First, it
> could easily be portrayed as spiteful
On Wed, Feb 2, 2011 at 5:31 AM, Cyrille Berger Skott
wrote:
> On Wednesday 02 February 2011, Inge Wallin wrote:
>> But as a user, I expect to be able to update to either a new version with
>> new features and possibly also new bugs or a more stable release with no
>> new features but also definit
On Wednesday 02 February 2011, Inge Wallin wrote:
> Do you have any thoughts
> on when to interrupt this scheme and go to X releases per year (4 is not
> yet decided)?
When Calligra is user-ready :) So in about 6 to 8 monthes.
--
Cyrille Berger Skott
2011/2/2 C. Boemann :
> On Wednesday 02 February 2011 10:34:30 Pierre Stirnweiss wrote:
>> On Wed, Feb 2, 2011 at 10:18 AM, Boudewijn Rempt wrote:
>> > On Wednesday 02 February 2011, Inge Wallin wrote:
>> > > Do you plan to make real, i.e. not previews, of Krita in the mean time?
>> >
>> > The
>>
On Wed, 2 Feb 2011, Inge Wallin wrote:
> While this is true, the Linux distros work the same way. I think we should
> ask
> the packagers first what they think of the idea.
I think packaging is mostly automated these days. It'll be possible, though,
that
one or more of the distros will pick a
On Wednesday, February 02, 2011 11:26:10 Boudewijn Rempt wrote:
> On Wednesday 02 February 2011, Inge Wallin wrote:
> > I may have misunderstood, but if I understood correctly I'm very sorry to
> > have to say that I hate this. The reason is that it is a
> > developer-centric way to work rather tha
On Wednesday 02 February 2011, Inge Wallin wrote:
> But as a user, I expect to be able to update to either a new version with
> new features and possibly also new bugs or a more stable release with no
> new features but also definitely less bugs.
It is temporary. Until we have reached a user ready
On Wednesday 02 February 2011, Inge Wallin wrote:
> I may have misunderstood, but if I understood correctly I'm very sorry to
> have
> to say that I hate this. The reason is that it is a developer-centric way to
> work rather than a user-centric.
>
> I'm sure it will be very ego-boosting for u
On Wednesday 02 February 2011 11:08:56 Cyrille Berger Skott wrote:
> On Wednesday 02 February 2011, C. Boemann wrote:
> > Calligra Suite 2.3 Stable snapshot 201103
>
> For packagers we would need a proper version number. One that is lower than
> the next stable, and bigger than the previous one.
s
On Wednesday 02 February 2011, C. Boemann wrote:
> Calligra Suite 2.3 Stable snapshot 201103
For packagers we would need a proper version number. One that is lower than
the next stable, and bigger than the previous one.
--
Cyrille Berger Skott
___
call
On Wednesday, February 02, 2011 10:34:30 Pierre Stirnweiss wrote:
> On Wed, Feb 2, 2011 at 10:18 AM, Boudewijn Rempt wrote:
> > On Wednesday 02 February 2011, Inge Wallin wrote:
> > > Do you plan to make real, i.e. not previews, of Krita in the mean time?
> >
> > The
> >
> > > reason I ask is th
On Wednesday 02 February 2011 10:47:40 Boudewijn Rempt wrote:
> On Wednesday 02 February 2011, C. Boemann wrote:
> > I like this very much, both now and as the future way of releasing.
> >
> > i would assume our first release would then be:
> >
> > Calligra Suite 2.3 Stable snapshot 201103
>
> I
On Wednesday 02 February 2011, C. Boemann wrote:
> I like this very much, both now and as the future way of releasing.
>
> i would assume our first release would then be:
>
> Calligra Suite 2.3 Stable snapshot 201103
>
I was rather hoping for a February release...
--
Boudewijn Rempt | http:/
On Wednesday 02 February 2011 10:34:30 Pierre Stirnweiss wrote:
> On Wed, Feb 2, 2011 at 10:18 AM, Boudewijn Rempt wrote:
> > On Wednesday 02 February 2011, Inge Wallin wrote:
> > > Do you plan to make real, i.e. not previews, of Krita in the mean time?
> >
> > The
> >
> > > reason I ask is that
On Wednesday 02 February 2011, Pierre Stirnweiss wrote:
> On Wed, Feb 2, 2011 at 10:18 AM, Boudewijn Rempt wrote:
>
> > On Wednesday 02 February 2011, Inge Wallin wrote:
> >
> > > Do you plan to make real, i.e. not previews, of Krita in the mean time?
> > The
> > > reason I ask is that I wonder w
On Wednesday 02 February 2011, Cyrille Berger Skott wrote:
> On Wednesday 02 February 2011, Jaroslaw Staniek wrote:
> > We have to plan branching rules for this, or is tagging the master our
> > way (+feature branches)? Whatever works for you.
> I wanted to discuss this at the sprint :)
:-). But t
On Wednesday 02 February 2011, Boudewijn Rempt wrote:
> Are you sure about the deps? I am fairly sure that we still compile against
> Qt 4.6 and KDE 4.5 -- maybe even 4.4.
yes it does. The build bot compiles calligra with Qt4.6 and KDE 4.4. (so does
some debian users :) ).
--
Cyrille Berger Sko
On Wed, Feb 2, 2011 at 10:18 AM, Boudewijn Rempt wrote:
> On Wednesday 02 February 2011, Inge Wallin wrote:
>
> > Do you plan to make real, i.e. not previews, of Krita in the mean time?
> The
> > reason I ask is that I wonder which Linux distros are going to package
> the
> > previews and how.
>
On Wednesday 02 February 2011, Jaroslaw Staniek wrote:
> We have to plan branching rules for this, or is tagging the master our
> way (+feature branches)? Whatever works for you.
I wanted to discuss this at the sprint :)
My idea was to have feature branches. And trying to have feature branches hav
On 2 February 2011 10:12, Inge Wallin wrote:
> On Wednesday, February 02, 2011 09:35:00 Boudewijn Rempt wrote:
>> Hi,
>>
>> With the removal of kexi, krita and kplato from the koffice.org website,
>> I'm reluctant to continue having krita released as part of KOffice 2.3.x.
>> In fact, even though
On Wednesday 02 February 2011, Jaroslaw Staniek wrote:
> On 2 February 2011 10:05, Cyrille Berger Skott wrote:
> > Only problem is that it would not really help users that would most likely
> > have to be satisfied with koffice 2.3 until we release something labeled
> > stable.
>
> I also see som
On Wednesday 02 February 2011, Inge Wallin wrote:
> Do you plan to make real, i.e. not previews, of Krita in the mean time? The
> reason I ask is that I wonder which Linux distros are going to package the
> previews and how.
I think that (after a bit of cleanup), Calligra master contains a sta
On 2 February 2011 10:05, Cyrille Berger Skott wrote:
> Only problem is that it would not really help users that would most likely
> have to be satisfied with koffice 2.3 until we release something labeled
> stable.
I also see something related to the recent thread about minimal Qt
dependencies.
On Wednesday 02 February 2011, Cyrille Berger Skott wrote:
> Only problem is that it would not really help users that would most likely
> have to be satisfied with koffice 2.3 until we release something labeled
> stable.
Well, that's why I stressed that master is quite stable -- and with a bit m
On Wednesday, February 02, 2011 09:35:00 Boudewijn Rempt wrote:
> Hi,
>
> With the removal of kexi, krita and kplato from the koffice.org website,
> I'm reluctant to continue having krita released as part of KOffice 2.3.x.
> In fact, even though I'm fairly sure that giving up maintainance of
> KOf
On 2 February 2011 09:35, Boudewijn Rempt wrote:
> Hi,
>
> With the removal of kexi, krita and kplato from the koffice.org website, I'm
> reluctant to continue having krita released as part of KOffice 2.3.x. In
> fact, even though I'm fairly sure that giving up maintainance of KOffice 2.3
> is
how about keep up two release branches, 2.4 and 3.0 snapshot?
On Wed, Feb 2, 2011 at 5:05 PM, Cyrille Berger Skott
wrote:
> Only problem is that it would not really help users that would most likely
> have to be satisfied with koffice 2.3 until we release something labeled
> stable.
>
> --
> Cyri
Only problem is that it would not really help users that would most likely
have to be satisfied with koffice 2.3 until we release something labeled
stable.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde
On Wednesday 02 February 2011, Jaroslaw Staniek wrote:
> (and Jaroslaw did remove all Cyrille's code as apparently shorter solution
> has been found, BUT Jaroslaw did this by looking at Cyrille's code as
> inspiration to this change). So Cyrille's copyright remains in r3. In
> calligra it's already
Thanks a lot for your inputs.
I will check with Marijn regarding that.
Br,
Mani
On Wed, Feb 2, 2011 at 1:31 PM, Boudewijn Rempt wrote:
> On Wednesday 02 February 2011, Jaroslaw Staniek wrote:
>
> > Just a thought:
> > BTW, do we want to consider having separate git repo for the
> > alternative
On 2 February 2011 09:23, Cyrille Berger Skott wrote:
> On Wednesday 02 February 2011, Jaroslaw Staniek wrote:
>> You have to copy any new copyrights too to every single relevant file
>> even if currently, after a number of commits there is no single
>> character of code by 'the other commiters'.
Hi,
With the removal of kexi, krita and kplato from the koffice.org website, I'm
reluctant to continue having krita released as part of KOffice 2.3.x. In fact,
even though I'm fairly sure that giving up maintainance of KOffice 2.3 is
exactly that TZ wanted to achieve, I don't think we should pu
> If you have:
> r3 by Jaroslaw
> r2 by Cyrille
> r1 by Casper
>
> at r1 file is copyrighted by Casper
> at r2 file is copyrighted by Casper, Cyrille
> at r3 file is copyrighted by Casper, Cyrille and Jaroslaw
>
> If someone takes the change at r2, it does not have to put Jaroslaw's
> copyright, on
In essence, provided that the copyright is respected, you can take any code
from calligra and put it in koffice, and vice-versa, without asking permission
from the original author. You might just have to be carefull that the target
project is willing to accept the contribution :)
On Wednesday 0
On Wednesday 02 February 2011, Jaroslaw Staniek wrote:
> You have to copy any new copyrights too to every single relevant file
> even if currently, after a number of commits there is no single
> character of code by 'the other commiters'. Whis is also obligation in
> the opposite way, so it's not o
On Wednesday 02 February 2011, Jaroslaw Staniek wrote:
> Just a thought:
> BTW, do we want to consider having separate git repo for the
> alternative GUIs, or even one-per gui? With the current infrastructure
> it's quite easy. And this could show the 3rd-parties that there APIs
> allow for such d
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/100522/#review1153
---
Ship it!
I'm curious for Boemann's todo's, since those seem to
42 matches
Mail list logo
