Software Development

Building your intranet is like using a recipe. You want to make the final product enjoyable, and to do so, you need to ensure that all of the ingredients are well balanced.

I recently made a delicious dinner for some friends and was later asked how I did it. I slyly said “a little this and that”, but really, it is a tried and true recipe from my step mom, a chef. Over the years I have perfected the dish to make it “my own”, but I still have to peak back at my food stained recipe book to ensure that I am on the right track. With an intranet, similar to cooking a nice meal, users do not see the creative process until it’s perfected and delivered.  Like a good meal, and as the site develops, the users will crave more. 

Intranet design is similar to cooking in that it allows for revisions along the way. An intranet site starts with design applications that provide functionality to the site. You need to build up these applications with text, borders, pictures, in order to make the site operational and appealing to the user’s eyes. Along the way, you can add or remove icons, text boxes and documents to enhance the page. It’s a never ending process of exciting changes that increasingly make the intranet more accessible for the users.

The Tiki Community recently completed TikiFest Boston, the seventh code sprint in Boston. More than 20 community met to plan, discuss, and demonstrate Tiki Wiki CMS Groupware. Many of the new features included in Tiki 7 were demonstrated, including:

• Unified Search (based on Lucene)
• Tiki-powered web sites on mobile devices, using jQuery Mobile
• theme generator

Extensive work began on the revamp of Tiki Trackers -- a Tiki feature that allows users to create interactive forms and searchable datasets. Tiki 7 will include reorganized and streamlined code, allowing for easier enhancements in the future. Several TikiFesters also participated in a documentation sprint, in an effort to make the Tiki Docs more user-friendly and "catch up" to the current development.

The TikiFesters also joined the Boston jQuery Meet-up group. The event, "Tiki Wiki CMS Groupware and jQuery: the story of a successful integration," featured talks by Nelson Ko and Jonny Bradley. Ko and Bradley provided an overview of Tiki to the group and explained (and demoed) the jQuery integration that will be available in Tiki 7.

DotNetNuke Corp., the company behind the most widely adopted Web Content Management Platform for Microsoft .NET, announced its intention to shift the primary core development language for its award-winning DotNetNuke core platform from Visual Basic (VB.NET) to C#. The first official release of the DotNetNuke platform available in C# will be Version 6.0 which will be publicly available for users of the DotNetNuke Community, Professional, and Enterprise Editions in Q2 2011, with the first Community Technology Preview available in early March.

News Highlights

• In recent years there has been a much greater emphasis on the C# language in the .NET ecosystem in terms of innovation, tooling, and examples. In switching to C#, DotNetNuke Corporation believes its developer community and install base will benefit from greater access to development resources, source code examples, and enterprise acceptance.
• A Community Technology Preview will be available in early March which will provide the opportunity for users and developers to get early access to the recently converted C# platform. Community participation and feedback will play a vital role in ensuring a high quality final release. 
• The .NET Framework provides design-time, compile-time, and run-time support for multiple programming languages. As a result, the DotNetNuke API will preserve full compatibility through this transition. This means that all platform extensions will continue to be fully compatible with the C# DotNetNuke 6.0 core. 
• DotNetNuke extensions developers, commercial or otherwise, will not be negatively impacted by the change as they will continue to be able to develop and deploy custom extensions in their preferred software development language including VB.NET or C#.
• DotNetNuke is the fastest growingopen source web CMS ever on .NET with over 1,100 subscription customers, 33,000 Snowcovered customers, 400 percent year-over-year growth, and more than 600,000 production web sites worldwide. Connect with us online: Twitter.com/dnncorp(company) or Twitter.com/dnnsc(Snowcovered marketplace); DotNetNuke blogs; and the DotNetNuke Community LinkedIn Group.

“As a long-time Visual Basic developer, I have personally witnessed the gradual shift in the .NET developer market as C# has become the dominant choice for the enterprise," said Shaun Walker, Co-founder and Chief Technology Officer of DotNetNuke Corp. "After extensive technical and business analysis, I believe the time is right for DotNetNuke to make the move to C#. I believe this migration will accelerate the adoption and deployment of the DotNetNuke Web Content Management Platform and make our product more attractive to a wider audience.”

The SilverStripe open source community recently posted their roadmap to SilverStripe CMS v3.0. Version 3.0 represents a major year-long development project and is expected to be a substantial improvement over the current v2.4.x series. With an aggressive schedule, a stable version of SilverStripe CMS v3.0 is expected to be available by the end of 2011.

The roadmap introduces three major goals of SilverStripe CMS v3.0:

• Better technical platform. Sapphire, the underlying programming framework, will evolve from an integral part of SilverStripe CMS, into a product that can stand on its own feet. In forming this delineation, improvements will be made throughout the core, including the ORM, data integrity, templating language, and performance. Sapphire v3.0 will consequently enable developers to make richer and more complex web applications and websites.
• Better user experience for content authors. A refresh of the content authoring environment will bring even better usability and productivity. The interface will transition to jQuery, making the system capable of much greater customization. Managing images, embedding videos, and previewing work in progress will all be made easier. Images and documents will be able to versioned and secured in the same way pages can currently be.
• Improved support for the social and mobile web. SilverStripe's existing templating language and support for web services already provide a foundation for the two top themes in the web currently: social media and mobile devices. With SilverStripe CMS v3.0, the developers intend to improve the core to make development for both easier and richer.

SilverStripe's Business Relationship Manager, Sigurd Magnusson, sent CMS Report an email about this new roadmap for version 3.0 and how developers can help get involved. "Note at this stage", said Magnusson, "the main thing we want people to do, is join our development mailing list so they people can be involved in the decisions and contribute to the development of this new major release, due late 2011". The official mailing list for the development of SilverStripe CMS 3.0 can be found at Google Groups.

Those interested in additional information regarding SilverStripe CMS v3.0 are encouraged to take a look at the SilverStripe 3.0 Planning page. A video recording of the  first public presentation on SilverStripe CMS v3.0 is posted below the fold and slides from the meeting are also available.

Today the easiest way to create a website and take care of its management is using a CMS. Nowadays the challenge is extremely competitive for HTML CMS like Joomla, Drupal, WordPress etc... But if you want create something different, in graphics and behaviours, something that only Flash and its stunning graphical effects can do, the outlook is a desert landscape.

Last fall, I once again had the privilege of participating as a member of the judging panel for Packt Publishing's Open Source Awards. For the 2010 event, I participated by voting for the category of Open Source CMS Awards. In that award, the winner was declared by the panel to be CMS Made Simple, with SilverStripe as first runner up followed by MODx as second runner up.

I received a lot of inquiries asking me how and in what order did I rank the content management systems. Each of the judges on the panel, selects and ranks their top three CMS from the five included in this category. The judges are given a lot of reign for how they rank the CMS and may consider a number of factors including performance, usability, size and support from community, accessibility, ease of configuration, customization, scalability and security.

It has been my history to be transparent to all with how I rank each CMS as my vote will have some differences to those of the panel. This time around, I find myself hesitant and under personal protest with me providing information on how I ranked the five content management systems.

I question whether we're doing any good by declaring one CMS as better than another CMS. Dean Barker discussed on his blog some time ago this same uneasy feeling you get when you judge a CMS without having some reference to real world requirements. None of these content management systems would I consider losers and all of them remain worthy of future consideration. Yet, I'm disturbed that people will look at the numbers and interpret the results in a ways I never intended my rankings to be used.

My rankings for the Five Best Open Source CMS (with number one being the highest) were:

1. SilverStripe
2. mojoPortal
3. MODx
4. XOOPS and CMS Made Simple (Tie)

I'm not a firm believer in ties when it comes to ranking content management systems. Yet, this year I did just that for XOOPS and CMS Made Simple. All five content management systems that were reviewed I would consider as a candidate for a future project. None of the CMS would I consider a "last place" CMS so I refused to do so. It is also important to note that neither Drupal, Joomla!, or WordPress competed in this ranking as previous winners in this category duke it out in the Hall of Fame category.

Intersoft Solutions today announced the official release of WebUI Studio® 2010 R2, the world’s most advanced presentation layer toolset for ASP.NET, Silverlight and WPF application development. Featuring over 60 new rich controls for Silverlight and WPF platform, and dozens of new business-inspiring samples, developers can now rapidly build cross-platform applications with the next-generation user experiences, while at the same time leveraging the best practice in architectural design pattern.

With the new R2 release, WebUI Studio® delivers a total of 280 high quality UI components for ASP.NET, Silverlight and WPF development, setting its position as the world’s most comprehensive user interface library suite available today.

After three years of open source development, Drupal 7 has finally been released to the public. As Ric Shreves previously mentioned in his article, there are literally hundreds of changes in Drupal 7. I've included below a list of the more significant changes from Drupal 6 to Drupal 7. I've also included a nice Drupal 7 marketing video via Jeff Robbins at the bottom of this post. Also there is always official Drupal 7 announcement for additional information on this latest version of Drupal.

Barring any unforseen changes to how I manage this site, I expect we will be upgrading CMSReport.com from Drupal 6 to Drupal 7 within the next few months. I've been playing with Drupal 7 off and on this past year, but I must confess I haven't been as aggressive in my testing of this version of Drupal as I was with Drupal 6.

Some of the more significant changes in Drupal 7 since the release of Drupal 6 include:

1. Overhaul of the User Interface

Work has been done to improve the user experience and administration interface. The new administration theme "Seven", the overlay module, the dashboard and the configurable shortcut bar, all lead to a much more user-friendly interface.

2. Custom Fields

Drupal 7 bundles in the ability to add custom fields, similar in functionality to the Content Construction Kit (CCK) module. However, fields are no longer limited only to content types; they can be added to users, taxonomy terms, and other entities. Fields also have support for translations.

3. Image Handling

Drupal 7 brings native image handling to core. Image fields may be added to content, and have image styles applied to them, such as scaling, cropping, and other effects.

We are very pleased to present you X3, the new Xoops Engine for the next generation of XOOPS powered web application development.

This new Xoops Engine was long time in coming. During that time, we went through different phases of trials and errors, but we believe that we finally have the best combination of features and technologies to strategically position XOOPS as one of the top Web Application Platform solutions.

The new Xoops Engine has been re-designed from the ground up to take advantages of third-party frameworks like Zend Framework and Smarty 3.

Why did we rewrite XOOPS?

XOOPS is one of the most successful Open Source CMS and portal solutions, constantly placing in top places in various competitions, and receiving various awards. But it is showing signs of aging, that would require major rewrites of the Core.

In order to keep us focused on creating a flexible and extensible development engine for developers and a high performance application platform for end users, the development team has decided to use industry-standard frameworks. By doing so, we can focus our limited resources on aspects that make XOOPS unique and special, while leaving standard functionality to be addressed by off-the-shelf frameworks. This way we can take advantage of latest internet developments already included in those frameworks - it's like getting suddenly a whole new team of some of the best and brightest PHP and RIA programmers joining XOOPS!

After much research, we've selected a couple of frameworks at this stage:

PHP: Zend Framework
Template: Smarty 3
JavaScript: jQuery

Meanwhile the multi-engine mechanism of the Xoops Engine will ensure the possibility of adopting other excellent frameworks in the future, like Yii Framework, Dojo Toolkit, etc.

A few days ago, I read Mary Jo Foley's article titled Microsoft: Our strategy with Silverlight has shifted. According to an interview with the President of the Server and Tools Division at Microsoft, the company will be shifting support for Silverlight away from the PC and Mac desktop and toward the phone market.

So what’s a developer to make of Microsoft’s messaging (or lack thereof) about Silverlight at its premiere developer conference?

I asked Bob Muglia, the Microsoft President in charge of the company’s server and tools business, that very question and got what I consider to be the clearest answer yet about how Microsoft is evolving its Silverlight strategy.

“Silverlight is our development platform for Windows Phone,” he said. Silverlight also has some “sweet spots” in media and line-of-business applications, he said.

But when it comes to touting Silverlight as Microsoft’s vehicle for delivering a cross-platform runtime, “our strategy has shifted,” Muglia told me.

Microsoft plans to be using HTML 5 to replace the functions currently being provided by Silverlight 5.

It is not the point of this post to debate the merits of HTML 5, Silverlight and even Flash. What is my point though, is that Microsoft appears to me to be desperate. Desperate to come up with a strategic plan that will carry them beyond the day of Windows PCs. Microsoft is desperate to become innovative for the sake of innovation that they're really confusing a lot of their developers. If only after a few years of support, Microsoft is shifting focus of it's Silverlight platform...what potential developer in his or her right mind would support another future Microsoft endeavor? Just take a look at the comments to Bob Muglia's blog post discussing this topic and I think you'll see my point.