Believe it or not, but the first time I tried the Opera Web browser was a month ago. Until recently, I was content in calling Mozilla's Firefox the alternative browser. Opera 9 is now out and contains a wide range of features. Some of the features unique to Opera and not provided by Internet Explorer and Firefox includes BitTorrent built into the browser and Site Preferences. Site preferences allows you to accept cookies and pop-ups according to specific sites you're visiting (as opposed to settings for all sites you visit with the browser).
I thought eweek did a decent review of the product. The following are some of the things they had to say about Opera 9 in their article:
In our tests, we found Opera 9 to be one of the best Web browsing tools we've used in a long time, which is why we are giving Opera 9 an eWEEK Labs Analyst's Choice award.
I find it very odd that the release of a two-button wireless mouse makes headlines in the tech world. Is this not 2006? The press is once again headlining the release by Apple of a two-button mouse for the Mac. I tip my hat off to Apple not for product this time, but for marketing. Our quote of the week:
"We cut the cord on our popular Mighty Mouse to give consumers more flexibility when using a Mac," said David Moody, vice president of Apple's worldwide Mac product marketing team, in a prepared statement. "A Bluetooth-enabled Mac desktop with an Apple wireless keyboard and Mighty Mouse is the ideal cable-free setup at home or in the office."
A sleepless night for Earl Miles late last week provided the Drupal community a replacement to his Dashboard module. Earl Miles announced a successor to Dashboard at his site, Angry Donuts. The new module is the Panels module and I expect we'll be seeing it used a lot by Drupal's users, especially newcomers of Drupal and those less inclined to dig into the PHP code.
Dashboard the previous module, allowed Drupal developers an easy way to implement "simple" two-column layouts of content (called nodes in Drupal) that are not sidebars. While you can put blocks about anywhere in Drupal, the core doesn't offer an easy way to put content outside the "main body". While dashboard overcame the "single column" for content obstacle, it required knowledge of PHP to implement.
A couple days ago I opened my Thunderbird e-mail client on my Windows XP system and found an e-mail from Joe Audette of the mojoPortal project. "Mojo whata?", I asked. I thought I knew most of the content management projects (CMS) projects around, but this one didn't ring a bell. After reading his e-mail, I understood I likely have not heard much about his project because my focus on CMS has been a little too narrow lately.
In his e-mail, Audette writes, "Hi, just wondering if you only cover CMS's using php technology or if you would consider giving any press to .NET/Mono based projects? Any coverage of my project mojoPortal would be much appreciated."
As I've mentioned in past posts, I have a strong desire to cover more than just PHP Web applications. mojoPortal, named after Audette's dog, is written in C# and runs under ASP.NET on Windows or under mono on Linux or Mac. Already the talk of a CMS using a blend of Microsoft and open source tools was peaking my interest.
Gallery has a new demo site for users to show off their photo sites using the online application. The new demo site provides a significant improvement over the previous forum to showcase albums. Some information on the new site by Gallery themselves found below:
We have launched a new showcase album of Gallery 2 Demo Sites. There are many great Gallery 2 sites out there with a huge variety of themes, modules, customizations and embedded environments that we want you to see! This new feature of our website is powered by Gallery 2 using the Link Items, Rating, New Items modules, and a custom module with the submission form for new entries. The album shows newly submitted items first and is then sorted by rating.
Does Drupal make the grade? The answer to that question evidently depends on who you ask. Last week, the Tech Republic posted a review by Justin James on the Drupal content management system. Mr. James concluded that "Overall, Drupal does not make the grade". This week the Drupal community is all a buzz over the decision for IBM's developerWorks to use Drupal for designing, developing, and deploying a collaborative Website.
Why is there such a disparity in viewpoints for using Drupal in content management? For many first time users of Drupal, Drupal doesn't leave them with a very good first impression. It's only after you spend some time with Drupal that you begin to discover it has a number of traits that make it an outstanding application to build your website around. While Drupal doesn't give you a good first impression, it will eventually give you a second or third good impression.
Mozilla's Mitchell Baker wrote an interesting post about product development. As you develop a product and customer loyalty there is a risk to making too many changes to a product. However, the success of your product likely came about because of innovation. If you kill off introducing new ideas and concepts for your product you are also likely to kill off the reason your product became successful in the first place.
One of the issues I see regarding our products is the tension between being cautious about changing our products on the one hand and trying to innovate on the other. There are good reasons for this tension, since each perspectives represents part of our current reality. There are a number of reasons to be cautious...
She then explains the need to introduce some Mozilla "Prototypes" with features that could later be brought back into the Firefox browser (and Thunderbird e-mail client). You can read the complete article at: Mitchell Baker: Mozilla "Prototypes".
So far I've mostly posted here at CMS Report about PHP-based content management systems. However, PHP isn't the only language being used on the Web. Other Web friendly languages include Perl, Java, Ruby, ASP, Python, etc.
So for one of our first non-PHP based CMS we're going to take a look at Radiant. The Radiant CMS is a Ruby on Rails CMS that has yet to reach version 1.0. Like a lot of CMS in early development it is considered a "no fluff" CMS for small teams. In other words, Radiant is not quite ready for enterprise level work. Radiant however may work well for those personal sites and small companies that have an invested interest to promote Ruby on Rails based applications.
Current features of Radiant, according to its home Website, include: