Single Common Group Across Multiple Stacks

[J. Landman Gay]

On 7/3/2016 10:29 PM, Sannyasin Brahmanathaswami wrote:
> GOAL: have a object/group (think navigation bar at the bottom of the
> screen or some other elements you may want to be common across all
> the stacks….) that can be displayed  in all the stacks.

This is exactly the setup I needed for the big project I've been working 
on for some time. We solved it by creating a one-card template stack 
that is used to create all new subsidiary stacks. The template has all 
shared groups placed on its single card. In our case we had several of 
those on each card that needed to appear everywhere.

All new content stacks are created from this one-card template. As new 
cards are made they automatically inherit and place the shared groups. 
Having these already on every card eased layout as well, because the 
available space for new controls was readily apparent.

The shared groups contained only the most basic scripts, usually a 
one-liner that called a handler. For example, each button has a "doX" 
handler call such as "doLookup" or "doNavFwd".

The "doX" handler itself was in a backscript loaded by the main launcher 
stack, the one that becomes the app. This script is always in use and it 
controls virtually everything no matter what stack is currently loaded 
from the server.

This has been working very well for us for some years now. To make 
changes, all you need to do is edit the backscript and release a new 
launcher app version. The content stacks never need to change.

-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com