It seems that the update delivered yesterday by Apple has fixed the memory and hick-up problems I mentioned earlier. Today I have been able to just work with the manuscript without pulling my hair out in agony.
Though the jury is still out, I don’t see any strange behavior anymore in the activity monitor regarding pages. On with the book!
I just wrote about my troubles with Pages and trying to write for Wicket in Action. Apple support is really quick: my blog entry was not up for longer than 8 hours, and they apparently already have fixed it!
About Pages 3.0.1
This update primarily addresses issues with change tracking and performance.
I already figured it had to do with change tracking, as before we sent the documents to our editor, we had nothing to complain about performance. However, when we received our feedback, it came in a Word document that had change tracking on.
Installing the upgrade as we speak! Thanks to John Gruber for his update on Daring Fireball.
The new Pages in iWork’08 seems to have some uncomfortable bugs: it claims quite a lot of memory, hogs the CPU, and often freezes my whole OS X GUI. To put it mildly: I have to restart Pages several times a day to make it usable.
It looks like the memory management of Pages 3 is b0rked. While I’m typing this, Pages is trying to shut down (now for over a minute!). It is using one core of my CoreDuo, and about 70-80% of the time it is spending time in the kernel, increasing the real memory usage (now 471 MB).
The shutdown has now finished, in over 5 minutes!!! AAAARGH.
Kent Tong, a Tapestry committer (and PMC member) has gotten his feet wet using Wicket and has written a nice, in my opinion fair, blog entry on what he conceives to be the differences between Tapestry and Wicket.
A couple of months ago we stripped the portlet support from Wicket because there was no apparent need, and active expertise for it on our team. If you don’t eat the food yourself it is hard to support it, especially something big as portlets.
But since ApacheCon Europe, our trusted member Ate has stepped up and came up with a great plan for reintroducing portlet support in Wicket, and even make it much better than ever before!
Using Ate’s work you can now use Wicket pages directly as portlets in a portal container. Nothing special needs to be done! Kudos to Ate and Hippo for providing the support for portlets!
The support is now available in trunk, and will be part of 1.3′s beta 4 release, which should be imminent (this weekend?).
Update: See issues WICKET-647 and WICKET-658 for some preliminary documentation on how to create them portal compatible pages.