Nov 21, 2009

Reiser4 May Go For Mainline Inclusion In 2010

source... The Reiser4 file-system has been around since 2004 but has not reached a point of being close to be included in the mainline Linux kernel, especially after the lead developer, Hans Reiser, was convicted of murdering his wife. Development of Reiser4 has continued on, albeit with a very limited number of developers, and not nearly at the brisk pace of Btrfs or with great interest by corporate parties. The last TODO list update on the Reiser4 file-system was posted back in April with just five items un-addressed. In late July it was then shared by Edward Shishkin, a former employee of Hans Reiser's Namesys who has since effectively taken over work on Reiser4, that in the Autumn they would begin exploring the opportunity of getting this file-system in the mainline Linux kernel. In the United States, the end of Autumn is nearing and Winter is approaching, but there hasn't yet been any push to get Reiser4 into the mainline Linux kernel. What has happened? Well, we asked Shishkin. Before asking Linus to pull Reiser4 into the mainline Linux kernel, he first wants to publish a plug-in design document in a scholarly magazine in order to facilitate some independent expert review. After missing the deadline for FAST 2010, Shishkin is now hoping to publish this Reiser4 document for USENIX Annual 2010. This would be due in January, but their annual conference does not take place until June. After that, they can focus on finally getting this advanced Linux file-system into the mainline code-base. It's possible we could possibly see Reiser4 in the mainline Linux kernel in H2'2010. Assuming this all works out and Shishkin and the other developers go for inclusion shortly thereafter, it would put Reiser4 on the block around the Linux 2.6.36 time-frame.

Nov 16, 2009

Google Chrome OS To Launch Within A Week

source... Google’s Chrome OS project, first announced in July, will become available for download within a week, we’ve heard from a reliable source. Google previously said to expect an early version of the OS in the fall. What can we expect? Driver support will likely be a weak point. We’ve heard at various times that Google has a legion of engineers working on the not so glamorous task of building hardware drivers. And we’ve also heard conflicting rumors that Google is mostly relying on hardware manufacturers to create those drivers. Whatever the truth, and it’s likely in between, having a robust set of functioning drivers is extremely important to Chrome OS’s success. People will want to download this to whatever computer they use and have it just work. We expect Google will be careful with messaging around the launch, and endorse a small set of devices for installation. EEE PC netbooks, for example, may be one set of devices that Google will say are ready to use Chrome OS. There will likely be others as well, but don’t expect to be able to install it on whatever laptop or desktop machine you have from day one. Google has previously said they are working with Acer, Adobe, ASUS, Freescale, Hewlett-Packard, Lenovo, Qualcomm, Texas Instruments, and Toshiba on the project. We’ve seen convincing and not so convincing screenshots of Chrome OS over the last several months. The good news is the speculation is about to end, and you can try it out yourself. If you have one of the supported devices, that is.

Nov 3, 2009

SwingX 1.6 released

Just 5 months after the 1.0 release, SwingX team is pleased to announce yet another release. This release signifies the big step in the project. This releave version number signifies abandoning the compatibility with Java 5 and aligning the base line with the Java 6. The release contains bug fixes, introduces full Nimbus Look and Feel support and removes all dependencies on Java 5 related libraries and code changes.
Release notes: http://swinglabs.org/releases/1.6/ReleaseNotes.html

Nov 1, 2009

Metawidget 0.8 - 0.85 migration - trying ordeal you have to deal with

Metawidget 0.85 is released. A great work was done to improve architecture of this framework. Now API looks mature and straightforward. But backward compatibility is broken. Here is a list of main changes:
  • WidgetProcessors and refactored internal pipeline
  • Upgraded RichFaces support (SuggestionBox, TabPanel and RichPanel)
  • Upgraded ExtGWT support to 2.0.1 (includes new Slider widget)
  • Much more documentation
  • XML Schemas for all components
  • Bug fixes; and
  • More unit tests
The official migration guide: http://kennardconsulting.blogspot.com/2009/09/metawidget-08-to-085-migration-guide.html My migration experience: http://docs.google.com/View?id=dmsrn2h_210gsfkf2dm PS. Actually it was impossible to migrate my project to 0.85 version, I had to use patched one. PPS. Finally I have migrated my project to 0.85 release. Many thanks to Richard Kennard for support.