My ISP confirmed last night that my ADSL should be working from tomorrow, so I'll be getting back to work on XPath and KJSEmbed. Hurray!

I just moved house (like aseigo) and I second his thought on how much it sucks. My ISP was due to reconnect me to my ADSL today, but this morning I got a call saying it could be another week. Arghhhhh

I've started taking another look at how to best add support for XPath to KHTML. I've got a bunch of code I'm busy reexamining that lets you define an AST for XPath. It needs cleaning up but I think it is a decent first cut.

There's good news to report today, I added the first autogenerated binding to the CVS last night! The binding provides access to QDir but the tool is generic and should work on anything we can access as a JSOpaqueProxy (this limitation will be lifted later). There are still some rough edges, and the constructor functions aren't autogenerated yet but basically it works.

Here's a nice piccy of a water colour effect that was created using Javascript. It was originally one of the n7y pics - enjoy!

This didn't seem to work first time, so I'll try again:

I did a major reorganisation of the code just before the freeze hit. This caused a lot of breakage (eg. the wrapper classes were borked, as was KPart support), fortunately things are working again now. One important change is the use of separate classes to handle proxies for QVariant types and opaque pointers, this makes the code a hell of a lot easier to understand. Now that the structural stuff is done, Ian Geiser's SQL bindings seem to be basically working (though the QObject wrapper class needs a couple of bugs squashing) so the only thing that's left actually broken is the QPainter wrapper class. All in all, this code is looking good for the 3.2 release.

I haven't written much about KJSEmbed for the last couple of weeks because I've been concentrating on squashing bugs in kasbar, but over the last couple of days I've had a chance to work on some kjsembed stuff that has been becoming more and more important.

KJSEmbed can now handle events. At the moment only mouse events, but the rest will come soon. The example below shows how this can be used in practice. Note that I haven't committed this code yet, so it'll be a couple of days before you can use it.

I've just committed some basic support for enums to kjsembed. This means that enums published by QObjects using the Q_ENUM declaration can be used by scripts. At the moment, the constants are properties of the proxy object itself rather than the class, but the basics are there.

This means that scripts can now do things like:

     f = new QFrame();
     f.frameShape = f.WinPanel | f.Sunken;

instead of needing to use the int values of the enum. As you can see the enum constants can be or'd together just as they are in C++.

Lots of new features in KJSEmbed over the last few days. I got a new factory method implemented that lets you create read-only parts! This has let me knock together an example that uses KHTMLPart to provide a web browser - total code 22 lines (including blanks and comments). There is also now support for any QVariant type - even those that aren't explicitly suported.