Skip to main content

Lotus Foundations Start Training

Yesterday I attended an all day session on Lotus Foundations for both IBM Business Partner and Lotus Foundation Partners. Being both an IBM Business Partner and Lotus Foundation Partner, it was interesting to here the perspectives of Lotus Foundation Partners (formerly Nitix Partners) versus IBM Business Partners. From the perspective of an IBM Business Partner, Lotus Foundation is has limitations. As states it is not a Domino server, but a server powered by Domino. This will likely change in the future. The Web interface is been improved. There is still a lot of work ahead to competite against Microsoft. Lotus Foundation is a good starting point for IBM. There is a number of things that I would like to see added or changed. But that is me. For Business Partners that are interested, there is discussions about forming a Lotus Foundation User Group. If you are interested, please contact me and I can get you in touch with the person who is heading it up.
Labels:

Comments

Unknown said…
Hi

i found this blog as i was researching on training for Foundation Start.

i agree with you that lotus Foundation has a bright future, i would like to have the contact information for further info.

richoracle@gmail.com
November 25, 2008 at 10:43 AM
Anonymous said…
I also agree that lotus foundation has a bright future and this is really a ncie product from IBM.still it need much attention for improvment but its really a great solution....

QaiserJadoon@lmkr.com

I am also interested in Lotus Foundation Forum
January 13, 2009 at 9:29 AM
Post a Comment

Popular posts from this blog

The iPhora Journey - Part 8 - Flow-based Programming

After my last post in this series -- way back in September 2022, several things happened that prevented any further installments. First came CollabSphere 2022 and then CollabSphere 2023, and organizing international conferences can easily consume all of one's spare time. Throughout this same time period, our product development efforts continued at full speed and are just now coming to fruition, which means it is finally time to continue our blog series. So let's get started... As developers, most of us create applications through the conscious act of programming, either procedural, as many of us old-timers grew up with, or object-oriented, which we grudgingly had to admit was better. This is true whether we are using Java, LotusScript, C++ or Rust on Domino. (By the way, does anyone remember Pascal? When I was in school, I remember being told it was the language of the future, but for some reason it didn't seem to survive past the MTV era).  But in the last decade, there a
Post a Comment
Read more

Creating Twitter Bootstrap Widgets - Part II - Let's Assemble

Creating Twitter Bootstrap Widgets - Part I - Anatomy of a Widget Creating Twitter Bootstrap Widgets - Part II - Let's Assemble Creating Twitter Bootstrap Widgets - Part IIIA - Using Dojo To Bring It Together This is two part of my five part series "Creating Twitter Bootstrap Widgets".   As I mentioned in part one of this series, Twitter Bootstrap widgets are built from a collection standard HTML elements, styled, and programmed to function as a single unit. The goal of this series is to teach you how to create a Bootstrap widget that utilizes the Bootstrap CSS and Dojo. The use of Dojo with Bootstrap is very limited with the exception of Kevin Armstrong who did an incredible job with his Dojo Bootstrap, http://dojobootstrap.com. Our example is a combo box that we are building to replace the standard Bootstrap combo box. In part one, we built a widget that looks like a combo box but did not have a drop down menu associated with it to allow the user to make a select
Post a Comment
Read more

The iPhora Journey - Part 3 - Creating an Integrated UI Framework

The iPhora Journey - Part 1 - Reimagining Domino The iPhora Journey - Part 2 - Domino, the Little Engine that Could The iPhora Journey - Part 3 - Creating an Integrated UI Framework There are many ways to create the user interface (UI) for a web application. The HTML page could be created on the server and then pushed out. It could be static with the data generated on the page by the server with JavaScript, providing a more dynamic experience, or the server could generate new HTML content to update portions of the web page. XPages or PHP are good examples of this. Another method is to have the web page partially generated by the server and have JavaScript build the rest of the HTML by pulling data from the server via an API. This is the approach used in the Single Page Application (SPA) model. In all cases, it is still dependent on the web server technology being using.  As mentioned previously in this blog, XPages is dependent on complete integration between form and document, which e
Post a Comment
Read more