Re: [Themis-dev] CSS support

[Mark H. <ma...@fi...>]

>Mark Hellegers wrote:
>> Hi,
>>
>> I mentioned I was going to look into the state of the CSS support in
>> Themis.
>> I have done some investigation and it seems we can use the parser that
>is
>> already in there.
>> I'm going to start working on making it work and hooking it into Themis
>> properly.
>>
>> Parsing, however, is only part of the whole CSS picture. We need a
>proper
>> structure to store the CSS information in and the CSS parser has some
>> support, but very minimal. I started something long ago, but never
>> finished it and I'm not yet sure if I can use that or if that needs to
>be
>> scrapped.
>> On top of that, the rules to determine which rule applies to an element
>> can be fairly complex as far as I understand it, so I will tackle that
>> part after parsing is properly working.
>>
>> Any comments, suggestions, etc are always welcome.
>>
>> Mark
>>
>>
>   I remember a few discussions (on which I think we disagreed :) )
>about trying to integrate CSS into the DOM tree some how, possibly
>applying the attributes directly to the branches. I think I've learned
>enough about CSS since then to see that it might not be practical;
>basically supporting your position about it not being a good idea.
>(Although I think you disagreed on the principle of modularity.) Beyond
>that, I don't really have any thoughts on CSS. :-/

I also learned a lot since then, especially from the rewrite of the html
parser.
My intention is to first get the css parser to work only parsing the
files. Putting them in a nice structure can come later. I really need to
take a good look good at that, because I don't want to rewrite this part
three times as well. :)

>On a separate but tangentially related subject, some time soon, I'm going
>to start piecing together a central activity tree which will house
>information about URLs loaded within a certain lifetime (say the last 4-5
>hours). Basically, it'll list URLs directly requested, the images and
>other media files requested as a result of parsing the page's HTML,
>content statuses, sizes, and types, and possibly window/tab
>relationships, and window/tab history. I still have a lot of thought to
>put into this, and I hope to actually write out a simple design document
>before I actually start coding it. The basic idea is the URL manager that
>I think I had Michael begin on years ago, but a bit better thought out
>than what I had described at the time... :-) I know it might be best to
>reuse code or complete what was already started, but I want to start from
>scratch on it.

That would be really cool. I'm looking forward to your ideas on this one.
Did you manage to take a look at the problem with reading the wrong data ?

Mark

-- 
Spangalese for beginnners: