Thursday, 23 July 2009

Project Kangaroo (resurrected)

The news is now out - Arqiva have bought Project Kangaroo. The offical press release has all the details so I haven't really got any more to add other than to say my post before now looks a bit premature...

Monday, 13 July 2009

XHTML vs HTML in HTML v5

I was recently thinking of adding a XHTML mode library to ioko-tapestry-commons, but before I did I decided to check out the latest position on XHTML vs HTML with HTML 5. I was glad I did - as it appears the attempt to move to XML compliant markup on the web is being de-emphasised!
When XHTML was first introduced is seemed (maybe just to me) that is was aiming to replace HTML (which is quite hard to parse) with a more structured version (XHTML) but it has been an uphill struggle to produce valid XHTML.
It seems the W3C have recognised this and now recommend in most usages using plain HTML 5. I found an interesting write up of the notes that led to this decision. It does nicely clarify the situation, so now we can all stop worrying and just write plain HTML 5. Those people who love XML can still write XML versions of their pages - but as before they still won't render in IE properly (when the mime types are correctly set).

Friday, 10 July 2009

Nokia (finally) did something right

A while back I reviewed my Nokia 5800 and wasn't entirely happy. However I just found the new Nokia email client and have discovered something actually good about the phone!

The Nokia Messaging client works like a high quality push email client (I am pretty sure it isn't push but it behaves well). It fetches emails straight from my Google Applications account (all it asked was my email and password) and seems to synchronise perfectly.

This is the kind of thing Nokia need if they are going to complete with Apple and Android in the smart phone market. People won't put up with things not working easily.


Eclipse, Maven and Subversion

<rant>
I want to open projects from subversion, in Eclipse using Maven. Why is it so hard?

This used to work - once upon a time I could type
mvn eclipse:eclipse
and it all worked.

However in the new exciting world of Eclipse 3.5 I have to download Eclipse, Install one of TWO subversion plugins. One of TWO maven plugins OR use the command line method.

Why do I have to choose between two eclipse.org projects the do basically the same thing. Why does neither work on my projects that IntelliJ's maven integration has no problem with. Why doesn't mvn eclipse:eclipse work properly with web applications? Why does one of the eclipse.org maven plugins insist on the non eclipse.org subversion plugin?

I think I will go back to IntelliJ now.

I know the answer to all of the above questions - but it is extremely annoying. No wonder people call Java complex.
</rant>