My Blog has moved to gnome.org. Link: Marco Pesenti Gritti
I started phase 2 of my mozilla SDK fight. In other words I'm starting to identify and solve problems with the embedding API. Mozilla hackers seem to be interested in feedback and that's a good start. I like how mozilla 2.0 plans are shaping up, I think mozilla has a chance to become a very good development platform on the not too long time.
One positive aspect of working in two communities is that when you are sad about how things are going in one, you can feel better about progresses on the other side ;)
I think there are a few misconceptions that are stopping the Mono debate to be productive:
Energy can be ambivalent. It's without any doubt positive when it builds something, even incomplete or flawed. But it can also be disruptive. In which case you'd better try and control it.
Seth is expressing very well my (and I'm sure of a large part of the community) concerns about Mono. Sadly this looks already like yet another (de facto) fork of the free desktop strategy. I hope there is a way to recover but I wish we had this argument a while ago.
I landed a pair of mozilla embedding patches, and I'm waiting for another one to be checked in. The GRE work is almost complete. I guess I'll have to wait embed string/private string incompatibilities to be fixed though, even if I'm not experiencing problems on linux.
Integrating mozilla and GNOME printing is not as easy as I'd have hoped, mainly because there is not yet something like a GNOME print system (or at least something stable, that we are planning to keep supporting in the future). Though I think providing a generic, full featured, frontend that can work with multiple backends could be a good start.
I should get back hacking on Epiphany a bit more, I guess I'm just a bit demotivated and time lacking at the moment.
I'd like to give gcj a try, but I'm too lazy to bootstrap another jhbuild tree. I guess I'll just wait the whole thing to be merged in real jhbuild.
On a side note, I finally graduated, it was about time :P
My thesis discussion is near now (18 May) and I'm pretty busy organizing latest details, did not get much done in the last few days :/
The GRE work is progressing slowly but pieces are getting in place as I would like. In particular Darin will work on a fix to allow mixing nsEmbedString and private string in the same DSO. That means my GRE patch will not break mozilla static build (the hard part of mozilla development is to deal with multiple platforms and builds) and that we will be able to port epiphany code to use nsEmbedString gradually.
Had to setup a windows build of mozilla to be able to test nsComObsolete.h kill off. That was really not fun, it's so much easier to install a linux distribution with all the tools you need then setup cygwin/mingw.
I'm doing some very boring work to cleanup epiphany mozilla inclusions and separate public api, private api, api incompatible with embed string. We are actually doing better than I thought. We are not using that much private stuff and incompatibility with embed strings looks fixable. I think this will help me figuring out stuff we need to fix in mozilla SDK.
Got approval for another Mozilla SDK bug. I have not been able to get someone to check it in so far though :/ Mozilla patch lifecycle is somewhat bloaty. I need to bug 4 different people (r, sr, a, checkin) to get a patch in. Oh well I guess at some point I'll be a mozilla guru and I'll get a cvs account ;)
This really need to be fixed. You cant have to go through 3 different private interfaces to be able to attach mouse event listeners.
Argh, need to go to civil service now, I'm late as usual ...
Finally I've been able to post the gnome print integration plan bug. I think it's a great, concrete chance to work with mozilla developers on something that will affect both epiphany and firefox, let's not waste it ;)
Sorry, I really hope I'll find ways to be more useful :/
My fight with mozilla SDK continues. It's taking a lot of my time but I think it's necessary, it's not my favourite hack but someone must do it. So, since this has been the main topic of this blog lately I'm in debt of an explanation to my 3 readers. Gtkmozembed is a nice, simple widget that allows to embed mozilla renderer in GNOME applications. To be able to adopt it more widely in GNOME applications (see devhelp, yelp, evolution at least) we need to solve some issues:
I opened bug 140713 about this. Feel free to add notes there if you are interested. It's the first of the plan tracking bugs (man, I'm slow), I'm going to post one about gnome print integration ASAP.
Keep up with the latest Advogato features by reading the Advogato status blog.