Wednesday 28 February 2007
Miscellany
Novell has generously granted permission to release Amber as open source. I need to choose a license and a place to host it. Currently I'm thinking GPL and Google Code. The GPL isn't too restrictive because applications talk to the query agent using a pipe, so a debugger frontend or whatever would not be required to be GPL.
I've been doing more wrestling with ATSUI to try to handle some tricky Hindi text. Hindi is basically left-to-right but sometimes a vowel that comes logically after a consonant is actually rendered to the left of the consonant. In this case ATSUI reorders the vowel visually which confuses our textrun infrastructure, because it depends on characters proceeding in a uniform direction. I'm dealing with this by fusing the reordered characters into a single atomic cluster. This is suboptimal, because you can't select part of the cluster or place the caret within the cluster, but it's probably good enough.
Beyond that, I've made considerable progress on the new textframe. It can now display many Web pages without crashing. I've also got textruns refactored so that all platform-specific code is isolated to gfxFont and gfxFontGroup implementations; most of the platform-specific code is code to use platform APIs to extract positioned glyph data, which is then stored in gfxTextRun (which is now the same code on all platforms). I've got Mac and Windows textrun setup implementations now too.
I'm going to be off work for a few days. Back at work on Monday, hopefully.
All four of us current and soon-to-be Gecko developers in Auckland met for lunch today. It was exciting!
Comments
At first I was mightily confused why it would be so important to get Hindi correctly rendered for Amber. A programmer certainly will be flexible enough to cope with a few UI inconsistencies. Until I've read the title of your blog post... :)
Seriously, why use a license that stops a whole class of people using and contributing back?
Given that Novell's being generous, I think it's fair to require some quid pro quo.
I'd think otherwise if this was code I expected people to want to use in a library, but I don't think that's going to happen.
BSD: You can use this code, even if you don't want to give anything back.
I don't see anything wrong with either license - let him pick whichever one he prefers. He is the one who wrote it, after all.
Matt: I wouldn't presume to tell someone what license they should use on their own work, unless, of course, they ask. And maybe I misunderstood ROC's post, but I read it as asking for feedback, which I offered.
It has the advantage that it maximizes cut-and-pastability of code, and although there is a risk someone can do something proprietary with it they still do it with the GPL, and unless you are willing to go to court there is no real difference.
Miguel
I read this article and have been searching for some way to contact you. I know that posting on your blog is a terrible way but it is my last resort!
Can you please email me: reception@orionhealth.com? I have someone who wants to meet with you.
Thanks,
Kate