Wed 13 Feb 2019
@MQRY and on-the-fly data retrieval
Mon 11 Feb 2019
Thu 7 Feb 2019
Could working with rich text really be RESTful?
Rendering a perfect 10 needs an assist
Tue 8 Jan 2019, 10:13 PMTweet
by Ben Langhinrichs
I'm glad to see the Domino Jams taking place, but since not everybody will even move to IBM Notes/Domino 10 in the near future, note that this demo would look the same if run in Notes/Domino 7 or 8 or 8.5 or 9 or 10. And yes, you can rest assured it will work in HCL Notes/Domino 11 when that comes around.
The fact of the matter is, if everybody would stick to simple text in Notes, there would be no need for Genii Software's products. In fact, if everybody carefully built their rich text content with web rendering in mind, there would be less need for Genii Software's products. But there would also be little need for Notes.
The fact is, people out there use all sorts of rich text constructs, thinking that whatever they create will keep looking the way it should. This sample was built around an actual customer issue from December, though I adapted it for demo purposes to be both generic and easy to visualize. The customer used the gradient colors for the title rows and had no borders except a table border. Easy enough to imitate, but not so easy for the Domino web engine to render. I am building demos showing this and other documents based on actual customer issues rendered for use in email, mobile apps, JSON, web apps, XPages apps. The results vary some, but in all cases, the Genii products come very close to rendering the customer's data the way it was built. (Note: this was not from rich text a person created by hand, but a rendered form, which is often the source of complex content.)
Can you spot the differences? If so, do you think your employees, partners, and customers might as well?
Request eval of the Midas LSX (programmability) or CoexLinks Fidelity (email) or AppsFidelity (web/mobile rendering)
Copyright © 2019 Genii Software Ltd.
What has been said: