Wednesday, August 10, 2011

IBM Connections vs Microsoft Sharepoint 2010



A colleague of mine attended a Sharepoint semiar eariler this year. Microsoft representatives there admitted that Microsoft Sharepoint lacks features you would expect from a social software platform. But the promise was that this will be better in Microsoft Sharepoint 2010.

To my knowledge Sharepoint 2010 does not deliver. This is based on what I've learned from the 'File' module in Sharepoint 2010 (My Site - >My Content -> ). In comparison to IBM Connections 3.0 Sharepoints fails on several points:

  • MS Sharepoint 2010 uses a silo architecure and is file centric.
  • There is no listing of all documents shared with me (the logged on user).
  • There is no listing of all public documents I (the logged on user) have access to.
  • There is no easy way to share a document from "Personal Docs" to "Shared Docs".
  • There is not Social metadata around documents like, who are interested in the document, is the document recommended, has it been download, who has recommended or downloaded it, and discussion around the document is missing.
  • Users are unable to se each others tags and notes.
  • Not easy to navigate to Sharepoint homescreen.
  • Fileupload controls offers not functions to add social data.
  • There is not filtering capabilies to search for files.
These are some of the issues with Sharepoint 2010 that is brought to my attention.
The fact that there are few social metadata types assosiated with documents, and the types of data you can attach is not visible to others is a big fail. So also the fact that for documents there is not a menu item in SharePoint that says "Share" (You have 'Permissions Tools' though).

I could go on an elaborate more on these shortcomings, but I'll think the above list is enough to convey the message: Microsoft Sharepoint 2010 does not live up to the standards of a Social Software Platform.

You are welcome to prove me wrong on the issues I mention, or list other shortcomings of MS Sharepoint 2010.






Wednesday, May 11, 2011

Windows 7 security is bad for Lotus Add-ons




Having av new laptop with Microsfot Windows 7, I wanted to follow software recommended settings when installing IBM Lotus Notes 8.5.2. This was a mistake.



When starting the installation the suggested paths are C:\ Program Files(x86)\IBM\Lotus\Notes and C:\Program Files (x869\IBM\Lotus\Notes\Data.



This works fine, and I used my client for a week now.



But then came the need for Teamstudio Script Browser 3.0. Trying to installed it failed.


The installation program does not have access to the Program Files (x86) folder.



I did not try NotesHound or any other programs that wants to copy dll files into the Lotus Notes Program directory, or editing the notes.ini for that matter.



Trying to run the Lotus Notes client as administrator, and then run Teamstudio Script Browser, but no avail.



So my only option wa to uninstall, and reinstall the Lotus Notes client, outside the Program Files (x86) this time.



Newer software may very well handle this security feature in Microsoft Windows 7 but just be be on the save side, and to be able to use older but good software that hooks in to the Lotus, Notes Client stay clear of the Program Files (x86) folder.




You have been warned.

Thursday, May 05, 2011

The Best Tool I use!!



The best tool for Lotus Notes Delevopment is Openlog logging application.

Why? It's a real timesaver. The ease of use and the accurate information it provides is really helpful when debugging applications.

I hardly ever use "Tools ->Debug Lotusscript" these days. I just pop in the OpenLogFunction script library, and enter statements to log event or and error.

When and error occurs, or I want to check what path my code takes in if, case or any other flow control statements, I can use a function called LogEvent.

The real power is the log documents the application creates. You get user infomation, user access levels, call stack, line where error occurs etc. You can even provide a document link for the a document you want to inspect when an event is logged or an error for that matter.

Any Lotus Notes developer should check out this application, and start using it when developing, and debugging.

Saturday, April 16, 2011

Mastering Xpages

Last friday I got the book "Mastering Xpages" This is going to be very good stuff I hope.
The reviews are great. Just browsing thru the pages the books seems promising. This book can also be used by anyone not familiar with Lotus Domino Designer or the IBM Lotus Domino document-centric data model.

I'we worked my way thru chapter 3 and moving forward. Beeing qurious about the history of Xpages and it's Java Server Faces origin, I'm now on Chapter 5.

Ed Brill has says something about this book on his blog.

Also xpages.tv is a good resource for quick show and tell instructions.

Go buy the book.