Fwd: Re: kdenonbeta/kdom/css

[Rob Buis]

Forwarding, suspecting this is a better place for discussing this stuff...

----- Forwarded message from Rob Buis <rwlbuis at xs4all.nl> -----

Hi,

On Fri, Feb 13, 2004 at 02:49:48PM -0500, Zack Rusin wrote:
> On Friday 13 February 2004 14:06, Rob Buis wrote:
> > On Fri, Feb 13, 2004 at 01:56:17PM -0500, Zack Rusin wrote:
> > > On Friday 13 February 2004 13:35, Nikolas Zimmermann wrote:
> > > > CVS commit by wildfox:
> > > >
> > > > Fix libcroco includes
> > >
> > > So instead of adopting our css parser from khtml you decided to use
> > > a gnome lib? May I ask why?
> >
> > Because it will happily parse svg css props, unlike css parser from
> > khtml? Cheers,
> 
> Guys but we don't know what your problems are because you don't 
> communicate enough. In fact you don't communicate at all. If you'd have 
> let Dirk know the problems you're having I'm sure we could resolve them 
> somehow. 

Well, you may have a point about the lack of communication, sorry...
But it wasnt always easy in the past to find the right discussion 
channels. I mean if there was a #khtml irc channel, we would have been 
nagging Dirk and co a lot more :)

> It's hard to figure out what you're doing because you usually respond 
> saying that "khtml doesn't do something you wanted it". Well, duh, it 
> wasn't written for svg but it doesn't mean that we couldn't work on 
> fixing/implementing whatever you needed.

Ok, the points about not being able to read minds is ofcourse justified,
point taken.
I must say Zack filling in lots of KHTML implementations (like 
getComputedStyle) and Dirk offering to install more headers is very 
positive, thanks!

I guess there are some future paths for ksvg :

1) Integrate fully inside khtml repository.
2) Install more khtml headers so it is easier to extend khtml, even with
   code outside khtml repository.
3) Keep working on the kdom prototype, having a functional dom at the cost
   of code duplication and doubled testing efforts.
4) Stick to the hacks we used for KSVG now to keep the half-working DOM.

IMHO number 4 is something we want to avoid, as Niko has already 
explained.

I would like to hear opinions on benefits and downsides to 1 and 2?
BTW is there a better place (mailing list?) to discuss things like this?
Cheers,

Rob.

----- End forwarded message -----