jim, hi,
https://bugs.kde.org/show_bug.cgi?id=172740
the maintainers of the khtmlpart have agreed to add an enum to uniquely
identify every single object derived from Node, which should help.
are you _sure_ it's to do with twine - twine is going to have to be
_seriously_ sophisticated, to under
Aaron Digulla wrote:
>
> Quoting Luke Kenneth Casson Leighton <[EMAIL PROTECTED]>:
>
>
> I'd like to use the HTML edit mode of webkit (there is a demo editor
> which comes with the webkit source).
>
there is? _great_. i wasn't aware of that. cool. very handy.
> My main issue with
David Boddie wrote:
>
>> there's something very, very important that gobject can do, and i am
>> unsure that it is appropriate to use e.g. QObject to do the same
>> thing, or even if Qt4 is capable of doing what gobject can provide
>> (which it could very well do, but i don't know how), and it's
David Boddie wrote:
>
> I don't think it was a problem in PyKDE3. At least, I don't remember
> running
> into any issues with casting - not with the DOM classes anyway. My brother
> wrote some convenience wrappers around the KHTML DOM, so I think I would
> have
> heard something if it had been
Jim Bublitz wrote:
>
> On Tuesday 14 October 2008 14:21, Luke Kenneth Casson Leighton wrote:
>
>> the issue is that the wrapper objects aren't unique [don't return the
>> same python object for a given DOM c++ object], due to the underlying
>> c++ objects being typecast down to "Node*" (or Elem
