rwlbuis | 1 Jun 08:18 2004
Picon
Picon

svg path parser

Hi,

This is just a reminder, since we are converting to Oasis format, and some
koffice apps have to parse svg path data (like kpr, karbon, kivio).
In koffice/lib/kopainter/ there is svgpathparser which does this work nice
and fast :)
I'll make an attempt to do some work converting karbon to use Oasis (I
still dont like the pop group though).
Cheers,

Rob.
Laurent Montel | 1 Jun 17:01 2004
Picon

Re: svg path parser

On Tuesday 01 June 2004 08:18, rwlbuis <at> xs4all.nl wrote:
> Hi,
>
> This is just a reminder, since we are converting to Oasis format, and some
> koffice apps have to parse svg path data (like kpr, karbon, kivio).
> In koffice/lib/kopainter/ there is svgpathparser which does this work nice
> and fast :)

I don't know.
Great.
How is it work ?
we can use it as lib ?

Regards.

> I'll make an attempt to do some work converting karbon to use Oasis (I
> still dont like the pop group though).
> Cheers,
>
> Rob.
> _______________________________________________
> koffice-devel mailing list
> koffice-devel <at> mail.kde.org
> https://mail.kde.org/mailman/listinfo/koffice-devel
Rob Buis | 1 Jun 17:47 2004
Picon
Picon

Re: svg path parser

Hi,

On Tue, Jun 01, 2004 at 05:01:27PM +0200, Laurent Montel wrote:
> On Tuesday 01 June 2004 08:18, rwlbuis <at> xs4all.nl wrote:
> > Hi,
> >
> > This is just a reminder, since we are converting to Oasis format, and some
> > koffice apps have to parse svg path data (like kpr, karbon, kivio).
> > In koffice/lib/kopainter/ there is svgpathparser which does this work nice
> > and fast :)
> 
> I don't know.
> Great.
> How is it work ?

It is really easy, look in the header file ;)

> we can use it as lib ?

Yes, simply link in kopainter if it is not already linked in.
Cheers,

Rob.
Peter Hyman | 3 Jun 02:19 2004
Picon
Picon

Kpresenter Compile Time error -- kpresenter_view.cc

Compiling KOffice CVS version 1.3post (pulled 20040602), the following
compile time error occurs.

KDE=3.2.90 CVS (around two weeks ago)
Kernel 2.6.5
Slackware 9.1 updated

make[1]: Entering directory `/mnt/src/kde/koffice/kpresenter'
if /bin/sh ../libtool --silent --mode=compile --tag=CXX g++ -DHAVE_CONFIG_H -I. -I. -I..
-I../lib/kofficeui -I../lib/kofficeui -I../lib/kofficecore -I../lib/kofficecore
-I../lib/store -I../lib/store -I../lib/kwmf -I../lib/kwmf -I../lib/kotext -I../lib/kotext
-I/opt/kde3.2/include/arts -I/opt/kde3.2/include -I/usr/lib/qt/include -I/usr/X11R6/include  
-DQT_THREAD_SUPPORT  -D_REENTRANT  -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W
-Wpointer-arith -Wwrite-strings -O2 -Wformat-security -Wmissing-format-attribute
-fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL
-DQT_NO_COMPAT -DQT_NO_TRANSLATION  -MT kpresenter_view.lo -MD -MP -MF
".deps/kpresenter_view.Tpo" \
  -c -o kpresenter_view.lo `test -f 'kpresenter_view.cc' || echo './'`kpresenter_view.cc; \
then mv -f ".deps/kpresenter_view.Tpo" ".deps/kpresenter_view.Plo"; \
else rm -f ".deps/kpresenter_view.Tpo"; exit 1; \
fi
kpresenter_view.cc: In member function `void KPresenterView::setupActions()':
kpresenter_view.cc:2967: warning: `setRemoveAmpersandsInCombo' is deprecated
   (declared at /opt/kde3.2/include/kactionclasses.h:472)
kpresenter_view.cc: In member function `void
   KPresenterView::openPopupMenuMenuPage(const QPoint&)':
kpresenter_view.cc:4510: warning: enumeration value `BT_BRUSH' not handled in
   switch
kpresenter_view.cc: In member function `void KPresenterView::startKSpell()':
(Continue reading)

David Faure | 3 Jun 11:11 2004
Picon

Re: Kpresenter Compile Time error -- kpresenter_view.cc

On Thursday 03 June 2004 02:19, Peter Hyman wrote:
> kpresenter_view.cc:4830: no matching function for call to `KSpell2::Dialog::
>    activeAutoCorrect(bool)'

I think you need to update kdelibs, your kspell2 is too old.

--

-- 
David Faure, faure <at> kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
Kim Normand | 4 Jun 04:01 2004
Picon

Downloading

I want download the new version of KOffice!
I have presently the Fedora Core 1
How I cant download that? Please to join the link (connection) *lien.

How can`t download Fedora Core 2? Please to join the link (connection) *lien.
And I would like to know how install VMware Work Station in Fedora Core 1. Please to join the link (connection) *lien.
Kim Normand Kimcom Tecnologie http://kimnormand <at> videotron.ca
_______________________________________________
koffice-devel mailing list
koffice-devel <at> mail.kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
Nicolas Goutte | 6 Jun 23:05 2004
Picon

[FYI] Doxygen configuration file

I think that I have now a Doxygen configuration file usable for extracting all 
Doxygen comments of KOffice, with the minimum of unnecessary warnings.

("Extracting all" means also from *.c and *.cpp, internal classes, private 
members of classes.)

So if someone is interested, I can send it to him... or perhaps even post it 
on koffice.org (I am not sure).

Note: this configuration is not the same as the one use for koffice.org, which 
only extract like for KDE.

Have a nice day!

PS.: configuration file size 45KB uncompressed 11KB compressed (with 
comments.)
Raphael Langerhorst | 7 Jun 16:45 2004
Picon
Picon

closing old and uncomfirmed bug reports...

Hi there,

It seems again that I have a few hours to spend during the next few days. I 
will go through KSpread bug reports.

There seem to be many old reports, some of them a bit outdated and thus 
out-of-context or simply not reproducable, many are in the state 
"uncomfirmed". What shall I do about those, should I close them? Or should I 
contact the bug-reporter to check whether the bug is still valid for him/her?

... by the way, am I "allowed" to close bugs as user bugzilla <at> kde.org with 
KBugBuster? Or need I get a CVS account to change states of bug reports?

thanks,
Raphael
David Faure | 7 Jun 14:53 2004
Picon

Re: closing old and uncomfirmed bug reports...

On Monday 07 June 2004 16:45, Raphael Langerhorst wrote:
> Hi there,
> 
> It seems again that I have a few hours to spend during the next few days. I 
> will go through KSpread bug reports.
> 
> There seem to be many old reports, some of them a bit outdated and thus 
> out-of-context or simply not reproducable, many are in the state 
> "uncomfirmed". What shall I do about those, should I close them? Or should I 
> contact the bug-reporter to check whether the bug is still valid for him/her?

Coolo's script already contacted all bug reporters to ask for that.
If the reporter didn't write back and the bug is not reproduceable or doesn't
apply anymore (the code changed), go ahead and close them.

> ... by the way, am I "allowed" to close bugs as user bugzilla <at> kde.org with 
> KBugBuster? Or need I get a CVS account to change states of bug reports?

Neither. It's the permissions of your bugzilla account that matter.
If you don't see the buttons for closing bugs, write to sysadmin <at> kde.org and
ask for permissions to be added.

--

-- 
David Faure, faure <at> kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
Raphael Langerhorst | 7 Jun 17:11 2004
Picon
Picon

Re: closing old and uncomfirmed bug reports...

On Monday 07 June 2004 12:53, David Faure wrote:
> On Monday 07 June 2004 16:45, Raphael Langerhorst wrote:
> > Hi there,
> >
> > It seems again that I have a few hours to spend during the next few days.
> > I will go through KSpread bug reports.
> >
> > There seem to be many old reports, some of them a bit outdated and thus
> > out-of-context or simply not reproducable, many are in the state
> > "uncomfirmed". What shall I do about those, should I close them? Or
> > should I contact the bug-reporter to check whether the bug is still valid
> > for him/her?
>
> Coolo's script already contacted all bug reporters to ask for that.
> If the reporter didn't write back and the bug is not reproduceable or
> doesn't apply anymore (the code changed), go ahead and close them.
>
> > ... by the way, am I "allowed" to close bugs as user bugzilla <at> kde.org
> > with KBugBuster? Or need I get a CVS account to change states of bug
> > reports?
>
> Neither. It's the permissions of your bugzilla account that matter.
> If you don't see the buttons for closing bugs, write to sysadmin <at> kde.org
> and ask for permissions to be added.

ok, thanks. Just requested that.

Raphael

Gmane