UPDATE: Since this was posted they have released a another version (8.01) that includes some of the things talked about here.

Several weeks back I wrote about the content management system Ektron, in a post titled Hacking a Better Ektron.  When I wrote that I was generally speaking towards issues with the product that are defects or weaknesses. I had more thoughts that I wanted to speak to that are more the 10,000 foot view rather than individual problems which there are many.

With that said, I am sure this and the other post will come across as just beating on Ektron and CMS400 as an unhappy client, however my intent is not that.  Rather it is the continuous improvement of the product as I think it is a pretty powerful product despite it's misgivings.  I have for the most part enjoyed working with the product and think it could be a whole lot more.

More...

In 2008 my workplace jumped into the world of Ektron and embarked on a year long implementation of the product.  Having now dealt with it for nearly 2 years, I think I have a pretty good perspective on the product and what it does well and not so well.

Although I have no really beef against the company, or it’s employees this review may come off pretty scathing.  Really that’s because I hold them to a pretty high standard.  Why?  Well first of all, it’s not a cheap software.  It’s an enterprise level software package, and if you are going to to do business with the big boys of the world, then I expect certain things from you.

More...

When it comes to Palm’s WebOS, something I have been struggling with for months is trying to re-style the default input boxes that Palm uses.  Up until now few if any apps have tried to alter the default Palm text field elements. 

Re-styling the text field element is made difficult not only because it’s really difficult and time consuming to use the inspector, but also because of how Palm implemented their text fields.

More...