One thing that's good is the terminology change, for "databases" now being called "applications" which is as it should be. ... Maybe I'm oversensitive about this. I mention it because, in another blog post, I bemoan the fact that the IBM Application System/400 (or AS/400), with its original emphasis on being an application-focused platform, had its name changed later to "IBM iSeries" and later again to "System i" as part of an IBM branding campaign, which in my mind is a loss of an important part of its identity. (During my decades at IBM, I spent many years supporting the predecessor IBM System/38, then the AS/400, with some intervening assignments on IBM mainframe networking systems, the real-time sensor-based IBM System/7, and the IBM RT System with AIX Version 1.0.)
So now we have moved on to using the term "applications" for Notes databases, and I like it! I reckon that far too much discussion about Notes -- and especially about Notes versus the rest (Outlook, Exchange, etc) -- centers on e-mail topics. There are many, many, many other sorts of applications out there, much loved and still widely used by IBM's customers. Sure, e-mail is still a very important application (the original "killer app"), but let's move the focus back on to applications. I think we'll see that happening with ND8, what with the great capability of integrated "composite applications" -- and not a moment too soon, I say!
Preliminary testing indicates that all of the NotesTracker Version 5.0 features work without problems under this slick new Notes 8 Client.
This is good news all round, because NotesTracker has some fairly intense LotusScript routines, and they all seem to work just like they do in Notes/Domino 7.0.2.
I say this with a feeling of relief, because I had an unsettling experience with Notes 6.0. NotesTracker uses two Rich Text fields to store the before and after values of user database fields that have been updated, and the code worked fine for Notes R4 and R5. However the code "broke" with Notes 6, due to an "undocumented feature" that erroneously created duplicate Rich Text fields. I would call this a bug, but I suppose that Lotus would regard as an "undocumented feature change" added when Rich Text support was significantly enhanced in Notes 6. Luckily I found a way to bypass this bug, so that feature of NotesTracker got back on track for Notes 6 and Notes 7. You will understand, then, why it was one of the first things I tested for Notes Domino 8, and all went well.
I rather like the Sidebar's standard RSS feeds capability, particularly in view of the fact that NotesTracker v5.0 has made it even easier (with some code tweaking and examples) for you to automatically generate data for Notes views that form the building blocks or your own RSS feeds! (Refer to the NotesTracker Guide to find out more about this, in a section near the end.)
Further reports on NotesTracker and Notes Domino 8 will surely follow.