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

List:       quanta-devel
Subject:    Re: [quanta-devel] Re: KDOM
From:       Paulo Moura Guedes <moura () kdewebdev ! org>
Date:       2005-05-25 18:28:15
Message-ID: 200505251928.15250.moura () kdewebdev ! org
[Download RAW message or body]

On Wednesday 25 May 2005 19:11, Andras Mantia wrote:
> On Wednesday 25 May 2005 21:07, Paulo Moura Guedes wrote:
[...]
> > In source - Text -> Node tree
> > Why can't we just update the node tree when needed:
> > - Change to the VPL view; rebuilding all the node tree is acceptable
> > IMO.
>
> Right.
>
> > - Before doing any node manipulation, which doesn't happen
> > offteb in source mode.
> > - In split mode I also don't thing that it is problematic to update
> > all the node tree in order to update VPL when editing in source.
>
> What would help is to detect which nodes were changed in the (Quanta)
> node tree and merge that with the KHTML DOM tree. Just like we do with
> the source. The whole node tree is not rebuilt on every keypress, just
> the part which was changed.

But there will not be any Quanta tree IIUC. We will use a tree that is 
compatible with khtml so it's very fast. This is one more reason to give some 
credit to the tree :)

> > So, I don't see other possible solution neither any real complicated
> > issue to solve.
>
> So your proposal is to keep the current implementation?

No. My proposal is to drop the dual tree solution that we have now and cleanup 
the code. That would be an extraordinary enhancement IMPOV.

I'm going to see the Champions Leag Final and dinner now. Cya later.
-- 
Paulo Moura Guedes

Linux Caixa Mágica  - http://caixamagica.org
KDE Web Development - http://kdewebdev.org
_______________________________________________
quanta-devel mailing list
quanta-devel@kde.org
https://mail.kde.org/mailman/listinfo/quanta-devel

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