Moving from Notes Client to iNotes Client

Over the past few months for one reason or another, I have been accessing our email more and more using the iNotes 8.51 client instead of the regular Lotus Notes client. From my experience, I must said that I am very impressed with the performance and functionality of the iNotes 8.51 client. The iNotes team has done an impressive job in making the experience is some ways even better than the Lotus Notes 8.51 client. For one thing it sure comes up much faster.

Comments

Keith Brooks said…

This is VERY true of late for me as well. However there are some issues which I would like to resolve before going whole hog.

Sidebar apps in iNotes, not quite same process, if at all, possible to install.
Browser issues usually from Firefox but not IE7. Not many but recent FF crashes make me wonder if another FF updaste is imminent.
ACL issues still are a problem, need some way to resolve from the web side, especially for apps.
Mail Rules work but more flexibility in client.
But these are nitpicks on what is generally still a far superior experience over OWA and Outlook and immensely over Exchange.

July 4, 2010 at 5:59 PM

Domino Interface said…

Keith,

I have not used the iNotes sidebar. I don't use it much with the Notes client but I would be nice for having the Web apps accessible on the sidebar.

July 5, 2010 at 8:45 AM

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

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

The iPhora Journey - Part 4 - JSON is King - The How

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 The iPhora Journey - Part 4 - JSON is King - The Why The iPhora Journey - Part 4 - JSON is King - The How As we mentioned yesterday, in reimagining Domino, we wanted Domino to be a modern web application server, one that utilized a JSON-based NoSQL database and be more secure compared to other JSON-based NoSQL platforms. A Domino document existing within a Domino database is the foundational data record used in iPhora, just as it is with traditional Domino applications. But instead of just storing data into individual fields, we wanted to store and process the JSON in a Domino document. However, text fields (AKA summary fields) in Domino documents are limited to only 64 KBytes, and that is a serious limitation. 64 KBytes of JSON data does not even touch what the real world typically transfers back and fo

Domino Interface

Search This Blog