Older blog entries for lkcl (starting at number 634)

russell sent a link to a self-tests autism / asperger's test, with associated warning. decided to give it a shot:

  • Autism Spectrum quotient: 21 (high-end of "average". nothing significant here, for me, then)
  • Systemizing quotient: 47 (ASP-indicative)
  • Empathy Quotient: 20 (most people with Asperger Syndrome or high-functioning autism score about 20)
  • Reading the mind in the eyes: 33 (30-36 very accurate)

that's fascinating. dreadful empathy quotient, but very high ability to determine people's emotional state (mind-in-the-eyes).

such a pity that bloody internet communication (free software development) isn't usually usually face-to-face.

hm. anyone else gonna give this a try? :)

pyjamas credits file

pyjamas has some _fantastic_ names of people who've contributed to it on it :)


2006-2007: James Tauber 
2008-2009: Luke Kenneth Casson Leighton 


Other Commmitters

Willie Gollino - wgollino@yahoo.com Dobes Vandermeer - dobesv@gmail.com Bernd Dorn - <bernd.dorn@lovelysystems.com> Luis Pamirez Erik Westra Jurgen Kartnaller

Other Contributors

Vicente J. Ruiz Jurado Gerard Labadie Stephan Diehl John Lehman G Clinch Kees Boss Oisin Mulvihill Ondrej Certik Laszlo Krekacs Stefan Schwarzer Radoslav Kirov Beni Kerniavsky Henk Punt Mathias Waack Guenter Walser Martin Blais Scott Graham Nick Hackadelic Catalin Patulea JJ Kunce Alexei Sokolov Carl Roach Yit Choong Sujan Shakya Klavdij Voncina Scott Koranda Phil Hands

it's like an international hall of unpronounceable fame. i love it. i'm trying to encourage other people with more syllables than vowels to contribute - anything, even if it's a single docstring line...

Open Smartphone Projects

All the while I've been bitching about how there are no open phone projects, it turns out that there are at least three:

this latter one gives a complete set of schematics and bill of materials, all GPL licensed.

i'm amazed. it ranks somewhere in the fishpond scum league when you search for "open mobile phone" or other keywords. i only accidentally encountered it when searching for the part-number "ew-wmbgmr01" of a CF WIFI/Bluetooth module!

strategy.wikimedia.org

i accidentally stumbled onto strategy.wikimedia.org recently, and decided to have a go at writing a couple of proposals. one is the distributed wikipedia proposal, in which, it should come as no surprise that it's the exact same idea as recommended in the arse-kicking article.

actually, the other proposal was originally part of the same one, but it became clear that i was basically talking about the wikipedia "API" which is primarily used by "bots". so, i morphed it into a proposal "extend wikipedia API to cover everything that the current HTTP interface can do, please" proposal.

where it all goes horribly wrong

then, i accidentally encountered some proposals that start talking about putting binary blobs into wikipedia pages (wtf??) and my alarm bells went off the scale. there are three that i've found so far, and they're proposing that wikipedia allow java and flash.

i cannot begin to describe how much of an insanely bad idea these are. from every possible angle imaginable, the risks and costs massively outweigh the marginable benefits, and whereever there is a marginable benefit, there are alternative ideas which do the job in a safer way.

at the core of these proposals is that it is more beneficial to be able to write animations into wikipedia pages, to enhance and augment the text and the information being presented.

where the proposals go wrong is that they then advocate that the use of a full-blown programming language, along with browser plugins necessary to run the resultant binary blobs, is a good idea.

the sheer cost to end-users to learn these programming languages, along with the necessary english language skills and the mindset required to be capable of doing programming, is utterly prohibitive. end-users have enough difficulty with the concept of "wiki markup", let alone a full-blown programming language.

advocates of these proposals are finally admitting "that's okay - end-users aren't expected to contribute to these pages (written in java or flash) anyway, so we don't have to care about them".

this is in direct contravention of the goals of wikipedia, and is completely against the whole purpose of the wikimedia strategy process.

exactly why the advocates of these proposals still cannot get this, even though i've been pointing it out to them in a dozen different ways, i really don't understand.

but - i am persisting with explaining it to them because the risk is that their proposals are accepted. i cannot find the words to describe how much of an incredibly bad idea that would be.

MSHTML and IE port of GWTCanvas to pyjamas

works a treat, which is an amazing surprise. the GWTCanvas API basically maps near-direct to SVG, to support all browsers but IE, and then does this weird string-creation trick using the VML namespace, for IE.

what stunned me is that the port of GWTCanvas also works under pyjamas-desktop as well. again, elements using the VML namespace get added (using the COM interface) and it's all hunky-dory.

very cool.

MSHTML port for pyjamas - works!

HA! i contacted the IE team through their blog page - for a couple of reasons. one was to say how genuinely impressed i am with Trident (the engine behind MSHTML). the second was to complain (not really) about the lack of keyboard support for tab and keyup and keydown.

it turns out that you can - i.e. have to - query the TranslateMessage COM interface of the ole object, and use it to perform translations of the windows system key messages into the appropriate key events. WM_SYSKEYUP -> WM_KEYUP or something like that.

anyway, after adding in a bit of quirky code, in probably a wildly inappropriate fashion, the whole thing now works! YAY!

Pyjamas port of GWTCanvas

well, as part of GChart, for a massive performance gain it's really necessary to use SVG Canvas. rather than mess with the design of GChart, i started porting GWTCanvas to pyjamas.

demo here. works in FF, probably safari/webkit/chrome, definitely not IE yet.

jeeezus - GWTCanvas contains an SVG-to-VML translator, to support IE!

WHA-HEY! i found the two bugs i was looking for, in the pyjamas port of GChart. pie-charts now work! there are now 14 examples and 4 tests.

30 Aug 2009 (updated 30 Aug 2009 at 21:22 UTC) »
GChart Pyjamas Demo!

ippee, after working with pyjamas-desktop for three days, getting pyjs to take the same python code and compile it to javascript was a matter of about 20 minutes, to fix three bugs that i should have known about (unsupported syntax of the pyjamas compiler) and two that i didn't.

FF2 is _dreadfully_ slow, beyond reason (but webkit is acceptable, so - whew!). it's essential that i get gwt-canvas ported to pyjamas, soooon. not that that may help, much, in some cases. we'll see...

but - waah! i'm just... surprised and delighted at the progress and the results, and i have _no_ real clue as to why i started porting GChart in the first place!

625 older entries...

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!