It has been a while since I blogged about the iText Office. The cable for the office LAN were placed on in April, but nothing was connected yet. We were waiting for the walls to dry and for the painters to come. This happened last week.
Yesterday, I attended BizCamp. In the morning I presented a "Double Bill". That is: two presentations in 20 minutes. I started with my Three things watching House MD has taught me about doing business blog, and I used the "... sometimes you might find you get what you need" quote as a bridge to my why you (don't?) need a VC presentation (I did the same talk at GentM, but now I could finally use my slides).
iText® XML Worker is no longer in beta. You can now start using XML Worker 1.0.0 in a production environment to create PDF files using HTML created using CKEditor or TinyMCE as input. We're simultaneously releasing iText 5.1.1 because XML Worker 1.0.0 depends on some new functionality that was added to iText.
For a full overview of what has changed, please consult the changelog.
Almost a month ago, I wrote Enforcing your Trademark: not that simple. I was complaining about the fact that somebody had claimed the @iText Twitter account, but hadn't been posting anything but absurd non sense (6 status updates on 3 different dates between November 8, 2007 and February 10, 2010).
Another month, another Google Analytics blogpost. Let's take a look at the Google heartbeat (this is the overview of the number of visits, not the number of hits):
Looks OK, doesn't it? No sign of the arrhytmia shown in the Alexa stats:
Did we have better results in May compared to (the slow month) April. the Alexa stats already gave away the answer: Yes!
A month ago, I wrote: I don't know what I'll read next, but I'll look for something entertaining. I found what I was looking for. Out of the 8 "books" I've read last month, 7 were graphic novels.
Yesterday, I filled out a survey that made me think about the period before iText. I was asked for my "failures" in the past. I wrote down two ideas that failed silently. Afterwards I remembered a third failure. I probably had more ideas that didn't make it, but these were the ones that were the most energy-consuming: