[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Possible cause of kivio problems
From:       Shawn Gordon <shawn () thekompany ! com>
Date:       2001-05-01 14:45:10
[Download RAW message or body]

At 08:21 AM 5/1/2001, you wrote:
>On Tuesday 01 May 2001 15:05, Shawn Gordon wrote:
> > At 07:11 AM 5/1/2001, you wrote:
> > >On Monday 30 April 2001 21:23, Ben Burton wrote:
> > > > Hi.  I've written this to a mailing list and to a kivio developer but
> > > nobody
> > > > has conformed or denied my suspicions.  Basically I believe the 
> reason the
> > > > connector tool is no longer working is because libkiviopart.so is no
> > > longer
> > > > directly linked to /usr/bin/kivio; instead it is being dlopened and 
> as a
> > > > result straight_connector.ksp can no longer find symbols it needs from
> > > > libkiviopart.so.
> > >
> > >It seems you are correct - this matches Waldo's findings too,
> > >and explains why the change happened recently: when we removed
> > >the link from the binary to the part (which was quite an ugly
> > >design, the code being both linked to and dlopened).
> > >
> > >Shawn: there you go. The fix is to either make the binary link the
> > >part again, or the plugins link the part, or better, follow Waldo's
> > >suggestion.
> > >
> > >An ACL really doesn't help here. It's Werner and I who made this change
> > >to all koffice apps, anyway :P
> >
> > Well here is a reason to use ACL.  6 days ago M. Laurant removed 
> several of
> > our icons and put them in koffice/pics, which I would imagine would be 
> fine
> > if they were actually there
>
>I see textcolor there but not pencolor and fillcolor indeed.
>I guess he forgot to cvs add them. Laurent?
>This happens all the time with cvs, BTW :)

which is another argument for ACL it seems

> > but they aren't so now we had to spend the
> > time to find the problem, and reverse it which would have been better 
> spent
> > on fixing the embedding problem.  It's 3 icons, fillcolor, textcolor,
> > pencolor, and I have no idea why someone would take them out of our
> > application.
>
>Guess ? To use them in other applications. See below.
>
> > At the same time M. Laurant also took all of our libraries in tklib
> > (thekompany library) and moved them to kofficeui.  None of this was
> > discussed with us, and this is a rather major modification.  We are the
> > project maintainers, and having the wholesale dispersal of our code 
> without
> > even a "hey, guess what I'm doing" at the same time as the beta for 
> KOffice
> > is outrageous.  This is causing us an enormous amount of extra work, and I
> > would dearly love the courtesy shown other project maintainers.
>
>Sorry, I really don't see where's the problem. A set of GPL widgets
>was moved in a common place so that other apps could use them.
>What extra work ? The stuff has been moved, it still works in kivio,
>and this makes it possible to use the same widgets in kword, kspread etc.
>This improves consistency in KOffice, and thus was a good move.
>
>"outrageous" ? Give me a break.
>If you don't want other koffice apps to use those widgets, then kivio
>isn't GPL.

What is outrageous is that a major surgery job was done on Kivio without 
any discussion whatsoever with us, and things were broken in the 
process.  What is outrageous is this was done on the day of the beta 
release.  The idea on a beta is do to bug fixes, not wholesale changes to 
the code, and it doesn't all work in Kivio now, that is the point.  Maybe 
if someone had said "Hey Shawn, it would be cool to have this and this from 
Kivio for all of Koffice, will you slice it out for us and stick it here" 
that would have been a better way to go.  I don't recall even seeing a 
discussion on it, but I'm not on koffice-devel, I only read the summaries, 
so maybe I missed it.

Again, I thought project maintainers had a little more contact with their 
projects, at least this is what we were assured when we put Kivio in 
Koffice, and was why we ultimately agreed to do it.

>I agree that a small mail about the move would have been nice to prevent
>the surprise, though.
>
>--
>David FAURE, david@mandrakesoft.com, faure@kde.org
>http://perso.mandrakesoft.com/~david/, http://www.konqueror.org/
>KDE, Making The Future of Computing Available Today


Regards,

Shawn Gordon
President
theKompany.com
www.thekompany.com
949-713-3276

[prev in list] [next in list] [prev in thread] [next in thread]