Domino Interface

The new buzz word that has become more and more important is SECURITY. But, why is that? Security should always have been up and front and center. The Domino platform has always been at the forefront in terms of security from its inception. The new HCL Nomad (Domino Mobile App) platform brings this security to your mobile device. But let's face it, Notes apps are ugly compared to modern mobile apps. In June 2019, HCL launched the HCL Design Project called "Template Experience" to transform and modernize select Notes templates. To encourage the Notes/Domino community to unleash the potential of Notes and Domino V10, CollabSphere has joined forces with OpenNTF and launched the CollabSphere Beauty Contest. This global contest encourages you the developer to show your potential in transforming an ugly duckling to a beautiful swan. So get your thinking caps on, design skills ready and transform the ToDo template into a beautiful but secure app. Go to https://tinyu...

Many in the ICS community have made the statement that Notes and Domino are dead. Many in the ICS community have been questioning the future of Domino and they have ever right to do so considering the lack of and inconsistent communication from IBM and lack of improvements to the platform for the past 4 years.  Yes we have had improvements regarding SSL security fixes but that was driven by the discovery of serious vulnerabilities in SSL. Like many customers and IBM partners, we built many many Notes applications internally and for clients. Some of these applications are still running on many of our clients and will continue to do so for the foreseeable future. They do not have the coolest interfaces since those capabilities weren't around even from other vendors at the time they were developed. They are clunky looking, but they are secure which is very important since the beginning of Notes and more so these days.  IBM announced yesterday that they are extending support...

For our iPhora applications we only use one XPage and dynamically create the content that appears.  We do this by storing the dynamic content in Notes Rich Text fields and using SSJS to read and generate the HTML/JavaScript during runtime.  Since we are moving to an single page MVC model, we were adding a few addition xp:scriptBlock to generate the initial loader and pulling the information from a NotesRichText field.  We were using doc.getFirstValueString('richtextfield') to pull and create the script. No problem until, we had a JavaScript object declaration that was longer than 72 odd characters. Unfortunately, there is an issue with Notes Rich Text fields that we encountered in the past using LotusScript that I forgot all about.  When you read a Notes Rich Text field it will automatically add a carriage return after 72 characters and this can drive you crazy. If the carriage return occurs between a JavaScript object declaration then yo...