Ben Langhinrichs

Photograph of Ben Langhinrichs

IBM Champion logo

E-mail address - Ben Langhinrichs






January, 2018
SMTWTFS
 01 02 03 04 05 06
07 08 09 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31

Search the weblog





























Genii Weblog


Civility in critiquing the ideas of others is no vice. Rudeness in defending your own ideas is no virtue.


Thu 25 Jan 2018, 01:22 PM
I made a very brief demo (53 seconds!) to show two different ways tabbed tables could be rendered by the Midas LSX or AppsFidelity. While your users may not add tabbed tables to rich text, it is quite likely your developers have added them to forms, so when you want a snapshot of a document, or want to display it on the web or in a mobile app as a rendered document, or email the document, the tabbed tables must be handled.
 
Try forwarding a document with a tabbed table either in the form or in the rich text itself, and you will get a "flattened" version where every row is shown. Depending on whether your client or server handles the MIME, the tabs may be lost completely or added to a separate row. With the Midas Exports engine, you can get a similar, but more well-rendered version of this "flattened" look. That is the default, and is certainly preferred for email or printing.
 
But the Midas Exports engine can also generate a JavaScript version of the tabbed table which allows for a look-and-feel much closer to that in Notes. It is preferred for archived snapshots (in MHT or HTML), as well as for apps that won't edit the content but do want to display it on the web or in a mobile app. This demo shows both approaches.
 
 
This is the first in a planned series of very brief demos showing how the Midas Exports engine handles different optional rendering to meet whatever needs you may have. Using only standards-based HTML, CSS and JavaScript means that whatever your intended target, it will almost certainly support the rendered Notes content.
 

Copyright © 2018 Genii Software Ltd.

Tags: