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

List:       kde-devel
Subject:    Re: port of pyjamas to pykde / khtml - issues and observations with
From:       "Luke Kenneth Casson Leighton" <lkcl () lkcl ! net>
Date:       2008-10-13 20:43:17
Message-ID: ced5f0f60810131343l3d87037er6a4fc1a7b4949c76 () mail ! gmail ! com
[Download RAW message or body]

> also, crucially - absolutely, absolutely crucially: you can't do a
> "compare" against nodes.  the objects are potentially different.  and

folks, hi,

this is a show-stopper, and needs to be fixed.  i tried creating a
workaround wrapper class, by extending pykhtml's dom.py, with a view
to making it the "central" location - choke-point - through which the
creation of all Node and Node-derived objects go, but there doesn't
exist a function in the underlying DOM model to uniquely identify the
c++ objects.  not the wrappers _around_ the c++ objects, the c++
objects themselves.

i'm trying to find the right people to speak to about this issue.  the
pykde mailing list server, since it moved in 2007, is down.
http://lists.kde.org/?l=pykde&m=117334580215794&w=2

riverbankcomputing, who host the web pages for pykde, such that their
web site is listed as the home page, say that they are not responsible
for the development of pykde.

so... who is responsible for the development of pykde; where is its
source code hosted; etc. etc.  riverbankcomputing's web site doesn't
appear to list pykde as an actively maintained project - it says
"documentation", "download" .... errr.. that's about it.

this one appears to be falling through the gaps in the woodwork and
it's a really quite powerful tool, especially the DOM model
manipulation, which is very much under-appreciated.

l.
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]