I let it slide for too long but now, Barcode4J 2.0 is finally available. Since the last alpha release I’ve been able to fix a number of bugs in DataMatrix and PDF417. As a last-minute addition I’ve added support for the USPS Intelligent Mail Barcode of which you can see an example below.
There’s also a detailed list of changes for this release.
The Clematis on my balcony is in full bloom again. In the background, mount Pilatus still has a little bit of snow. But it’s getting less every day.
On days like today, it is really hard after a 5-minute break in Balconia to go back into the home office just because the notebook display isn’t bright enough to work outside. Sigh.
I’ve been to Amsterdam a number of times and will go there again for ApacheCon EU 2008. I always took the train or night train. So, nine days before departure I look again into the best way to get there and back. But despite all the discussions about CO2 and all that, something is still very wrong with the picture I have to paint…
Two days with buzzing activity. Interesting talks. Lots of FOSS projects presenting themselves. Free food, drinks and admission. On Wednesday evening Google sponsored a social event with food, drinks and lightning talks. LiSoG and /ch/open offered delicious cocktails under free license on Thursday. Ever present was the organic FreeBeer by project21 (it comes at a price but the recipe is under the Creative Commons License Attribution Share-Alike).
It’s unbelievable what these guys put together. Sometimes I had the impression that there was more interest in the OpenExpo than in the larger TopSoft that was held right beside the OpenExpo in the same hall.
For the ASF, Andreas Hartmann presented Lenya, Christian Geisert presented OfBiz and I FOP. On Thursday, I held a presentation on FOP and I was happy to have an almost full room. Many people indicated that they didn’t know FOP, yet. So, this was a really good opportunity to do a little promotion.
I had a nice long talk with Andreas Vox from the Scribus team about layout. It was interesting to learn how Scribus does line-breaking compared to FOP.
More photos should be available on the OpenExpo site shortly along with the presentations (videos plus slides).
I’ve got a 4 year old IBM ThinkPad X31 which served me very well. But it’s time now for a new notebook. I want something as small as my X31. It should be affordable but ideally have a better display. Yesterday, Lenovo announced the new ThinkPad X300. Hot!
Various open source projects will be represented at the OpenExpo in Berne (12./13. March 2008), among them the Apache projects FOP, Lenya and OfBiz. It’s a good opportunity to get in touch with people from the respective project teams and to learn more about the products. OpenExpo also offers various interesting presentations (mostly in German!) and much more. Entrance is free. Tickets can be ordered on the website. See you there…
I’ve just noticed an interesting coincidence: There will be will be a PDF/A conference next year in Amsterdam. The event will take place April 10th and 11th at the Hilton Hotel in Amsterdam. This is at the same time as ApacheCon EU 2008 which takes place at the Moevenpick Hotel in Amsterdam from April 7th to April 11th 2008.
I guess it would be interesting to present Apache FOP at the PDF/A conference. For FOP users this could also be a reason to come to Amsterdam in that week. To a certain degree you can probably combine catching up on PDF/A with interesting discussions with FOP developers. I don’t know, yet, but hopefully Vincent gets one of his session proposals on FOP accepted which would be one more reason for FOP users to come to Amsterdam.
The first release (0.90alpha1) coming out of FOP’s redesign effort is exactly two years old today!
Between 2003-07-18 and 2005-11-22 (for more than two years), there was no release of Apache FOP. Many believed the project was dead. No wonder: the majority of the project team back then gradually went away for various reasons. There was no consensus about how the project should be continued. The “maintenance branch” constantly competed for attention with the necessary redesign effort which was started back in late 2001. The XSL standard lost its “new and shiny” status at some point which obviously didn’t help attracting a lot of creative minds with a lot of free time at their hands.
Today, XSL is a mature, if complex, technology which is widely adopted and treated as a commodity taken for granted. At least that’s often my impression. I mean, if we look at the size of the user base of Apache FOP compared to the number of the active committers, the difference is huge. Still, I’m very happy that we’ve been able to attract a sizeable group of new committers to Apache FOP once again over time.
From a personal perspective, it’s so good to see various companies and even some government institutions investing in FOP. Of course, the whole open source movement is still gaining momentum which helps here. Nowadays, I can even make my living by doing freelance work almost exclusively in the Apache XML Graphics ecosystem. My clients, in turn, get added value in various forms: new features, bugfixes, professional support with good reaction times, no vendor lock-in (independance from a single commercial provider), full access to the source code, sharing of development costs, no licensing costs etc. That’s a win-win situation for everyone involved.
I’m looking forward to the time ahead. There are still many things to do. One of the most important ones: Still not having jumped over the version 1.0 barrier harms the project: some companies don’t adopt 0.x software and others won’t invest in it. I hope we can finally, finally fix that in 2008, almost ten years after the XSL standard was started. And FOP was actually the first implementation of XSL-FO available.
The title says it all. I was quite surprised when I was approached last month. Reminds me to find time for the final 2.0 release…
Here’s the Project of the Month page.
Last week, we’ve conducted a user poll to get hard data for a decision to drop support for Java 1.3 for the Apache XML Graphics project (Batik & FOP). The results are quite clear: we’re safe to drop support for Java 1.3. That’s good news since it helps us concentrate on more important aspects of the project. The survey also revealed how many people are still on Java 1.4 and how many are already using Java 6.
We will now have to take a closer look at the question, if we should directly skip to Java 1.5 as some suggested. Personally, I’m a little hesitant, since I know a lot of people who are still stuck with Java 1.4 for the moment. They all want to migrate to at least 1.5, of course, but that requires careful preparation in complex environments. Better stick to Java 1.4 until at least summer 2008 when the end-of-life process at Sun ends for Java 1.4.