Skip to main content

Initial Review of Notes 8 Beta 2

I spent the past few days playing with the Notes 8 beta 2 both the Standard version (eclipse) and the Basic version (w32 C++). My review here is based only on the UI and not the other features that are available in the new version of Notes 8. In addition, this is the my first review. My review was done on a Thinkpad T41 with 1Gbytes of memory with Windows XP SP1. The Domino server that I used to make this review is an Domino 6.53 server.

Notes 8 Standard client:
As I understand it, the standard version is an Eclipse wrapper around the Notes Basic client. If I am wrong, please correct me. Even with the much larger footprint, the standard version perform pretty well on a machine that is not dual-core. The interface looks very good, though there are a number of quirks that I assume will be fixed in the final release. I did discovered and reported a number of bugs, but that is normal since this is a beta. I was disappointed to discover that there is no storage of the productivity documents into Notes out of the box. I guess that will be coming with Quickr. However there are a few things that I do not like about Notes 8 Standard. I do not like in particular the Open button. What appears on the list should be programmed either by the administrator or set by the user. Every single bookmark seems to show up in the list. Since I upgraded from a Notes 6.5 client, I have over 300 items listed in various folders. This is annoying. Our applications and probably many others have a primary launching application from which other applications start from. I only want a icon for the launching application.

Application launched from the sidebar like the RSS reader as a separate window should remain like the info box in front of the Notes 8 client. It was a pain in the butt to have to switch back and forward between the window and Notes client. In the RSS reader, when you open the feed it should appear in the same window instead of being in a new Notes tab.

Notes 8 Basic client:
The basic client looks and feels like Notes 7 with the exception of inline spell checking, nicer icons, and changes to the menu arrangement to match the standard client menu. I was disappointed to see that a number of UI improvements that are in the standard client was not in this client. Technically, I do not know why it could not have been in this client. Since this client is smaller and lighter it does run faster. Though it looks like Notes 7, there are still a few bugs in this client when it comes to UI specially with javascript and Notes windows.

These are my initial comments for the Notes 8 beta 2 standard and basic client. I will be setting up Domino 8 in the next few weeks and report back to you.

Comments

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

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 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