Every so often something comes along that completely changes the way I use a computer. My new MacBook Pro has provided one of those: two finger scrolling. The concept is just so simple; to move the mouse you slide one finger across the track pad, to scroll you slide two fingers across the track pad. You can scroll vertically or horizontally so it beats a scroll wheel mouse hands down.

So for the record, if you have a textarea in Safari that is set to display: none; You can’t set it’s content via JavaScript unless you show it first. So:

edCanvas.style.display = "inline";
edCanvas.innerText = body;
edCanvas.style.display = "none";

Really annoying. For those Ephox people using the latest version of our EditLive! WordPress plugin in Safari, that’s where your content went. Pull an update from subversion soon and the issue should be fixed.

I’ve been in our San Mateo office the past week working with the sales and marketing folk which has been great, but also challenging and often frustrating. The challenge is in getting a grip on my new job as product manager, the frustrating from the initial objections we often get from clients as they try and guess what the reaction will be from their users instead of actually finding out. It’s fair enough, that’s all they have to go on but it’s frustrating to have to try and share the experiences that we’ve seen with users giving our software rave reviews. It’s also frustrating to hear negative things about software you’ve written – I always get so attached.

While most of the Ephox folk use EditLive! to edit their blog entries, there are some poor saps who are using a blog hosting service and can’t (we’ve got some interns working on a standalone blog editor with EditLive!, but that’ll take a while yet). This morning Antony learnt the value of a great editor the hard way when he copied and pasted from Microsoft Word into Typepad’s default editor:

Now I understand why so many of our users think our Microsoft Word filtering is so good…

I’ve spent the day doing some work with our Alfresco integration to make it easier to install and a bit more maintainable. Fortunately the Alfresco team were kind enough to point me at their Module Management Tool which while being a bit rough around the edges is really quite cool. Basically, it takes the alfresco.war and a zip file containing the module you want to install and shoves the module into the war file, ready to be deployed. What’s particularly cool is that it actually has version management so it knows if it’s previously installed a module or if the installed module is more recent than the one you’re installing etc.

I’ve been doing a lot of thinking lately about how to make wikis accessible to the common man – in other words, how do we get wikis to spread out of the technical departments and make it not just usable by non-technical people but make them actually want to use it and advocate it. Certainly there’s been a lot of movement in this area and a lot of good progress made, but I suspect there’s a lot more than can be done.

One of the things I’ve often found annoying about Brisbane, and to a degree Australia in general, is you just don’t get enough chance meet ups with interesting geeks. So since I’m over in San Francisco at the moment and Robert Scoble invited everyone and anyone to join Tom Conrad and him on the top floor of the Marriot hotel to watch the fireworks, I figured it was worth the walk.

Turns out that only a few people thought of that particular vantage point so when I got there Tom and Robert had secured the best seats in the house. Conversation was great, both Tom and Robert are very down to earth and easy to get on with. We were saved from getting too geeky by Robert inviting over a couple of girls who hadn’t secured good seats but it was good to see some of the stuff put in perspective and get a non-geeks view on things as well.

I mentioned that I was chatting to a reporter after the Java Libre panel yesterday. The article she wrote is now online and it’s a pretty good summary of the key points of interest in the discussion (it skips all the bits where everyone agreed in true reporter style though). I think she did a pretty good job of understanding what I was attempting to say (I elaborated more on that yesterday). We even got an actual link to ephox.com which is unusual.

There was an interesting panel discussion at JavaOne today about the open sourcing of Java. The panel was made up of folks developing open source JVMs and a representative from Sun. Compatibility is obviously a common theme to these discussions and there were a number of mentions to just how bug for bug compatible the alternative JVMs are trying to be. It occurs to me though that if all the implementations wind up behaving in precisely the same way, there’s not really any point to having multiple implementations. Yes multiple licenses are nice for particular niches but for the average Java developer, what’s the benefit?

The session was a lot more fluff than useful stuff and often went for showy graphics instead of actual usability which is a shame. There were some good ideas though.

• Use a modern L&F – they suggested Nimbus. Gosh it’s ugly and gray. I suggest using the system native L&F (except on Linux and Solaris then anything is an improvement)
• Add a splash screen, can do this with the -splash argument in Java 6.
  • Supports alpha transparency so can be non-rectangular
  • Should provide a progress bar.
    • They used a sepia image fading into color to show progress which looked cool but didn’t really show progress at all effectively.
• Validating Data
  • Give feedback immediately.
  • JGoodies can provide a small icon in the corner of the component. You can do this yourself by painting the icon in the layered pane’s popup layer.
• Custom Components
  • You can improve GUIs by creating custom components.
  • This is where they messed up usability in some places. Make sure your custom components are significantly easier to use than the standard components otherwise it’s better to go with what the user is used to. Also need to consider accessibility which they didn’t mention at all.
• Improve interactivity by updating search results immediately as the user changes values.
• Use cyclic gradients for improved performance, even if you don’t need the cyclic property (just paint one iteration).
• Measure text with:
  • g2.getFotnMetrics() then stringWidth and getAscent
• JList has a setLayoutOrientation method which lets you use it as a multicolumn list.
• You can span text across all the cells in a row by clipping the text with a JViewPort to show just the section inside the cell currently being painted.
• You can animate the changes made when sorting by painting the animation in the glass pane over where the table is.

These are my notes from the technical session, “Being Productive With Swing” by Ben Galbraith. The session focussed a lot on Ben’s library that he’s creating which was a shame but there are some ideas that are worth taking away.

The techniques described below are very specific to business applications that center around forms. At the moment desktop applications are “stepping up the wow” to compete with AJAX and Swing traditionally hasn’t had this – JavaFX is likely to bring this to Swing. However, for most business applications “wow” isn’t a requirement, productivity is. In that area, no emerging platform provides material advantages over Swing with the exception of JFace and Cocoa.

These are my notes from the talk on the Swing Application Framework (JSR296). This is probably my favorite technology I’ve seen at JavaOne so far. It’s not trying to be overly fancy but it solves a clear need in a very simple way.

Malcolm Davis also commented on it but wasn’t impressed. Personally I think he missed the point. Firstly Malcolm, yes Eclipse and NetBeans platforms have had basically all these features and far, far more for a while and that’s the problem. Using Eclipse or NetBeans as a base for a small or medium sized swing app is total overkill and the frameworks are huge and take ages to learn and configure for your needs. JSR296 is all about defining a really simple framework that gives you just the basics. If you need more you can either add on to it or go the whole hog with Eclipse or NetBeans. Malcolm suggested a few areas he thought it should also cover: