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?
A layer, a layout region and an embedded control walked into a bar
Tue 19 Dec 2017, 12:21 PMTweet
by Ben Langhinrichs
If you wonder what the joke in that is, you have not tried rendering documents created over the past twenty years by various companies. While it may be easy to dismiss such design elements as legacy artifacts, your company or your client's company may have them in active use or in archives that must be preserved. Whether due to ISO 9000 or other statutory or regulatory requirements, both data and appearance must be preserved. Even if you wanted to replace the design of every database (trust me, you don't) to replicate the look and feel, you'd have to deal with stored forms and rendered documents which have those layout regions, layers and embedded controls inside the rich text fields. This includes emails as well as application documents, etc.
IBM has done an amazing job in the Notes client, supporting every ancient design spasm that came along, but even if you love the Notes client, you may not want to remain locked to it forever. A big part of our effort at Genii Software in the past couple of years has been in rendering the unrenderable. Whether you want those ISO 9000 documents displayed through a web front end or stored in a standards-based vault, you need to be able to get an accurate rendering without changing the stored document at all. That is where Midas and AppsFidelity and CoexLinks come in, all of them sharing crucial pieces of a rendering engine built to handle just about anything. Give us a call at +1 216‒991‒5220 or send us an email at email@example.com, and ask how we can help with your thorniest issues, whether you are moving to the cloud, migrating, or just mobile-enabling an app. No risk asking, and you might find a solution which make you a hero, rather than a punch line.
Copyright © 2017 Genii Software Ltd.
What has been said: