p.stirnweiss_koffice | 1 Sep 2004 09:07
Picon
Favicon

Re: Shadow distance type


>-- Message original --
>From: Nicolas Goutte <nicolasg <at> snafu.de>
>To: For developer's discussion about KOffice <koffice-devel <at> mail.kde.org>
>Date: Tue, 31 Aug 2004 22:50:16 +0200
>Subject: Re: Shadow distance type
>Reply-To: For developer's discussion about KOffice <koffice-devel <at> mail.kde.org>
>
>
>As you have not shown how the linker is called, it is diffuclt to tell if
>
>libkofficecore is included in the list of libraries to link against.

no it is not. But I wonder why, given the fact that they it is in the same
directory than libkdeui and this one has been picked up automatically without
problem.

>
>On Tuesday 31 August 2004 22:34, p.stirnweiss_koffice <at> bluewin.ch wrote:
>> >-- Message original --
>>
>> From: Nicolas Goutte <nicolasg <at> snafu.de>
>>
>> >To: For developer's discussion about KOffice <koffice-devel <at> mail.kde.org>
>> >Date: Tue, 31 Aug 2004 20:59:08 +0200
>> >Subject: Re: Shadow distance type
>> >Reply-To: For developer's discussion about KOffice
>> > <koffice-devel <at> mail.kde.org>
>> >
>> >On Tuesday 31 August 2004 20:51, p.stirnweiss_koffice <at> bluewin.ch wrote:
(Continue reading)

Nicolas Goutte | 1 Sep 2004 09:57
Picon

Re: Shadow distance type

Is it possible that you compile against KOFFICE CVS HEAD but link against 
KOFFICE 1.3.x?

On Wednesday 01 September 2004 09:07, p.stirnweiss_koffice <at> bluewin.ch wrote:
> >-- Message original --
>
> From: Nicolas Goutte <nicolasg <at> snafu.de>
>
> >To: For developer's discussion about KOffice <koffice-devel <at> mail.kde.org>
> >Date: Tue, 31 Aug 2004 22:50:16 +0200
> >Subject: Re: Shadow distance type
> >Reply-To: For developer's discussion about KOffice
> > <koffice-devel <at> mail.kde.org>
> >
> >
> >As you have not shown how the linker is called, it is diffuclt to tell if
> >
> >libkofficecore is included in the list of libraries to link against.
>
> no it is not. But I wonder why, given the fact that they it is in the same
> directory than libkdeui and this one has been picked up automatically
> without problem.
>
> >On Tuesday 31 August 2004 22:34, p.stirnweiss_koffice <at> bluewin.ch wrote:
> >> >-- Message original --
> >>
> >> From: Nicolas Goutte <nicolasg <at> snafu.de>
> >>
> >> >To: For developer's discussion about KOffice
> >> > <koffice-devel <at> mail.kde.org> Date: Tue, 31 Aug 2004 20:59:08 +0200
(Continue reading)

p.stirnweiss_koffice | 1 Sep 2004 11:04
Picon
Favicon

Re: Shadow distance type


>-- Message original --
>From: Nicolas Goutte <nicolasg <at> snafu.de>
>To: For developer's discussion about KOffice <koffice-devel <at> mail.kde.org>
>Date: Wed, 1 Sep 2004 09:57:44 +0200
>Subject: Re: Shadow distance type
>Reply-To: For developer's discussion about KOffice <koffice-devel <at> mail.kde.org>
>
>
>Is it possible that you compile against KOFFICE CVS HEAD but link against
>
>KOFFICE 1.3.x?

No because KOffice 1.3.x has never been installed on that box. How recent
is the KoDoubleUnitSpinBox code? My compile is probably a week or two old
now.

>
>On Wednesday 01 September 2004 09:07, p.stirnweiss_koffice <at> bluewin.ch wrote:
>> >-- Message original --
>>
>> From: Nicolas Goutte <nicolasg <at> snafu.de>
>>
>> >To: For developer's discussion about KOffice <koffice-devel <at> mail.kde.org>
>> >Date: Tue, 31 Aug 2004 22:50:16 +0200
>> >Subject: Re: Shadow distance type
>> >Reply-To: For developer's discussion about KOffice
>> > <koffice-devel <at> mail.kde.org>
>> >
>> >
(Continue reading)

p.stirnweiss_koffice | 1 Sep 2004 11:31
Picon
Favicon

Re: Shadow distance type


>-- Message original --
>Date: Wed, 1 Sep 2004 11:04:47 +0200
>From: p.stirnweiss_koffice <at> bluewin.ch
>To: "For developer's discussion about KOffice" <koffice-devel <at> mail.kde.org>
>Subject: Re: Shadow distance type
>Reply-To: For developer's discussion about KOffice <koffice-devel <at> mail.kde.org>
>
>
>
>>-- Message original --
>>From: Nicolas Goutte <nicolasg <at> snafu.de>
>>To: For developer's discussion about KOffice <koffice-devel <at> mail.kde.org>
>>Date: Wed, 1 Sep 2004 09:57:44 +0200
>>Subject: Re: Shadow distance type
>>Reply-To: For developer's discussion about KOffice <koffice-devel <at> mail.kde.org>
>>
>>
>>Is it possible that you compile against KOFFICE CVS HEAD but link against
>>
>>KOFFICE 1.3.x?
>
>No because KOffice 1.3.x has never been installed on that box. How recent
>is the KoDoubleUnitSpinBox code? My compile is probably a week or two old
>now.

I checked my local code and there is code for KoDoubleUnitSpinBox

>
>>
(Continue reading)

Nicolas Goutte | 1 Sep 2004 12:28
Picon

Re: Shadow distance type

