From quanta-devel  Mon May 09 11:19:51 2005
From: Rob Buis <rwlbuis () xs4all ! nl>
Date: Mon, 09 May 2005 11:19:51 +0000
To: quanta-devel
Subject: [quanta-devel] Re: KDOM & CSS
Message-Id: <20050509111951.GA75227 () xs4all ! nl>
X-MARC-Message: https://marc.info/?l=quanta-devel&m=111563760200663

Hi Paulo,

Sorry for the late reply.

On Tue, May 03, 2005 at 01:32:43PM +0100, Paulo Moura Guedes 
wrote:
> Hi,
> 
> I think it would be cool if Quanta could have a toolview with all the CSS 
> properties values for a tag in the source document. I mean values like they 
> are calculated by a user agent, after inheritance and cascading rules. 
> This way the user could understand more easily what are really the values that 
> are affecting a tag.
> I guess kdom already offers this functionality as each node on the document 
> source tree should have the style information attached.
> What would also be needed is to know what is the matching selector and also 
> the source of rule, i.e., if it us defined in an external stylesheet, etc, so 
> the IDE can modify its value.
>  
> Do you think this can be done with kdom and, if yes, can you give some tips on 
> how to do it?

Well, the same datastructures are used in kdom as in khtml css. Our 
priorities were to get css running to be used in svg and not to
differ too much in code to khtml css, to ease possible porting. This
more or less means above usage should be the same as for khtml. We
may lack some classes to access the computed values, you'd have to try it 
though.

About the external stylesheet, my guess is that the href is set then, so
you could take that as a criterium. Please let me know any quirks you find
if you test the kdom css :)
Cheers,

Rob.
_______________________________________________
quanta-devel mailing list
quanta-devel@kde.org
https://mail.kde.org/mailman/listinfo/quanta-devel