On Tuesday 31 August 2004 22:50, Nicolas Goutte wrote:
> As you have not shown how the linker is called, it is diffuclt to tell if
> libkofficecore is included in the list of libraries to link against.

Silly me, the unit widget are in kofficeui, not in kofficecore...

>
(...)
Nicolas Goutte | 1 Sep 2004 12:37
Picon

Re: Shadow distance type

Sometimes I have got curious linking errors when a class was only forward 
defined and not completely defined.

So check if you have really included the right header file.

By the way: are those the only errors given by make or is there anything 
before, especially a warning?

Have a nice day!

On Wednesday 01 September 2004 11:04, p.stirnweiss_koffice <at> bluewin.ch wrote:
> >-- Message original --
>
> From: Nicolas Goutte <nicolasg <at> snafu.de>
>
> >To: For developer's discussion about KOffice <koffice-devel <at> mail.kde.org>
> >Date: Wed, 1 Sep 2004 09:57:44 +0200
> >Subject: Re: Shadow distance type
> >Reply-To: For developer's discussion about KOffice
> > <koffice-devel <at> mail.kde.org>
> >
> >
> >Is it possible that you compile against KOFFICE CVS HEAD but link against
> >
> >KOFFICE 1.3.x?
>
> No because KOffice 1.3.x has never been installed on that box. How recent
> is the KoDoubleUnitSpinBox code? My compile is probably a week or two old
> now.
>
(Continue reading)

Raphael Langerhorst | 1 Sep 2004 12:02
Picon
Picon

KSpread redesign

Hi all,

As it seems now that things get started with KSpread, maybe we can set up a 
wiki to keep a good summary of what is currently being done, the overall 
plan, who is taking care about what, etc.

I couldn't read much mail during the last week so I might have missed some 
info here. This is also a reason why I would value such a summary website 
because if one simply can't read mails for two or three weeks it would be 
enough to just take a look at the wiki site and know where we are.

Should we use the quality page for KOffice for it? Or should we dedicate a 
KSpread wiki for it? Should we use a wiki at all?

What do you think?

Raphael

PS: kspread/FORMATTING_DESIGN holds some thoughts on redesign... but you 
probably all know that anyway.

PPS: I am quite unsure what part I will be working on. I'm keen on helping in 
some way. But this might range from implementing/redesigning specific KSpread 
classes to helping Marc with a new KSpread handbook... although I'm a 
programmer I'm also very much dedicated to documentation - and most of the 
time I write the docs before I write source code. Anyway, just wanted to say 
that I can't tell yet in what way I will help. Also, if I don't help with 
discussing specific implementation details it either means I simply don't 
know enough about the subject or I try to save time somehow (often both). But 
as soon as someone says "OK, and THIS is the way we do it.", then I'll be 
(Continue reading)

Nicolas Goutte | 1 Sep 2004 13:20
Picon

Re: KSpread redesign

Well, having an overview page (be it normal web or Wiki or whatever) is only 
good if it remains up-to-date or you would still need to read the bunch of 
emails to get informed.

Have a nice day!

On Wednesday 01 September 2004 12:02, Raphael Langerhorst wrote:
> Hi all,
>
> As it seems now that things get started with KSpread, maybe we can set up a
> wiki to keep a good summary of what is currently being done, the overall
> plan, who is taking care about what, etc.
>
> I couldn't read much mail during the last week so I might have missed some
> info here. This is also a reason why I would value such a summary website
> because if one simply can't read mails for two or three weeks it would be
> enough to just take a look at the wiki site and know where we are.
>
> Should we use the quality page for KOffice for it? Or should we dedicate a
> KSpread wiki for it? Should we use a wiki at all?
>
> What do you think?
>
> Raphael
(...)
p.stirnweiss_koffice | 1 Sep 2004 14:07
Picon
Favicon

Re: Shadow distance type


>-- Message original --
>From: Nicolas Goutte <nicolasg <at> snafu.de>
>To: For developer's discussion about KOffice <koffice-devel <at> mail.kde.org>
>Date: Wed, 1 Sep 2004 12:37:54 +0200
>Subject: Re: Shadow distance type
>Reply-To: For developer's discussion about KOffice <koffice-devel <at> mail.kde.org>
>
>
>Sometimes I have got curious linking errors when a class was only forward
>
>defined and not completely defined.
>
>So check if you have really included the right header file.
I have #include <koUnitWidgets.h> in the header file of the DecoTab, so I
guess it is OK.

>
>By the way: are those the only errors given by make or is there anything
>
>before, especially a warning?

I have two warnings of converting to int from double and that's it.

>
>Have a nice day!
>
>On Wednesday 01 September 2004 11:04, p.stirnweiss_koffice <at> bluewin.ch wrote:
>> >-- Message original --
>>
(Continue reading)

Marc Heyvaert | 1 Sep 2004 14:19
Picon
Favicon

Re: KSpread redesign

Hello,

--- Raphael Langerhorst <raphael-langerhorst <at> gmx.at>
wrote:

> 
> Should we use the quality page for KOffice for it?
> Or should we dedicate a 
> KSpread wiki for it? Should we use a wiki at all?
> 

Well, the Quality Team KDE KOffice page is really
there for other stuff (and it is more or less dead
BTW). But it is easy to create a new wikipage on
wiki.kde.org and there could be a link to it from the
KOffice quality page.

> But this might range from
> implementing/redesigning specific KSpread 
> classes to helping Marc with a new KSpread
> handbook...

I have decided to translate the existing docs into
dutch first. I made a start with the KOffice handbook
and found myself correcting mistakes and updating
outdated stuff. This one is finished now and I will
tackle the rest as well. I may add some screenshots
too.

As for the sequel to this...I started writing an
(Continue reading)


Gmane